[mythtv-users] MythBackend Suddenly swamping CPU on system

[John]

On 01/07/12 02:36, Tom Hayward wrote:
> On Sat, Jun 30, 2012 at 7:28 PM, Chris Edwards<chris at chris-edwards.org>  wrote:
>> On 1 July 2012 11:25, Ben Kamen<bkamen at benjammin.net>  wrote:
>>> And I'm not recording anything or running the frontend on this machine or
>>> any connected to it...
>> <snip>
>>> This started around 7pm CDT for me.
>> I'm seeing the same thing here. I don't know when 7pm CDT is, but I
>> saw it (here in eastern Australia) at 10am, which is midnight GMT,
>> which is when a leap second was added, so I'd say that was the problem
>> (9:59:60 being the time for a second). My mysql has been misbehaving
>> ever since.
> I had the same issue starting at the same time, but a reboot seems to
> have solved it (restarting just mythbackend didn't help).
>
> Tom
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users
>
Thanks for posting this, good to know what happened. Bit of googling 
shows that this happened to a lot of people.


[I was woken up by  a warbling noise in the early hours, found my 
Backend overheat alarm ( set very conservatively) had started because 
the cpu had been running at 100% on both cores for too long. Mythbackend 
restarts didn't help, killed mysql and rebooted, and then mythbackend 
wouldn't start because it couldn't connect to database. Ended up 
shutting it all down for the first time in months :-(, too sleepy to 
fault find.

Thought this morning would be filled with pain, but found that the 
network interface had changed on reboot, and that was all that was wrong 
with database access :-). ]