So a little background, a few weeks ago I brought a new CentOS dedicated server in Melbourne, however it seems beside the number of attackers I get, there also seem to be an issue with the MySQL database, or a software that is using is as it keep crashing and drying.
I have gone thru the logs and don't see any reason why it would be crashing but i am wondering if anyone out there would be able to give me a hand fixing this issue.
Last part of the log file:
150512 06:15:02 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
150512 06:20:02 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
150512 6:20:02 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
150512 6:20:02 [Note] Plugin 'FEDERATED' is disabled.
150512 6:20:02 InnoDB: The InnoDB memory heap is disabled
150512 6:20:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150512 6:20:02 InnoDB: Compressed tables use zlib 1.2.3
150512 6:20:02 InnoDB: Using Linux native AIO
150512 6:20:02 InnoDB: Initializing buffer pool, size = 128.0M
150512 6:20:02 InnoDB: Completed initialization of buffer pool
150512 6:20: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!
150512 6:20: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...
150512 06:20:02 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
150512 06:25:02 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
150512 6:25:02 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
150512 6:25:02 [Note] Plugin 'FEDERATED' is disabled.
150512 6:25:02 InnoDB: The InnoDB memory heap is disabled
150512 6:25:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150512 6:25:02 InnoDB: Compressed tables use zlib 1.2.3
150512 6:25:02 InnoDB: Using Linux native AIO
150512 6:25:02 InnoDB: Initializing buffer pool, size = 128.0M
150512 6:25:02 InnoDB: Completed initialization of buffer pool
150512 6:25: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!
150512 6:25: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...
150512 06:25:03 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
150512 06:30:01 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
150512 6:30:01 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
150512 6:30:01 [Note] Plugin 'FEDERATED' is disabled.
150512 6:30:01 InnoDB: The InnoDB memory heap is disabled
150512 6:30:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150512 6:30:01 InnoDB: Compressed tables use zlib 1.2.3
150512 6:30:01 InnoDB: Using Linux native AIO
150512 6:30:01 InnoDB: Initializing buffer pool, size = 128.0M
150512 6:30:01 InnoDB: Completed initialization of buffer pool
150512 6:30: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!
150512 6:30: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...
150512 6:30:01 InnoDB: Waiting for the background threads to start
150512 6:30:02 InnoDB: 5.5.41 started; log sequence number 68534366
150512 6:30:02 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
150512 6:30:02 [Note] - '0.0.0.0' resolves to '0.0.0.0';
150512 6:30:02 [Note] Server socket created on IP: '0.0.0.0'.
150512 6:30:02 [Note] Event Scheduler: Loaded 0 events
150512 6:30:02 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.41' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) by Remi
150512 06:42:37 mysqld_safe Number of processes running now: 0
150512 06:42:37 mysqld_safe mysqld restarted
150512 6:42:37 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
150512 6:42:37 [Note] Plugin 'FEDERATED' is disabled.
150512 6:42:37 InnoDB: The InnoDB memory heap is disabled
150512 6:42:37 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150512 6:42:37 InnoDB: Compressed tables use zlib 1.2.3
150512 6:42:37 InnoDB: Using Linux native AIO
150512 6:42:37 InnoDB: Initializing buffer pool, size = 128.0M
150512 6:42:37 InnoDB: Completed initialization of buffer pool
150512 6:42:37 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!
150512 6:42:37 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...
150512 6:42:37 InnoDB: Waiting for the background threads to start
150512 06:42:37 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
150512 06:45:02 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
150512 6:45:02 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
150512 6:45:02 [Note] Plugin 'FEDERATED' is disabled.
150512 6:45:02 InnoDB: The InnoDB memory heap is disabled
150512 6:45:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150512 6:45:02 InnoDB: Compressed tables use zlib 1.2.3
150512 6:45:02 InnoDB: Using Linux native AIO
150512 6:45:02 InnoDB: Initializing buffer pool, size = 128.0M
150512 6:45:02 InnoDB: Completed initialization of buffer pool
150512 6:45: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!
150512 6:45: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...
150512 6:45:02 InnoDB: Waiting for the background threads to start
150512 6:45:03 InnoDB: 5.5.41 started; log sequence number 68578838
150512 6:45:03 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
150512 6:45:03 [Note] - '0.0.0.0' resolves to '0.0.0.0';
150512 6:45:03 [Note] Server socket created on IP: '0.0.0.0'.
150512 6:45:03 [Note] Event Scheduler: Loaded 0 events
150512 6:45:03 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.41' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL \
The server is running the following:
CentOS 6 vestaCP MYSQL 5.5.4 Mail Server