[Bug 326768] [NEW] mysql thinks it has crashed when it hasn't

2009-02-07 Thread Will Uther
Public bug reported: Binary package hint: mysql-server-5.0 I'm running mythtv on jaunty with mysql-server-5.0 version 5.1.30really5.0.75-0ubuntu5. During boot mysql starts, then mythtv starts, then mysql restarts and mythtv gets confused. What seems to be happening is that line 387 (or 389?)

[Bug 326768] Re: mysql thinks it has crashed when it hasn't

2009-04-11 Thread Will Uther
Yeah - it looks to me like Bug 358173 is the same bug. I find it very strange that this bug only affects mythbackend (all the possible duplicates seem to reference mythtv). I suspect that it is doing something strange. I reported a mysql bug because I figured that the mysql server shouldn't

[Bug 326768] Re: mysql thinks it has crashed when it hasn't

2009-04-20 Thread Will Uther
Barney - could you clarify your comment for me? You say Running mythtv-setup, removing all encoder cards and adding them again fixes this. Is this a permanent fix, or does the problem recur if you reboot? If this is only a fix for that boot, there are easier ones. Anything that causes

[Bug 326768] Re: mysqld_safe thinks mysqld has crashed when it hasn't

2009-05-10 Thread Will Uther
I patched mysqld_safe directly based on Mario's diff (and replace the wait that I had removed). This fixes the problem for me. I also looked in the logs to see what was happening on boot with the change and I noticed: May 10 11:02:55 willvo sshd[2981]: Received signal 15; terminating. May 10

Re: [Bug 326768] Re: mysqld_safe thinks mysqld has crashed when it hasn't

2009-05-11 Thread Will Uther
On 12/05/2009, at 2:16 AM, Mathias Gug wrote: Thanks for figuring this out. This is probably the root cause of the issue. I've seen similar behavior with sshd - could you describe your network configuration? Are you using network-manager or /etc/network/intrefaces? Are you using a static

[Bug 326768] Re: mysqld_safe thinks mysqld has crashed when it hasn't

2009-05-12 Thread Will Uther
I just tried Marc's signal tracker: Here is the output after boot: Executing (/usr/bin/mysqld_safe_real ) signo: [1], errno: [0], code: [128], pid: [0], uid: [0] It looks like a code of 0x80 corresponds to a code of SI_KERNEL. What does the kernel have against mysqld_safe? -- mysqld_safe