We already know that the bug is triggered by something that restart the mysql process (On my server it sometimes even occurs when I run /etc/init.d/mysql restart)
2009/6/3 NickA <sdnick...@gmail.com>: > I woke up this morning and found I was experiencing this issue on 9.04 > (final, standard desktop version). I also saw two instances of > mysql_safe with one eating all the CPU. I installed mytop but didn't > see anything happening, and /etc/init.d/mysql restart did not help. > Both mysql.log and mysql.err were empty files. > > The only mysql database on this box is for Amarok 1.4, and amarok was not > running at the time. Last night the problem was definitely not occurring, > and I hadn't logged into this system for a couple days prior to that (the box > was restarted on Sunday). The commands I performed last night were: > an apt-get update > apt-get upgrade > apt-get install prelink > prelink -amR > > I just went through y dpkg.log, and mysql was updated last night, so I'm > willing to bet the bug was somehow triggered by that process. > > -- > mysqd_safe high cpu usage > https://bugs.launchpad.net/bugs/105457 > You received this bug notification because you are a direct subscriber > of the bug. > -- mysqd_safe high cpu usage https://bugs.launchpad.net/bugs/105457 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
