[mythtv-users] Suddenly all Upcoming Recordings vanished; DB Error?

[Jos Hoekstra]

Op 25-10-2012 3:37, Justin Smith schreef:
> Hi,
>
> I upgraded to 0.26 a couple of weeks ago and all has been well.
>
> Until last night. I noticed that a show I was expecting to record was
> not recording. A quick check showed that the guide data all appeared
> as per normal, and that all recording rules were still present, but
> the upcoming recording list was empty (normally has many entries). The
> scheduler was no longer matching recording rules to the guide data for
> some reason.
>
> I restarted the backend but that didn't change anything.
>
> Checking the backend log, I found the following at around the time the
> problem started:
>
> Oct 24 19:20:02 pooper mythlogserver: mythbackend[2068]: E Scheduler
> mythdb.cpp:183 (DBError) DB Error (AddNewRecords):#012Query
> was:#012SELECT     c.chanid,         c.sourceid,
> p.starttime,           p.endtime,        p.title,
> p.subtitle,            p.description,    c.channum,
> c.callsign,            c.name,           oldrecduplicate,
> p.category,            sched_temp_record.recpriority,
> sched_temp_record.dupin,   recduplicate,          findduplicate,
> sched_temp_record.type,        sched_temp_record.recordid,
> p.starttime - INTERVAL sched_temp_record.startoffset     minute AS
> recstartts,     p.endtime + INTERVAL sched_temp_record.endoffset
> minute AS recendts,
> p.previouslyshown,     sched_temp_record.recgroup,
> sched_temp_record.dupmethod,  c.commmethod,
> capturecard.cardid, cardinput.cardinputid,p.seriesid,
> p.programid,       sched_temp_record.inetref,    p.category_type,
>   p.airdate,         p.stars,             p.originalairdate,
> sched_temp_record.inactive, sched_temp_record.parentid,
> recordmatch.findid,     sched_temp_record.playgroup,
> oldrecstatus.recstatus,     oldrecstatus.reactivate, p.videoprop+0,
>       p.subtitletypes+0, p.audioprop+0,
> sched_temp_record.storagegroup,     capturecard.hostname,
> recordmatch.oldrecstatus,
> sched_temp_record.avg_delay,     oldrecstatus.future,
> cardinput.schedorder, c.recpriority + cardinput.recpriority +
> (cardinput.cardinputid = sched_temp_record.prefinput) * 2 AS
> powerpriority FROM recordmatch INNER JOIN sched_temp_record ON
> (recordmatch.recordid = sched_temp_record.recordid) INNER JOIN program
> AS p ON ( recordmatch.chanid    = p.chanid    AND
> recordmatch.starttime = p.starttime AND      recordmatch.manualid  =
> p.manualid ) INNER JOIN channel AS c ON ( c.chanid = p.chanid ) INNER
> JOIN cardinput ON (c.sourceid = cardinput.sourceid) INNER JOIN
> capturecard ON (capturecard.cardid = cardinpu
>
>
> I also noticed an error from the DVBRead - but this may be an
> independent issue - does this mean a rescan is required?
>
> Oct 24 19:55:13 pooper mythlogserver: mythbackend[2068]: E DVBRead
> dtvsignalmonitor.cpp:321 (HandlePAT)
> DTVSM(/dev/dvb/adapter0/frontend0): Program #1669 not found in
> PAT!#012Program Association S
> ection#012 PSIP tableID(0x0) length(41) extension(0x261)#012
> version(2) current(1) section(0) last_section(0)#012      tsid(609)
> programCount(8)#012  program number     0 has PID 0x0010#012
> program number   736 has PID 0x0102#012  program number   737 has PID
> 0x0100#012  program number   738 has PID 0x0101#012  program number
> 739 has PID 0x0103#012  program number   740 has PID 0x0
> 104#012  program number   742 has PID 0x0105#012  program number   743
> has PID 0x0106
>
>
> Does anyone have any suggestions on how to debug or fix this problem?
>
>
> Cheers,
> Justin.
> _______________________________________________
>


Your capturecard might not be present anymore or the rootdisk might be 
(almost) full, the latter happened to me today, clearing it up made 
upcoming recordings visible.