Red Hat Bugzilla – Bug 842977
mysql shuts itself down approx every 24 hrs
Last modified: 2015-05-14 18:56:58 EDT
Approximately between 12:15 and 13:15 EDT every day mysql appears to shut itself down.
Version-Release number of selected component (if applicable): mysql-5.1
How reproducible: Always on my app
Steps to Reproduce:
1. Just wait :)
Additional info: This is the output that appears in the log files each day:
120724 13:16:20 [Note] /usr/libexec/mysqld: Normal shutdown
120724 13:16:20 [Note] Event Scheduler: Purging the queue. 0 events
120724 13:16:20 InnoDB: Starting shutdown...
120724 13:16:20 InnoDB: Shutdown completed; log sequence number 0 44233
120724 13:16:20 [Note] /usr/libexec/mysqld: Shutdown complete
120724 13:16:20 mysqld_safe mysqld from pid file /var/lib/stickshift/90146f1adc384f7e82fdf0214b92f2bc//mysql-5.1/pid/mysql.pid ended
My app is at lab-iksystems. Please let me know if I can provide any further info for you.
MySQL shutdown again at 13:50 today:
120725 13:50:29 [Note] /usr/libexec/mysqld: Normal shutdown
120725 13:50:29 [Note] Event Scheduler: Purging the queue. 0 events
120725 13:50:29 InnoDB: Starting shutdown...
120725 13:50:31 InnoDB: Shutdown completed; log sequence number 0 44233
120725 13:50:31 [Note] /usr/libexec/mysqld: Shutdown complete
120725 13:50:31 mysqld_safe mysqld from pid file /var/lib/stickshift/90146f1adc384f7e82fdf0214b92f2bc//mysql-5.1/pid/mysql.pid ended
The root cause of the issue was found and will be corrected in the next release.
A workaround was put in place on your mysql gear which should prevent shutdown until the next release is put into production.
Verified this bug on devenv_1920, and PASSED.
just to mention that this issue has re-occured on my box. Is this due to a new release overwriting your update?
Sorry about that - the permanent fix got delayed going to production. It should happen in the next few days.
Hitting the following URL will give your mysql instance 14 more days before the idle gear detection sees it again.
My apologies again for the hassle.
...forgot to mention, I've already re-awakened it.
lol - cheers Rob. Apache on the web gear had gone down as well - not sure if that was related to hitting that URL, but I've started it back up again. I'll keep an eye on it next couple of days...