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
Mathias:
Spectacular idea. I just manually tried it on my test system that i've been
using to investigate this bug. It solves the problems entirely.
On Mon, May 11, 2009 at 22:04, Mathias Gug wrote:
> Here is another way to fix the issue: add a wait to the trap:
>
> -+trap '/usr/bin/mysqladmi
Hi Will,
On Mon, May 11, 2009 at 01:35:31AM -, Will Uther wrote:
> 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 11:02:55 willvo ntpd[3721]: ntpd exiting on signal 1
There are two problems at stake here actually:
1) something is sending HUP to mysqld_safe. That's not been determined
yet. Clearly it's some root process that is doing it. It can't be
mythbackend because it doesn't run as root.
2) mysqld_safe is not properly handling the HUP. When the trap g
