Red Hat Bugzilla – Bug 58732
/etc/init.d/mysqld doesn't wait for server to start
Last modified: 2007-04-18 12:39:09 EDT
From Bugzilla Helper: User-Agent: Mozilla/5.0 Galeon/1.0.2 (X11; Linux i686; U;) Gecko/20011224 Description of problem: one can run /etc/init.d/mysqld start and since it backgrounds the safe_mysqld process and doesn't do any mysqladmin pinging, the server isn't guaranteed to have started. this causes problems if steps soon after the server (re)start depend upon it. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. run /etc/init.d/mysqld restart 2. try to make a mysql query right away 3. Actual Results: the client failed to find the socket by which to communicate with the server. Expected Results: step (1) should have waited for the server to come online before returning. then (2) would succeed. Additional info: the debian start script (/etc/init.d/mysql in the mysql-server package) does this rationally, by mysqladmin pinging a number of times until the server comes online or dying after a timeout.
Seems like a good enhancement.
Kim, can you handle this please. Have the script loop five times with a 1 second hold. Break out of the loop if the mysqladmin ping succeeds, bail otherwise.
*** Bug 106833 has been marked as a duplicate of this bug. ***
Fixed in rawhide. We chose to wait for a max of tens seconds, pinging every second.
An errata has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2004-569.html