wordpress数据库问题
LNMP 1.5环境下安装wordpress学习建站。vultr 512M，经军歌指导设置了SWAP交换文件。WP也正常使用了一段时间，昨天发现，再打开网站提示“建立数据库连接时出错”，检查了下LNMP环境运行正常，进数据库发现wordpress的数据库文件不见了。幸好我有备份。
手动重新wp数据库文件，重新安装wp，恢复数据，wp站就正常了。今天再开又是“建立数据库连接时出错”，wp的数据库文件又丢失了。
只得来求助军哥了。
以下是昨天 今天的数据库日志，完整日志在附件。
1901090:07:47 IP address '196.52.43.122' could not be resolved: Name or service not known
1901098:51:21 IP address '61.96.86.28' could not be resolved: Name or service not known
190109 10:26:59 IP address '115.231.222.95' could not be resolved: Name or service not known
190109 16:01:12 Plugin 'FEDERATED' is disabled.
190109 16:01:12 InnoDB: The InnoDB memory heap is disabled
190109 16:01:12 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190109 16:01:12 InnoDB: Compressed tables use zlib 1.2.7
190109 16:01:12 InnoDB: Using Linux native AIO
190109 16:01:12 InnoDB: Initializing buffer pool, size = 16.0M
190109 16:01:12 InnoDB: Completed initialization of buffer pool
190109 16:01:12 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
190109 16:01:12InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Last MySQL binlog file position 0 11374195, file name ./mysql-bin.000007
190109 16:01:12InnoDB: Waiting for the background threads to start
190109 16:01:13 InnoDB: 5.5.60 started; log sequence number 19858605
190109 16:01:13 Recovering after a crash using mysql-bin
190109 16:01:13 Starting crash recovery...
190109 16:01:13 Crash recovery finished.
190109 16:01:13 Server hostname (bind-address): '0.0.0.0'; port: 3306
190109 16:01:13 - '0.0.0.0' resolves to '0.0.0.0';
190109 16:01:13 Server socket created on IP: '0.0.0.0'.
190109 16:01:13 Event Scheduler: Loaded 0 events
190109 16:01:13 /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.5.60-log'socket: '/tmp/mysql.sock'port: 3306Source distribution
190109 16:02:21 IP address '85.93.20.38' could not be resolved: Name or service not known
190109 16:24:30 IP address '211.218.126.142' could not be resolved: Name or service not known
190109 16:26:15 /usr/local/mysql/bin/mysqld: Normal shutdown
190109 16:26:15 Event Scheduler: Purging the queue. 0 events
190109 16:26:15InnoDB: Starting shutdown...
190109 16:26:16InnoDB: Shutdown completed; log sequence number 19858615
190109 16:26:16 /usr/local/mysql/bin/mysqld: Shutdown complete
190109 16:26:18 Plugin 'FEDERATED' is disabled.
190109 16:26:18 InnoDB: The InnoDB memory heap is disabled
190109 16:26:18 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190109 16:26:18 InnoDB: Compressed tables use zlib 1.2.7
190109 16:26:18 InnoDB: Using Linux native AIO
190109 16:26:18 InnoDB: Initializing buffer pool, size = 16.0M
190109 16:26:18 InnoDB: Completed initialization of buffer pool
190109 16:26:18 InnoDB: highest supported file format is Barracuda.
190109 16:26:18InnoDB: Waiting for the background threads to start
190109 16:26:19 InnoDB: 5.5.60 started; log sequence number 19858615
190109 16:26:19 Server hostname (bind-address): '0.0.0.0'; port: 3306
190109 16:26:19 - '0.0.0.0' resolves to '0.0.0.0';
190109 16:26:19 Server socket created on IP: '0.0.0.0'.
190109 16:26:19 Event Scheduler: Loaded 0 events
190109 16:26:19 /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.5.60-log'socket: '/tmp/mysql.sock'port: 3306Source distribution
190109 16:30:10 IP address '85.93.20.38' could not be resolved: Name or service not known
190109 16:59:48 /usr/local/mysql/bin/mysqld: Normal shutdown
190109 16:59:48 Event Scheduler: Purging the queue. 0 events
190109 16:59:48InnoDB: Starting shutdown...
190109 16:59:49InnoDB: Shutdown completed; log sequence number 22330147
190109 16:59:49 /usr/local/mysql/bin/mysqld: Shutdown complete
190109 17:30:47 Plugin 'FEDERATED' is disabled.
190109 17:30:47 InnoDB: The InnoDB memory heap is disabled
190109 17:30:47 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190109 17:30:47 InnoDB: Compressed tables use zlib 1.2.7
190109 17:30:47 InnoDB: Using Linux native AIO
190109 17:30:47 InnoDB: Initializing buffer pool, size = 16.0M
190109 17:30:47 InnoDB: Completed initialization of buffer pool
190109 17:30:47 InnoDB: highest supported file format is Barracuda.
190109 17:30:47InnoDB: Waiting for the background threads to start
190109 17:30:48 InnoDB: 5.5.60 started; log sequence number 22330147
190109 17:30:48 Server hostname (bind-address): '0.0.0.0'; port: 3306
190109 17:30:48 - '0.0.0.0' resolves to '0.0.0.0';
190109 17:30:48 Server socket created on IP: '0.0.0.0'.
190109 17:30:48 Event Scheduler: Loaded 0 events
190109 17:30:48 /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.5.60-log'socket: '/tmp/mysql.sock'port: 3306Source distribution
190109 17:33:46 IP address '85.93.20.38' could not be resolved: Name or service not known
190109 18:41:43 IP address '89.248.162.177' could not be resolved: Name or service not known
190109 20:36:40 IP address '178.156.202.235' could not be resolved: Name or service not known
190109 22:33:00 IP address '27.124.17.108' could not be resolved: Name or service not known
1901102:56:55 IP address '196.52.43.113' could not be resolved: Name or service not known
1901105:56:26 IP address '124.95.128.226' could not be resolved: Name or service not known
190110 12:31:32 /usr/local/mysql/bin/mysqld: Normal shutdown
190110 12:31:32 Event Scheduler: Purging the queue. 0 events
190110 12:31:32InnoDB: Starting shutdown...
190110 12:31:34InnoDB: Shutdown completed; log sequence number 23186134
190110 12:31:34 /usr/local/mysql/bin/mysqld: Shutdown complete
190110 12:31:35 Plugin 'FEDERATED' is disabled.
190110 12:31:35 InnoDB: The InnoDB memory heap is disabled
190110 12:31:35 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190110 12:31:35 InnoDB: Compressed tables use zlib 1.2.7
190110 12:31:35 InnoDB: Using Linux native AIO
190110 12:31:35 InnoDB: Initializing buffer pool, size = 16.0M
190110 12:31:35 InnoDB: Completed initialization of buffer pool
190110 12:31:35 InnoDB: highest supported file format is Barracuda.
190110 12:31:35InnoDB: Waiting for the background threads to start
190110 12:31:36 InnoDB: 5.5.60 started; log sequence number 23186134
190110 12:31:36 Server hostname (bind-address): '0.0.0.0'; port: 3306
190110 12:31:36 - '0.0.0.0' resolves to '0.0.0.0';
190110 12:31:36 Server socket created on IP: '0.0.0.0'.
190110 12:31:36 Event Scheduler: Loaded 0 events
190110 12:31:36 /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.5.60-log'socket: '/tmp/mysql.sock'port: 3306Source distribution
mysql自己是不会去删除文件的，你说的数据库文件丢了，是去 /usr/local/mysql/var/ 下查看的数据库名字的目录吗？
从mysql日志上看的话mysql从9号开始有异常，有可能内存不够用被系统kill掉了
回复 2# 的帖子
嗯。 /usr/local/mysql/var/ 下的确是没有wordpress的目录了。
页:
[1]