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

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...

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

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

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