Description of problem: The Red Hat MySQL initscript stop part does: /bin/kill `cat /var/run/mysqld/mysqld.pid then continues on its merry way not waiting for the server to shutdown before returning. If this followed rapidly by a start (ie restart was called), then mysql does not start as the previous server has not completed the shutdown. Version-Release number of selected component (if applicable): mysql-3.23.58-1.9 (also on RHL 8 & 7.3 affected) How reproducible: Most of our MySQL servers did not come back up after recent upgrades via RHN. Steps to Reproduce: 1. On a busy MySQL server run: service mysqld restart OR On many of our RHL machines push mysql update from RHN (and let rpm do the service mysqld condrestart from postinstall script) 2. Watch service get killed, but not restarted. 3. Writh around in pain as servers need to have MySQL started on. Actual results: MySQL does not come after package upgrade. Expected results: MySQL restart to work. Additional info: Initscript stop function should run mysqladmin shutdown and also loop with a sleep waiting for pid file to disappear before returning.
This is a known problem and we have a fix for it but I haven't had time to put it in. Anyway, this is a duplicate of bug #58732. It should be in by end of the month. *** This bug has been marked as a duplicate of 58732 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.