[mythtv-users] Mysql timeouts in 0.19 lead to no upcoming recordings

[Eloy A. Paris]

Hi Mike,

On Tue, Mar 07, 2006 at 01:48:27PM -0500, Michael T. Dean wrote:

> I think you missed a few messages as you were getting signed up.  The 
> thread is here 
> http://www.gossamer-threads.com/lists/mythtv/users/187953#187953 .  The 
> second post is from Isaac, then, two hours later, it's followed by me 
> asking if [9233] and [9243] from trunk should be ported to -fixes ( 
> http://www.gossamer-threads.com/lists/mythtv/users/187986#187986 ), 
> followed by David Engel saying they should and he will do it that night 
> (and he did :).

Actually, I did see the entire thread, which is the reason I decided to
re-activate my myth-users subscription ;-)

I even looked at the changesets you mentioned (9233 and 9243), but
missed the part about "If the scheduler was idle for an extended
period of time, it could lose its database connection because the
automatic reconnect logic was being bypassed by keeping a copy of the
MSqlQueryInfo object." My apologies for that.

I think one of the reasons I missed this is that I see that this fix
will make the need to restart mythbackend go away, for sure. However,
I think the connection will still go away during the daily
mythfilldatase run, as I described in my first post to this thread a
couple of hours ago, and this is what I was focused on figuring out.

I think the question still remains... why the connection dies? That the
reconnection logic was broken is a different problem (now resolved.)

In any case, I'll give these fixes a try and report back.

> Note that you can always check out threads--even ones you don't have 
> locally--and search the lists with the archive at 
> http://www.gossamer-threads.com/lists/mythtv/ .

Oh sure, I do this all the time ;-)

Thanks for the help and comments.

Cheers,

Eloy.-