100% cpu usage of mysqld_safe after upgrade mysql 5.0 to mariadb 5.2.2

Bug #662024 reported by Henrik Ingo on 2010-10-17
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

I upgraded yesterday Kubuntu Jaunty (386) from the original MySQL 5.0.x to MariaDB 5.2.2. I just installed the debs onto a running mysql.

After the upgrade mysqld_safe is using up 100% of one cpu core (ie 48-50% on my 2 core system). After investigation it turns out there is another mysqld_safe and mysqld running just fine and the one that is using up all cpu has no child mysqld process. So I would guess it is the old mysqld_safe from the uninstalled mysql 5.0. and it is busy trying to restart the old mysqld that doesn't exist.

There are similar Jaunty bugs where mysqld_safe is left hanging after upgrading to a newer mysql. So this is possibly not MariaDB related and also might not be possible to fix from MariaDB, if it is a bug in the old mysqld_safe.

Suggested fix:
either: nothing, this is a mysql 5.0 bug.
or: kill mysqld_safe when installing a newer mariadb, however, this is a bad idea if there are multiple mysqld/mysqld_safe processes running. (One could possibly kill mysqld_safe if it has no child process.)

After killing the mysqld_safe process gone astray, the problem doesn't seem to come back.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers