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 thin
I just tried manually adding Mathias' latest change. That also seems to
solve the problem for me. (This was not a full re-install with that
patch - just me with vim reverting the old patch and adding that patch.
I hope I haven't made any mistakes :)
--
mysqld_safe thinks mysqld has crashed when
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
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
I thought I'd list what I discovered when originally looking at this
bug. Much of this is mythtv specific. I'm currently of the opinion
that there are issues in both mythtv and mysql, with the mythtv strange
behaviour tickling a mysql issue.
On a problematic boot, mysql starts normally. This me
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 mythbac
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 beha
Without the fix I mentioned in the original report, mysql gets restarted
once. Obviously mysqld_safe uses some CPU to do this (it will do one
iteration of the loop at the bottom of the script). mysqld_safe is not
looping and restarting mysql multiple times, which is, I think, the
behaviour you we
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?) of
