[mythtv-users] mythfilldatabase with EIT data

[Philip Nourse]

On 07/20/2009 06:58 PM, Richard Morton wrote:
>
> On Jul 20, 2009 11:28 PM, "Michael T. Dean" wrote:
>
>> That sounds a lot like your backend lost its connections to the MySQL 
>> server.  When you restarted the backend, it got new connections, so 
>> it was working fine.
>>
>> If it happens every day (or every 8 hours), it probably means that 
>> your backend is unable to detect dead connections or unable to 
>> reconnect.  You can set MySQL's wait_timeout and interactive_timeout 
>> in /etc/mysql/mysql.ini (or wherever your distro puts it) to small 
>> values (like 120 --2mins) to test if the backend recovers.  They 
>> default to 8hrs worth of seconds (though your distro may have 
>> modified the defaults).
>>
>> I've heard reports that some versions of MySQL/MySQL libs/Qt-MySQL 
>> drivers/something cause huge delays when Myth needs to 
>> reconnect--possibly long enough that Myth gives up.
>
> I thought that but the epg is populated. Isn't that also fetched by 
> mythweb etc from the db?
>

>The Scheduler uses its own distinct MySQL connections (which aren't 
>commingled with the others).  And, Myth uses a bunch of different 
>connections in a pool, so it's possible that some were timed out and 
>others weren't.

>Mike


I have also seen this issue happen.  I suspect what is happening is that
mythtv is running into an error after it has deleted the schedule and is
about to re-populate.  I have been meaning to post a bug but I haven't seen
it since.  The solution would be to open / commit the transaction around the
entire delete/re-populate routine.