[mythtv-users] MySQL related BE deadlocks - collective wisdom needed

[Michael T. Dean]

On 08/26/2011 07:31 AM, Brian J. Murrell wrote:
> On 11-08-26 04:39 AM, warpme wrote:
>> Pls look for "MySQL reconnected successfully" string in be logs.
>> In last 12 days, 600 rec I had 2 of them. Both exactly at the same:
>>
>> 1st:
>> 2011-08-15 06:00:01.626423 I  Tuning recording: "Jak to jest zrobione?":"Jak to jest zrobione? (How It's Made), odc. 2": channel 15315 on cardid 5, sourceid 8
>> 2011-08-15 06:00:01.627545 I  MySQL reconnected successfully
>>
>> 2nd:
>> 2011-08-22 06:00:01.561354 I  Tuning recording: "Jak to jest zrobione?: Ołówki/Recykling metalu/Kawa": channel 15315 on cardid 5, sourceid 8
>> 2011-08-22 06:00:01.562367 I  MySQL reconnected successfully
> Interesting.  I have no such pattern:
>
> 2011-08-09 16:00:06.923299 I [20242/20259] Scheduler mythdbcon.cpp:234
> (Reconnect) - MySQL reconnected successfully
> 2011-08-11 08:59:59.367130 I [1559/2010] Scheduler mythdbcon.cpp:234
> (Reconnect) - MySQL reconnected successfully
> 2011-08-05 18:08:22.311 MySQL reconnected successfully
> 2011-08-05 18:08:31.159 MySQL reconnected successfully
> 2011-08-05 19:59:01.659 MySQL reconnected successfully
> 2011-08-06 17:43:39.218 MySQL reconnected successfully
> 2011-08-06 17:43:39.612 MySQL reconnected successfully
> 2011-08-08 16:29:41.669276 I [1505/2283] Scheduler mythdbcon.cpp:234
> (Reconnect) - MySQL reconnected successfully
>

warpme, maybe you have a database- or I/O-intensive cron job occurring 
once a week at 6:00am on Monday that causes problems?

Mike