Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#18818 - [mysql] Starts But Fails to Restart
Attached to Project:
Arch Linux
Opened by solsTiCe (zebul666) - Wednesday, 24 March 2010, 10:14 GMT
Last edited by Jan de Groot (JGC) - Friday, 28 May 2010, 20:27 GMT
Opened by solsTiCe (zebul666) - Wednesday, 24 March 2010, 10:14 GMT
Last edited by Jan de Groot (JGC) - Friday, 28 May 2010, 20:27 GMT
|
Detailsfrom the mailing-list:
Carlos said: [...] [root@ghost /]# /etc/rc.d/mysqld restart :: Stopping MySQL Server [DONE] :: Starting MySQL Server [FAIL] I can use the 'start' and 'stop' commands for /etc/rc.d/mysqld but 'restart' for some reason fails and this concerns me. Can anyone help me understand what is wrong? Allan said: When you stop MySQL, the kill command completes immediately, while MySQL is still doing shutdown tasks to make sure the database is in a consistent state. As MySQL is still running when you try to start it, it will fail to do so. There's 2 ways to fix this: - use mysqladmin shutdown, needs a user in the database with process privileges, this is the way used by debian - implement a loop that waits for MySQL to shutdown after executing the kill command. This is what the upstream MySQL start/stop script does. /etc/rc.d/mysqld could be fixed then |
This task depends upon
Closed by Jan de Groot (JGC)
Friday, 28 May 2010, 20:27 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 5.1.47
Friday, 28 May 2010, 20:27 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 5.1.47
Comment by Andrea Scarpino (BaSh) -
Wednesday, 24 March 2010, 10:43 GMT
increment the sleep to 5 seconds fixes this. I'll commit this change to trunk ASAP
Comment by Jan de Groot (JGC) -
Wednesday, 24 March 2010, 11:23 GMT
Sleeping for 5 seconds doesn't cut it. If you have a very big transaction log configured, MySQL will take far more than 5 seconds to shutdown.