这是一个创建于 2731 天前的主题，其中的信息可能已经有所发展或是发生改变。
情况：在服务器上运行了几个 wordpress 小站点，数据库之前一直没有问题，昨天开始就连接不上数据库了。 多次重启了数据库，在查看数据库状态是 active 的，但是最下面报了上图信息。在服务器上是可以登入到数据库的。
服务器上多个站点，并时不是所有站点都连接不上数据库，有一个最近新添加的站点是可以连接到数据库并可以放问网站，这个站点就添加一个主题，没有其他操作。
我尝试了 把所有数据通过 mysqldump 导出，又重新导入到全新的数据库内，但是新的数据库导入还会遇到上图问题。
第 1 条附言 · 2017-06-01 05:47:42 +08:00
在 /var/log/mariadb/ 下找到一个 mariadb.log.rpmsave 文件
170209 2:03:51 [Note] Event Scheduler: Purging the queue. 0 events
170209 2:03:51 InnoDB: Starting shutdown...
170209 2:03:52 InnoDB: Shutdown completed; log sequence number 147762982
170209 2:03:52 [Note] /usr/libexec/mysqld: Shutdown complete
170209 02:03:52 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
170209 02:03:52 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
170209 2:03:52 [Note] /usr/libexec/mysqld (mysqld 5.5.52-MariaDB) starting as process 20626 ...
170209 2:03:52 InnoDB: The InnoDB memory heap is disabled
170209 2:03:52 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170209 2:03:52 InnoDB: Compressed tables use zlib 1.2.7
170209 2:03:52 InnoDB: Using Linux native AIO
170209 2:03:52 InnoDB: Initializing buffer pool, size = 128.0M
170209 2:03:52 InnoDB: Completed initialization of buffer pool
170209 2:03:52 InnoDB: highest supported file format is Barracuda.
170209 2:03:52 InnoDB: Waiting for the background threads to start
170209 2:03:53 Percona XtraDB ( http://www.percona.com) 5.5.49-MariaDB-38.0 started; log sequence number 147762982
170209 2:03:53 [Note] Plugin 'FEEDBACK' is disabled.
170209 2:03:53 [Note] Server socket created on IP: '0.0.0.0'.
170209 2:03:53 [Note] Event Scheduler: Loaded 0 events
170209 2:03:53 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.52-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
170209 2:10:30 [Note] /usr/libexec/mysqld: Normal shutdown
170209 2:10:30 [Note] Event Scheduler: Purging the queue. 0 events
170209 2:10:30 InnoDB: Starting shutdown...
170209 2:10:31 InnoDB: Shutdown completed; log sequence number 147779151
170209 2:10:31 [Note] /usr/libexec/mysqld: Shutdown complete
170209 02:10:31 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
170209 2:03:51 [Note] Event Scheduler: Purging the queue. 0 events
170209 2:03:51 InnoDB: Starting shutdown...
170209 2:03:52 InnoDB: Shutdown completed; log sequence number 147762982
170209 2:03:52 [Note] /usr/libexec/mysqld: Shutdown complete
170209 02:03:52 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
170209 02:03:52 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
170209 2:03:52 [Note] /usr/libexec/mysqld (mysqld 5.5.52-MariaDB) starting as process 20626 ...
170209 2:03:52 InnoDB: The InnoDB memory heap is disabled
170209 2:03:52 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170209 2:03:52 InnoDB: Compressed tables use zlib 1.2.7
170209 2:03:52 InnoDB: Using Linux native AIO
170209 2:03:52 InnoDB: Initializing buffer pool, size = 128.0M
170209 2:03:52 InnoDB: Completed initialization of buffer pool
170209 2:03:52 InnoDB: highest supported file format is Barracuda.
170209 2:03:52 InnoDB: Waiting for the background threads to start
170209 2:03:53 Percona XtraDB ( http://www.percona.com) 5.5.49-MariaDB-38.0 started; log sequence number 147762982
170209 2:03:53 [Note] Plugin 'FEEDBACK' is disabled.
170209 2:03:53 [Note] Server socket created on IP: '0.0.0.0'.
170209 2:03:53 [Note] Event Scheduler: Loaded 0 events
170209 2:03:53 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.52-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
170209 2:10:30 [Note] /usr/libexec/mysqld: Normal shutdown
170209 2:10:30 [Note] Event Scheduler: Purging the queue. 0 events
170209 2:10:30 InnoDB: Starting shutdown...
170209 2:10:31 InnoDB: Shutdown completed; log sequence number 147779151
170209 2:10:31 [Note] /usr/libexec/mysqld: Shutdown complete
170209 02:10:31 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
 |
1
lancerliu 2017-05-31 23:18:09 +08:00
一般这种问题，按一下流程走一遍：1.服务器 CPU 负载状况 2.内存占用状况 3.数据库连接是不是满了 但是最重要的是：连接不上数据库的错误日志呢？你不看日志怎么知道是什么问题
|
 |
2
yidinghe 2017-05-31 23:31:54 +08:00 via Android
是的，先看日志找原因。
|
 |
3
msg7086 2017-06-01 07:08:04 +08:00
图上什么都没说。
附言也什么都没说。 建议你看看内核日志，看看是不是内存不足被暗杀了。 |
Select Language