MySQL dead after latest update

Simon Andrews simon.andrews at bbsrc.ac.uk
Thu Jul 21 08:08:38 UTC 2005


Just a quick word of warning, on two of our MySQL servers last nights 
update caused the mysql daemon to fail to restart.  The log says:

050721  9:03:35 [Note] /usr/libexec/mysqld: Normal shutdown

050721  9:03:35  InnoDB: Starting shutdown...
050721  9:03:38  InnoDB: Shutdown completed; log sequence number 0 43654
050721  9:03:38 [Note] /usr/libexec/mysqld: Shutdown complete


Memory status:
Non-mmapped space allocated from system: 6692864
Number of free chunks:                   19
Number of fastbin blocks:                0
Number of mmapped regions:               12
Space in mmapped regions:                37273600
Maximum total allocated space:           0
Space available in freed fastbin blocks: 0
Total allocated space:                   5836264
Total free space:                        856600
Top-most, releasable space:              115400
Estimated memory (with thread stack):    43966464

A mysqld process already exists at  Thu Jul 21 09:03:37 BST 2005
050721 09:03:38  mysqld ended

Which makes it look like the restart was attempted whilst some remnant 
of the old server was still shutting down.

In both cases a simple restart of the service got everything running again.

Simon.




More information about the fedora-list mailing list