[mythtv-users] Recording unavailable , zero length at incorrect time

Sean Salisbury sean_salisbury at hotmail.com
Tue Dec 14 08:16:46 UTC 2010




> Date: Mon, 13 Dec 2010 10:12:37 +0000
> From: knowledgejunkie at gmail.com
> To: mythtv-users at mythtv.org
> Subject: Re: [mythtv-users] Recording unavailable ,	zero length at incorrect time
> 
> On 13 December 2010 09:48, Sean Salisbury <sean_salisbury at hotmail.com> wrote:
> > I recently updated my myth backend and frontends to 0.24 via mythbuntu repos
> > and have started experiencing unavailable recordings. Having looked through
> > the mailing lists and tried various suggested methods (use quick tuning,
> > delete cards in setup and start again) no solution has been found.
> >
> > To try and track down any errors I enabled backend logging to try and find
> > an obvious problem however I am now confused.
> >
> > Last night I had "Mad Max" scheduled to record at 22:00 and the backend logs
> > shows this nicely
> >
> >
> > 2010-12-12 21:57:30.342 Scheduler: Update next_record for 115
> > --- print list start ---
> > Title - Subtitle                    Ch Station Day Start  End   S C I  T N
> > Pri
> > Mad Max                              24 ITV4    12 22:00-23:55  1 3 1  S 3 1
> > From Hell                            31 FIVE US 13 22:00-00:35  1 3 1  S 3 1
> > Severance                             1 BBC ONE 17 23:30-01:00  1 3 1  S 3 1
> > ---  print list end  ---
> > 2010-12-12 21:57:30.345 Scheduled 3 items in 0.1 = 0.00 match + 0.06 place
> >
> >
> > However the next mention of recording of Mad Max comes nearly 6 hours late
> > with the following from the backend log
> >
> >
> > 2010-12-13 03:47:08.356 TVRec(4): ASK_RECORDING 4 29 0 0
> > 2010-12-13 03:47:08.357 MythEvent: ASK_RECORDING 4 29 0 0
> > 2010-12-13 03:47:08.358 MythSocket(88e4240:41): write -> 41 589
> > BACKEND_MESSAGE[]:[]ASK_RECORDING 4 29 0 0[]:[]Mad Max[]:[][]:[]N...
> > 2010-12-13 03:47:08.485 MythEvent: SYSTEM_EVENT REC_PENDING SECS -20829
> > CARDID 3 CHANID 1024 STARTTIME 2010-12-12T22:00:00 SENDER elliot
> 
> For some reason, your Mad Max rule was set to start early by -20829
> seconds (note the negative sign) - this has the effect of starting the
> recording a little over 5:45 hours _late_ due to the negative timing,
> which agrees with the actual recording.
> 
> Make sure you have not got a ridiculous system-wide global pre-roll
> setting or per-rule start early setting in effect. If these are both
> set to zero, I'd run the optimize_db.pl script to check the integrity
> of the MythTV database.
> 
> Cheers,
> Nick
> 
> -- 
> Nick Morrott
> 
> MythTV Official wiki: http://mythtv.org/wiki/
> MythTV users list archive: http://www.gossamer-threads.com/lists/mythtv/users
> 
> "An investment in knowledge always pays the best interest." - Benjamin Franklin
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


After checking settings, running optimize script more failures occured last night, one recording starting 90 mins late and one not recording at all (or maybe not yet).

Is there an example of sql commands I could use to query the offset for all upcoming recordings to see if its affecting all recordings.

Also noticed the following mysql error before recording at the wrong time last night 

2010-12-13 23:31:15.693 Error preparing query: SELECT value  FROM codecparams WHERE profile = :WHEREPROFILE AND name = :WHERENAME
2010-12-13 23:31:15.693 Driver error was [2/2013]:
QMYSQL3: Unable to prepare statement
Database error was:
Lost connection to MySQL server during query

2010-12-13 23:31:15.695 MySQL reconnected successfully
2010-12-13 23:31:15.696 DB Error (SimpleDBStorage::Load()):
Query was:
SELECT value  FROM codecparams WHERE profile = :WHEREPROFILE AND name = :WHERENAME
Bindings were:
:WHERENAME=recordingtype, :WHEREPROFILE=18
Driver error was [2/1064]:
QMYSQL: Unable to execute query
Database error was:
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ':WHEREPROFILE AND name = :WHERENAME' at line 1

QMYSQLResult::cleanup: unable to free statement handle
QMYSQLResult::cleanup: unable to free statement handle


So it looks like I've got a database/query/version problem somewhere, any suggestions as I will soon be in trouble for no recordings on the run up to christmas.

Many thanks

Sean


 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20101214/2dea74c6/attachment.htm>


More information about the mythtv-users mailing list