[mythtv-users] Mythbackend losing sql connection on the start of some recordings

Nathan Howell nathan at atdot.ca
Fri Feb 10 01:49:58 UTC 2006


Sasha Z wrote:
> Now I'm not even sure that it's the start of a recording. Here it died
> for no apparent reason:
> 
> stream: start_time: 0.289 duration: 3656.664 bitrate=6478 kb/s
> 2005-12-12 22:02:01.234 New DB connection, total: 3
> 2005-12-12 22:30:45.290 Unknown socket closing
> 2005-12-13 07:00:53.254 adding: mythbe01 as a client (events: 0)
> 2005-12-13 07:00:57.754 adding: mythbe01 as a client (events: 0)
> 2005-12-13 07:00:58.274 adding: mythbe01 as a remote file transfer
> 2005-12-13 07:00:58.446 adding: mythbe01 as a remote file transfer
> 2005-12-13 07:00:58.594 adding: mythbe01 as a remote file transfer
> 2005-12-13 07:00:59.762 adding: mythbe01 as a client (events: 0)
> 2005-12-13 07:01:02.406 adding: mythbe01 as a client (events: 0)
> 2005-12-13 07:01:13.447 adding: mythbe01 as a client (events: 0)
> 2005-12-13 07:01:16.723 DB Error (KickDatabase):
> Query was:
> SELECT NULL;
> Driver error was [2/2006]:
> QMYSQL3: Unable to execute query
> Database error was:
> MySQL server has gone away

So was there a fix for this that I just can't find? I've just upgraded
to mysql 5, and the random disconnections from the db are pretty
annoying. I've seen some references to working around it with timeouts
in mysql, but no decent details. So what's the situation with this
problem? Does it go away with myth > 0.18.1? Where does the actual
problem lie (myth or mysql)? Can anyone sum this issue up? Thanks,

Nathan



More information about the mythtv-users mailing list