Red Hat Bugzilla – Bug 82007
crash on upgrade to mysql-server-3.23.54a-3.72
Last modified: 2007-04-18 12:50:03 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003
Description of problem:
After an up2date upgrade, client programs were not able to connect to the
mysql-server. This happened on two machines (both running RedHat Linux 7.2) at
the same time. After manually killing all mysql processes (the
/etc/init.d/mysqld script could not stop them, because
/var/run/mysqld/mysqld.pid was non-existant) mysqld could be started again, and
is functioning now (20 minutes later).
Version-Release number of selected component (if applicable): 3.23.54a-3.72
Before restarting mysqld, the 'top' command did not function, but returned a
'floating point exception'. The 'ps' command did function, so I could verify
that mysqld was indeed running. When mysql is running again, 'top' also works.
Ok... tested this. I shut down the mysqld service, did an up2date on my 7.2
machine, restarted the mysqld service and all ran fine. My mysql clients
were able to connect and extract data from the database. There was no problem
with top either.