首页 新闻 搜索 专区 学院

关于mysql在Linux中自动停止的问题

0
[待解决问题]

这个问题持续有一段时间了,就是mysql运行一段时间之后就会自动停止,去网上也查过修改配置文件也修改了,可是问题还是照旧,有没有大神遇到过这种情况,还请麻烦指点一二,感激不尽!

 

注:系统版本是CentOS 6.8 (Final) 面板用的是BT宝塔

问题补充:

补充一下:不是服务器内存溢出,这点已经查看过了,服务器是2核4G的

admin22的主页 admin22 | 菜鸟二级 | 园豆:220
提问于:2018-03-28 09:50
< >
分享
所有回答(3)
0

你可以查一下,mysql有一个记录执行记录的日志,这个文件如果在大数据量操作下会非常的大,会造成mysql挂起

番茄先生 | 园豆:911 (小虾三级) | 2018-03-28 10:16

日志每次都看,什么提示都没有就提示一个不是正常关闭,对数据库根本没有什么大数据的操作,这段期间对数据库的操作几乎都没有,修改过c3p0连接池的配置结果还是不行,太郁闷了

支持(0) 反对(0) admin22 | 园豆:220 (菜鸟二级) | 2018-03-28 10:26

180328 9:57:02 InnoDB: The InnoDB memory heap is disabled
180328 9:57:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins
180328 9:57:02 InnoDB: Compressed tables use zlib 1.2.3
180328 9:57:02 InnoDB: Using Linux native AIO
180328 9:57:02 InnoDB: Initializing buffer pool, size = 600.0M
180328 9:57:02 InnoDB: Completed initialization of buffer pool
180328 9:57:02 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!
180328 9:57:02 InnoDB: 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 512, file name ./mysql-bin.000298
180328 9:57:03 InnoDB: Waiting for the background threads to start
180328 9:57:04 InnoDB: 5.5.59 started; log sequence number 1627275
180328 9:57:04 [Note] Recovering after a crash using mysql-bin
180328 9:57:04 [Note] Starting crash recovery...
180328 9:57:04 [Note] Crash recovery finished.
180328 9:57:04 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
180328 9:57:04 [Note] - '0.0.0.0' resolves to '0.0.0.0';
180328 9:57:04 [Note] Server socket created on IP: '0.0.0.0'.
180328 9:57:04 [Note] Event Scheduler: Loaded 0 events
180328 9:57:04 [Note] /www/server/mysql/bin/mysqld: ready for connections.
Version: '5.5.59-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution
180328 10:00:02 [Note] Plugin 'FEDERATED' is disabled.
180328 10:00:02 InnoDB: The InnoDB memory heap is disabled
180328 10:00:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins
180328 10:00:02 InnoDB: Compressed tables use zlib 1.2.3
180328 10:00:02 InnoDB: Using Linux native AIO
180328 10:00:02 InnoDB: Initializing buffer pool, size = 600.0M
180328 10:00:02 InnoDB: Completed initialization of buffer pool
180328 10:00:02 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!
180328 10:00:02 InnoDB: 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 512, file name ./mysql-bin.000298
180328 10:00:02 InnoDB: Waiting for the background threads to start
180328 10:00:03 InnoDB: 5.5.59 started; log sequence number 1627275
180328 10:00:03 [Note] Recovering after a crash using mysql-bin
180328 10:00:03 [Note] Starting crash recovery...
180328 10:00:03 [Note] Crash recovery finished.
180328 10:00:03 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
180328 10:00:03 [Note] - '0.0.0.0' resolves to '0.0.0.0';
180328 10:00:03 [Note] Server socket created on IP: '0.0.0.0'.
180328 10:00:03 [Note] Event Scheduler: Loaded 0 events
180328 10:00:03 [Note] /www/server/mysql/bin/mysqld: ready for connections.
Version: '5.5.59-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution
180328 10:19:02 [Note] Plugin 'FEDERATED' is disabled.
180328 10:19:02 InnoDB: The InnoDB memory heap is disabled
180328 10:19:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins
180328 10:19:02 InnoDB: Compressed tables use zlib 1.2.3
180328 10:19:02 InnoDB: Using Linux native AIO
180328 10:19:02 InnoDB: Initializing buffer pool, size = 600.0M
180328 10:19:02 InnoDB: Completed initialization of buffer pool
180328 10:19:02 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!
180328 10:19:02 InnoDB: 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 512, file name ./mysql-bin.000298
180328 10:19:02 InnoDB: Waiting for the background threads to start
180328 10:19:03 InnoDB: 5.5.59 started; log sequence number 1627285
180328 10:19:03 [Note] Recovering after a crash using mysql-bin
180328 10:19:03 [Note] Starting crash recovery...
180328 10:19:03 [Note] Crash recovery finished.
180328 10:19:03 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
180328 10:19:03 [Note] - '0.0.0.0' resolves to '0.0.0.0';
180328 10:19:03 [Note] Server socket created on IP: '0.0.0.0'.
180328 10:19:03 [Note] Event Scheduler: Loaded 0 events
180328 10:19:03 [Note] /www/server/mysql/bin/mysqld: ready for connections.
Version: '5.5.59-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution
180328 10:20:01 [Note] Plugin 'FEDERATED' is disabled.
180328 10:20:01 InnoDB: The InnoDB memory heap is disabled
180328 10:20:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
180328 10:20:01 InnoDB: Compressed tables use zlib 1.2.3
180328 10:20:01 InnoDB: Using Linux native AIO
180328 10:20:01 InnoDB: Initializing buffer pool, size = 600.0M
180328 10:20:01 InnoDB: Completed initialization of buffer pool
180328 10:20:01 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!
180328 10:20:01 InnoDB: 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...

支持(0) 反对(0) admin22 | 园豆:220 (菜鸟二级) | 2018-03-28 10:27

@admin22: 难道是数据库连接池线程用光了?或者mysql链接默认8个小时就会关闭,你也可以从这方面入手,我也不是做DB的。。。。。,都是自己平时的了解

支持(0) 反对(0) 番茄先生 | 园豆:911 (小虾三级) | 2018-03-28 11:27

@admingk: 之前也试过了,不行,我都郁闷死了

支持(0) 反对(0) admin22 | 园豆:220 (菜鸟二级) | 2018-03-28 13:48
0
dudu | 园豆:37154 (高人七级) | 2018-03-28 11:52

大哥看不懂啊,有没有中文的

支持(0) 反对(0) admin22 | 园豆:220 (菜鸟二级) | 2018-03-28 13:47
0

重装系统,所有问题全部解决!!

admin22 | 园豆:220 (菜鸟二级) | 2018-04-27 19:14
清除回答草稿
   您需要登录以后才能回答,未注册用户请先注册