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 On 12/12/05, Sasha Z <[EMAIL PROTECTED]> wrote: > Another update, it only seems to be unable to connect to the schedules > tables... specifically the upcoming recordings. Everything else seems > to work just fine, listings, recorded programs, job queue history, > etc. > > What could possibly be going on? > > On 12/11/05, Sasha Z <[EMAIL PROTECTED]> wrote: > > OK, it seems to really happen at two times. One right at the start of > > a recording, and again at the end of (some) listings updates. > > > > On 12/9/05, Sasha Z <[EMAIL PROTECTED]> wrote: > > > Anybody have further information on this? (ie, bump) > > > > > > > On 12/3/05, Michael Eldridge <[EMAIL PROTECTED]> wrote: > > > > > > > > > I have to restart the backend about once a day for things to work > > > > > properly. Should we open a ticket about this issue? > > > > > > > > > > On 11/28/05, Sasha Z <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > I seem to be losing the database connection before some recordings, > > > > > > but not all. Mysql is *not* dying, and I am able to open and > > > > > > manipulate the database via the mysql console without trouble. > > > > > > Mythbackend itself isn't crashing either, it's just no longer able > > > > > > to > > > > > > communicate with the database. > > > > > > > > > > _______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
