Error establishing a database connection

前天数据库出错，无法启动，经过河妖耐心指导解决了问题，昨天早上打开网站提示
Error establishing a database connection面板里面仍然是开启不了数据库，
运行修复命令wget -O sql-repair.sh http://download.bt.cn/install/sql-repair.sh && sh sql-repair.sh
然后可以开启，但是今早打开网站，又是
Error establishing a database connection
还是只能通过修复命令才可以开启，
Version: '5.6.39-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
2018-05-03 09:26:57 20977 [Note] Plugin 'FEDERATED' is disabled.
2018-05-03 09:26:57 20977 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-05-03 09:26:57 20977 [Note] InnoDB: The InnoDB memory heap is disabled
2018-05-03 09:26:57 20977 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-05-03 09:26:57 20977 [Note] InnoDB: Memory barrier is not used
2018-05-03 09:26:57 20977 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-05-03 09:26:57 20977 [Note] InnoDB: Using CPU crc32 instructions
2018-05-03 09:26:57 20977 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-05-03 09:26:57 20977 [Note] InnoDB: Completed initialization of buffer pool
2018-05-03 09:26:57 20977 [Note] InnoDB: Highest supported file format is Barracuda.
2018-05-03 09:26:57 20977 [Note] InnoDB: The log sequence numbers 43929642 and 43929642 in ibdata files do not match the log sequence number 46034383 in the ib_logfiles!
2018-05-03 09:26:57 20977 [Note] InnoDB: Database was not shutdown normally!
2018-05-03 09:26:57 20977 [Note] InnoDB: Starting crash recovery.
2018-05-03 09:26:57 20977 [Note] InnoDB: Reading tablespace information from the .ibd files...
2018-05-03 09:26:57 20977 [Note] InnoDB: Restoring possible half-written data pages
2018-05-03 09:26:57 20977 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Last MySQL binlog file position 0 1173931, file name mysql-bin.000004
2018-05-03 09:26:57 20977 [Note] InnoDB: 128 rollback segment(s) are active.
2018-05-03 09:26:57 20977 [Note] InnoDB: Waiting for purge to start
2018-05-03 09:26:57 20977 [Note] InnoDB: 5.6.39 started; log sequence number 46034383
2018-05-03 09:26:57 20977 [Note] Recovering after a crash using mysql-bin
2018-05-03 09:26:57 20977 [Note] Starting crash recovery...
2018-05-03 09:26:57 20977 [Note] Crash recovery finished.
2018-05-03 09:26:57 20977 [Note] Server hostname (bind-address): '*'; port: 3306
2018-05-03 09:26:57 20977 [Note] IPv6 is not available.
2018-05-03 09:26:57 20977 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
2018-05-03 09:26:57 20977 [Note] Server socket created on IP: '0.0.0.0'.
2018-05-03 09:26:57 20977 [Note] Event Scheduler: Loaded 0 events
2018-05-03 09:26:57 20977 [Note] /www/server/mysql/bin/mysqld: ready for connections.
Version: '5.6.39-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
2018-05-04 07:05:09 29118 [Note] Plugin 'FEDERATED' is disabled.
2018-05-04 07:05:09 29118 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-05-04 07:05:09 29118 [Note] InnoDB: The InnoDB memory heap is disabled
2018-05-04 07:05:09 29118 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-05-04 07:05:09 29118 [Note] InnoDB: Memory barrier is not used
2018-05-04 07:05:09 29118 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-05-04 07:05:10 29118 [Note] InnoDB: Using CPU crc32 instructions
2018-05-04 07:05:10 29118 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-05-04 07:05:10 29118 [Note] InnoDB: Completed initialization of buffer pool
2018-05-04 07:05:10 29118 [Note] InnoDB: Highest supported file format is Barracuda.
2018-05-04 07:05:10 29118 [Note] InnoDB: The log sequence numbers 43929642 and 43929642 in ibdata files do not match the log sequence number 47148835 in the ib_logfiles!
2018-05-04 07:05:10 29118 [Note] InnoDB: Database was not shutdown normally!
2018-05-04 07:05:10 29118 [Note] InnoDB: Starting crash recovery.
2018-05-04 07:05:10 29118 [Note] InnoDB: Reading tablespace information from the .ibd files...
2018-05-04 07:05:10 29118 [Note] InnoDB: Restoring possible half-written data pages
2018-05-04 07:05:10 29118 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Last MySQL binlog file position 0 868900, file name mysql-bin.000005
2018-05-04 07:05:10 29118 [Note] InnoDB: 128 rollback segment(s) are active.
2018-05-04 07:05:10 29118 [Note] InnoDB: Waiting for purge to start
2018-05-04 07:05:10 29118 [Note] InnoDB: 5.6.39 started; log sequence number 47148835
2018-05-04 07:05:10 29118 [Note] Recovering after a crash using mysql-bin
2018-05-04 07:05:10 29118 [Note] Starting crash recovery...
2018-05-04 07:05:10 29118 [Note] Crash recovery finished.
2018-05-04 07:05:10 29118 [Note] Server hostname (bind-address): '*'; port: 3306
2018-05-04 07:05:10 29118 [Note] IPv6 is not available.
2018-05-04 07:05:10 29118 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
2018-05-04 07:05:10 29118 [Note] Server socket created on IP: '0.0.0.0'.
2018-05-04 07:05:10 29118 [Note] Event Scheduler: Loaded 0 events
2018-05-04 07:05:10 29118 [Note] /www/server/mysql/bin/mysqld: ready for connections.
Version: '5.6.39-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution

这是MYSQL这两天的日志

你多大内存？

河妖 发表于 2018-5-4 09:58
你多大内存？

白天有事，没及时回复，抱歉！这个空间是阿里云的1核2G那款，就是活动价279三年的那个

jueshi 发表于 2018-5-4 22:03
白天有事，没及时回复，抱歉！这个空间是阿里云的1核2G那款，就是活动价279三年的那个 ...

啥时候的活动279三年

问题怎么解决的，我的和你的一样情况-WORDPRESS 过几天就这样，重启服务器就好了

zf2020 发表于 2021-1-25 19:47
问题怎么解决的，我的和你的一样情况-WORDPRESS 过几天就这样，重启服务器就好了 ...

哥们，你的问题是否解决？
同样Error establishing a database connection，重启就好，关键是不知道什么时候会崩

宝塔用户_lilhqt 发表于 2021-5-1 12:34
哥们，你的问题是否解决？
同样Error establishing a database connection，重启就好，关键是不知道什么 ...

计划任务栏目，设置定时释放内存，监控数据库