I have a problem shutting down the mysql server that is running on my mac. I tried from ActivityMonitor, from terminal using "mysqladmin shutdown" , kill -9 , and many other proposed ways but it always restarts within a second. Error log doesnt show anything strange:
30113 16:28:12 [Note] /usr/local/Cellar/mysql/5.5.25a/bin/mysqld: Normal shutdown
130113 16:28:12 [Note] Event Scheduler: Purging the queue. 0 events
130113 16:28:14 [Warning] /usr/local/Cellar/mysql/5.5.25a/bin/mysqld: Forcing close of thread 3 user: 'root'
130113 16:28:14 InnoDB: Starting shutdown...
130113 16:28:15 InnoDB: Shutdown completed; log sequence number 2614644
130113 16:28:15 [Note] /usr/local/Cellar/mysql/5.5.25a/bin/mysqld: Shutdown complete
130113 16:28:15 mysqld_safe mysqld from pid file /usr/local/var/mysql/mun07066.local.pid ended
130113 16:28:15 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql
130113 16:28:15 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive
130113 16:28:15 [Warning] One can only use the --user switch if running as root
130113 16:28:15 InnoDB: The InnoDB memory heap is disabled
130113 16:28:15 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130113 16:28:15 InnoDB: Compressed tables use zlib 1.2.5
130113 16:28:15 InnoDB: Initializing buffer pool, size = 128.0M
130113 16:28:15 InnoDB: Completed initialization of buffer pool
130113 16:28:15 InnoDB: highest supported file format is Barracuda.
130113 16:28:16 InnoDB: Waiting for the background threads to start
130113 16:28:17 InnoDB: 1.1.8 started; log sequence number 2614644
130113 16:28:17 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
130113 16:28:17 [Note] - '0.0.0.0' resolves to '0.0.0.0';
130113 16:28:17 [Note] Server socket created on IP: '0.0.0.0'.
130113 16:28:17 [Note] Event Scheduler: Loaded 0 events
130113 16:28:17 [Note] /usr/local/Cellar/mysql/5.5.25a/bin/mysqld: ready for connections.
Version: '5.5.25a' socket: '/tmp/mysql.sock' port: 3306 Source distribution
Related
I Migrate it MySQL Databse MyISAM to InnoDB but still problem facing last 24 hours . Its a wordpress database . When it was MyISAM i face some table crash . then i dump and create a new database and change to innoDB Engine .
150323 17:56:46 InnoDB: Completed initialization of buffer pool
150323 17:56:47 InnoDB: highest supported file format is Barracuda.
150323 17:56:49 InnoDB: Waiting for the background threads to start
150323 17:56:50 InnoDB: 5.5.41 started; log sequence number 739930449
150323 17:56:50 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
150323 17:56:50 [Note] - '127.0.0.1' resolves to '127.0.0.1';
150323 17:56:50 [Note] Server socket created on IP: '127.0.0.1'.
150323 17:56:50 [Note] Event Scheduler: Loaded 0 events
150323 17:56:50 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.41-0+wheezy1-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)
Killed
150323 17:58:55 mysqld_safe Number of processes running now: 0
150323 17:58:55 mysqld_safe mysqld restarted
150323 17:58:55 [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.
150323 17:58:55 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
150323 17:58:55 [Warning] The syntax '--log-slow-queries' is deprecated and will be removed in a future release. Please use '--slow-query-log'/'--slow-query-log-file' instead.
150323 17:58:56 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
150323 17:58:56 [Note] Plugin 'FEDERATED' is disabled.
150323 17:58:56 InnoDB: The InnoDB memory heap is disabled
150323 17:58:56 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150323 17:58:56 InnoDB: Compressed tables use zlib 1.2.7
150323 17:58:56 InnoDB: Using Linux native AIO
150323 17:58:56 InnoDB: Initializing buffer pool, size = 128.0M
150323 17:58:56 InnoDB: Completed initialization of buffer pool
150323 17:58:56 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!
150323 17:58:56 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...
150323 17:58:57 InnoDB: Waiting for the background threads to start
150323 17:58:58 InnoDB: 5.5.41 started; log sequence number 740208077
150323 17:58:58 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
150323 17:58:58 [Note] - '127.0.0.1' resolves to '127.0.0.1';
150323 17:58:58 [Note] Server socket created on IP: '127.0.0.1'.
150323 17:58:58 [Note] Event Scheduler: Loaded 0 events
150323 17:58:58 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.41-0+wheezy1-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)
Smells like you updated versions without running mysql_update.
And several of those [Warning]s smell like an old my.cnf that needs some minor editing.
128M is ok for a "tiny" 2GB of "RAM".
Kindly note that the redmineMySQL services is not running and I am not able to start it. Everytime I try to start I get the following in the server.err log file, the 1067 windows error. Please assist.
Thanks a lot.
140603 10:57:54 [Note] Plugin 'FEDERATED' is disabled.
140603 10:57:54 InnoDB: The InnoDB memory heap is disabled
140603 10:57:54 InnoDB: Mutexes and rw_locks use Windows interlocked functions
140603 10:57:54 InnoDB: Compressed tables use zlib 1.2.3
140603 10:57:54 InnoDB: Initializing buffer pool, size = 128.0M
140603 10:57:54 InnoDB: Completed initialization of buffer pool
140603 10:57:54 InnoDB: highest supported file format is Barracuda.
140603 10:57:54 InnoDB: Waiting for the background threads to start
140603 10:57:55 InnoDB: 1.1.8 started; log sequence number 38540871
140603 10:57:55 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
140603 10:57:55 [Note] - '0.0.0.0' resolves to '0.0.0.0';
140603 10:57:55 [Note] Server socket created on IP: '0.0.0.0'.
140603 10:57:55 [ERROR] Can't start server: Bind on TCP/IP port: No such file or directory
140603 10:57:55 [ERROR] Do you already have another mysqld server running on port: 3306 ?
140603 10:57:55 [ERROR] Aborting
140603 10:57:55 InnoDB: Starting shutdown...
140603 10:57:56 InnoDB: Shutdown completed; log sequence number 38540871
140603 10:57:56 [Note] C:\BitNami\redmine-2.2.2-0\mysql\bin\mysqld.exe: Shutdown complete
I solved the problem by setting the port of the SQLEXPRESS server to a specific value as it was dynamic and reserved port 3306.
My site is on Wordpress and is hosted on a VPS server. The traffic is not much but the database connect error is displayed many times, and then I had to restart MySQL.
I've checked the MySQL error file log. Here is a certain portion of the log.
140310 01:13:26 mysqld_safe mysqld from pid file /var/lib/mysql/server.gosoftnep.com.pid ended
140310 01:13:26 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140310 1:13:26 [Note] Plugin 'FEDERATED' is disabled.
140310 1:13:26 InnoDB: The InnoDB memory heap is disabled
140310 1:13:26 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140310 1:13:26 InnoDB: Compressed tables use zlib 1.2.3
140310 1:13:26 InnoDB: Using Linux native AIO
140310 1:13:26 InnoDB: Initializing buffer pool, size = 128.0M
140310 1:13:26 InnoDB: Completed initialization of buffer pool
140310 1:13:26 InnoDB: highest supported file format is Barracuda.
140310 1:13:26 InnoDB: Waiting for the background threads to start
140310 1:13:27 InnoDB: 5.5.36 started; log sequence number 12082242998
140310 1:13:27 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
140310 1:13:27 [Note] - '0.0.0.0' resolves to '0.0.0.0';
140310 1:13:27 [Note] Server socket created on IP: '0.0.0.0'.
140310 1:13:27 [Note] Event Scheduler: Loaded 0 events
140310 1:13:27 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.36-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
140310 01:13:32 mysqld_safe A mysqld process already exists
140310 5:52:48 [Warning] IP address '58.118.152.8' could not be resolved: Temporary failure in name resolution
140310 12:27:37 mysqld_safe Number of processes running now: 0
140310 12:27:38 mysqld_safe mysqld restarted
140310 12:27:44 [Note] Plugin 'FEDERATED' is disabled.
140310 12:27:45 InnoDB: The InnoDB memory heap is disabled
140310 12:27:45 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140310 12:27:45 InnoDB: Compressed tables use zlib 1.2.3
140310 12:27:45 InnoDB: Using Linux native AIO
140310 12:27:47 InnoDB: Initializing buffer pool, size = 128.0M
140310 12:27:49 InnoDB: Completed initialization of buffer pool
140310 12:27:50 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 12354557593
140310 12:27:52 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: Doing recovery: scanned up to log sequence number 12354588661
140310 12:28:05 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
140310 12:28:07 InnoDB: Waiting for the background threads to start
140310 12:28:08 InnoDB: 5.5.36 started; log sequence number 12354588661
140310 12:28:08 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
140310 12:28:08 [Note] - '0.0.0.0' resolves to '0.0.0.0';
140310 12:28:08 [Note] Server socket created on IP: '0.0.0.0'.
140310 12:28:12 [Note] Event Scheduler: Loaded 0 events
140310 12:28:12 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.36-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
140311 11:51:59 [Warning] IP address '61.160.249.239' could not be resolved: Name or service not known
140312 9:23:21 [Warning] IP address '183.60.107.205' could not be resolved: Name or service not known
140313 0:33:47 [Warning] IP address '221.228.231.59' could not be resolved: Name or service not known
140313 7:33:05 [Warning] IP address '61.147.103.160' could not be resolved: Name or service not known
140313 20:42:42 [Warning] IP address '124.89.32.242' could not be resolved: Name or service not known
140313 23:33:38 mysqld_safe Number of processes running now: 0
140313 23:33:38 mysqld_safe mysqld restarted
140313 23:34:09 [Note] Plugin 'FEDERATED' is disabled.
140313 23:34:14 InnoDB: The InnoDB memory heap is disabled
140313 23:34:14 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140313 23:34:14 InnoDB: Compressed tables use zlib 1.2.3
140313 23:34:14 InnoDB: Using Linux native AIO
140313 23:34:17 InnoDB: Initializing buffer pool, size = 128.0M
140313 23:34:20 InnoDB: Completed initialization of buffer pool
140313 23:34:30 mysqld_safe mysqld from pid file /var/lib/mysql/server.gosoftnep.com.pid ended
140314 02:55:09 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140314 2:55:10 [Note] Plugin 'FEDERATED' is disabled.
140314 2:55:10 InnoDB: The InnoDB memory heap is disabled
140314 2:55:10 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140314 2:55:10 InnoDB: Compressed tables use zlib 1.2.3
140314 2:55:10 InnoDB: Using Linux native AIO
140314 2:55:10 InnoDB: Initializing buffer pool, size = 128.0M
140314 2:55:10 InnoDB: Completed initialization of buffer pool
140314 2:55:10 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 14587500130
140314 2:55:10 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: Doing recovery: scanned up to log sequence number 14587535674
140314 2:55:11 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
140314 2:55:11 InnoDB: Waiting for the background threads to start
140314 2:55:12 InnoDB: 5.5.36 started; log sequence number 14587535674
140314 2:55:12 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
140314 2:55:12 [Note] - '0.0.0.0' resolves to '0.0.0.0';
140314 2:55:12 [Note] Server socket created on IP: '0.0.0.0'.
140314 2:55:12 [Note] Event Scheduler: Loaded 0 events
140314 2:55:12 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.36-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
I do not understand anything about this. Could anyone explain the issue to me or suggest a fix?
After having some trouble with installing a UDF in MySQL (Cannot install MySQL UDF) I'm facing another issue. When executing the function I get a "Lost connection to MySQL server during query" error (errno 2013). Error logging is enabled, but I can't see any error messages in the log file. The my.ini configuration file has the following log properties under mysqld:
log-output=FILE
general-log=0
general_log_file="mysql-general-log-file.log"
slow-query-log=1
slow_query_log_file="mysql-slow-query-log-file.log"
long_query_time=10
log="mysql.log"
# Error Logging.
log-error="mysql-error.log"
log-warnings=2
And here is the mysql-error.log output:
140314 21:29:25 [Note] Plugin 'FEDERATED' is disabled.
140314 21:29:25 InnoDB: The InnoDB memory heap is disabled
140314 21:29:25 InnoDB: Mutexes and rw_locks use Windows interlocked functions
140314 21:29:25 InnoDB: Compressed tables use zlib 1.2.3
140314 21:29:25 InnoDB: Initializing buffer pool, size = 307.0M
140314 21:29:25 InnoDB: Completed initialization of buffer pool
140314 21:29:25 InnoDB: highest supported file format is Barracuda.
140314 21:29:26 InnoDB: Waiting for the background threads to start
140314 21:29:27 InnoDB: 5.5.32 started; log sequence number 9975593
140314 21:29:27 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
140314 21:29:27 [Note] - '0.0.0.0' resolves to '0.0.0.0';
140314 21:29:27 [Note] Server socket created on IP: '0.0.0.0'.
140314 21:29:27 [Note] Event Scheduler: Loaded 0 events
140314 21:29:27 [Note] C:/Program Files/MySQL/MySQL Server 5.5/bin\mysqld: ready for connections.
Version: '5.5.32-log' socket: '' port: 3306 MySQL Community Server (GPL)
I've also tried to debug the UDF itself by adding a few print commands to the code, e.g.
fprintf(stderr, "%s", "Launching JVM\n");
fflush(stderr);
Unfortunately this didn't work either. Which other options do I have to track down the issue?
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
My database (mysql) server keeps crashing / restarting and I am at a loss of what to do. I keep getting the following in my dbname.org.err file:
131205 18:49:05 mysqld_safe mysqld from pid file /var/lib/mysql/les.lesplan.org.pid ended
131205 18:50:12 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
131205 18:50:12 [Note] Plugin 'FEDERATED' is disabled.
131205 18:50:12 InnoDB: The InnoDB memory heap is disabled
131205 18:50:12 InnoDB: Mutexes and rw_locks use GCC atomic builtins
131205 18:50:12 InnoDB: Compressed tables use zlib 1.2.3
131205 18:50:12 InnoDB: Using Linux native AIO
131205 18:50:12 InnoDB: Initializing buffer pool, size = 128.0M
131205 18:50:12 InnoDB: Completed initialization of buffer pool
131205 18:50:12 InnoDB: highest supported file format is Barracuda.
131205 18:50:12 InnoDB: Waiting for the background threads to start
131205 18:50:13 InnoDB: 5.5.32 started; log sequence number 94296300
131205 18:50:13 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
131205 18:50:13 [Note] - '0.0.0.0' resolves to '0.0.0.0';
131205 18:50:13 [Note] Server socket created on IP: '0.0.0.0'.
131205 18:50:14 [Note] Event Scheduler: Loaded 0 events
131205 18:50:14 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.32-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
131206 07:32:53 mysqld_safe Number of processes running now: 0
131206 07:32:53 mysqld_safe mysqld restarted
131206 7:32:54 [Note] Plugin 'FEDERATED' is disabled.
131206 7:32:54 InnoDB: The InnoDB memory heap is disabled
131206 7:32:54 InnoDB: Mutexes and rw_locks use GCC atomic builtins
131206 7:32:54 InnoDB: Compressed tables use zlib 1.2.3
131206 7:32:54 InnoDB: Using Linux native AIO
131206 7:32:54 InnoDB: Initializing buffer pool, size = 128.0M
131206 7:32:54 InnoDB: Completed initialization of buffer pool
131206 7:32:54 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!
131206 7:32:54 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...
131206 7:32:54 InnoDB: Waiting for the background threads to start
131206 7:32:55 InnoDB: 5.5.32 started; log sequence number 94790638
131206 7:32:55 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
131206 7:32:55 [Note] - '0.0.0.0' resolves to '0.0.0.0';
131206 7:32:55 [Note] Server socket created on IP: '0.0.0.0'.
131206 7:32:55 [Note] Event Scheduler: Loaded 0 events
131206 7:32:55 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.32-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
131206 07:33:07 mysqld_safe Number of processes running now: 0
131206 07:33:07 mysqld_safe mysqld restarted
131206 7:33:07 [Note] Plugin 'FEDERATED' is disabled.
131206 7:33:07 InnoDB: The InnoDB memory heap is disabled
131206 7:33:07 InnoDB: Mutexes and rw_locks use GCC atomic builtins
131206 7:33:07 InnoDB: Compressed tables use zlib 1.2.3
131206 7:33:07 InnoDB: Using Linux native AIO
131206 7:33:07 InnoDB: Initializing buffer pool, size = 128.0M
131206 7:33:07 InnoDB: Completed initialization of buffer pool
131206 7:33:07 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!
131206 7:33:07 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...
131206 7:33:08 InnoDB: Waiting for the background threads to start
131206 7:33:09 InnoDB: 5.5.32 started; log sequence number 94790648
131206 7:33:09 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
131206 7:33:09 [Note] - '0.0.0.0' resolves to '0.0.0.0';
131206 7:33:09 [Note] Server socket created on IP: '0.0.0.0'.
131206 7:33:09 [Note] Event Scheduler: Loaded 0 events
131206 7:33:09 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.32-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
131206 07:38:38 mysqld_safe Number of processes running now: 0
131206 07:38:38 mysqld_safe mysqld restarted
131206 7:38:38 [Note] Plugin 'FEDERATED' is disabled.
131206 7:38:38 InnoDB: The InnoDB memory heap is disabled
131206 7:38:38 InnoDB: Mutexes and rw_locks use GCC atomic builtins
131206 7:38:38 InnoDB: Compressed tables use zlib 1.2.3
131206 7:38:38 InnoDB: Using Linux native AIO
131206 7:38:38 InnoDB: Initializing buffer pool, size = 128.0M
131206 7:38:38 InnoDB: Completed initialization of buffer pool
131206 7:38:38 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!
131206 7:38:38 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...
131206 7:38:38 InnoDB: Waiting for the background threads to start
131206 7:38:39 InnoDB: 5.5.32 started; log sequence number 94790674
131206 7:38:39 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
131206 7:38:39 [Note] - '0.0.0.0' resolves to '0.0.0.0';
131206 7:38:39 [Note] Server socket created on IP: '0.0.0.0'.
131206 7:38:39 [Note] Event Scheduler: Loaded 0 events
131206 7:38:39 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.32-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
root#les [/var/lib/mysql]#
The server 'crashes' and restarts at seemingly random intervals although it does happen around 7:30 am (+/- 30 minutes) more then other times it seems.
There are no cron jobs running anywhere near this time.
Any help would be appreciated!
ss
Drop your ib_log files and Put innodb_force_recovery=6 in config file and restart your mysql it will resolve
Turns out that from time to time, memory usage would spike (I'm guessing that this was because of a dramatic spike in apache child processes) and this would cause memory pressure. The out-of-memory killer would choose mysql to close down, because it was (usually) the biggest memory user in the system.
So to fix, I
got more memory
fine tuned Apache to control the number of child processes that were spun up.