[mythtv] [mythtv-commits] Ticket #1319: scheduler is sometimes recording wrong program

henri henri at qais.com
Tue Mar 7 22:28:21 UTC 2006


On 07 Mar 2006, Bruce Markey <bjm at lvcm.com> wrote: 

> MythTV wrote:
> > #1319: scheduler is sometimes recording wrong program
> ...
> >  almost seems to be getting worse (just yesterday it recorded 4 incorrect
> >  problems)
> > 
> >  here is more info using the same example ("teen titans" i tried removing
> >  the recording rule and creating a new one, so the recordid has changed)
> 
> There are two phases in the scheduler; match, which finds programs
> in the listings that match each rule, them place, which fills in
> the schedule and sets the status for each program from match.
> 
> The match results are stored in 'recordmatch':
> 
> mysql> describe recordmatch;
> +-----------+------------------+------+-----+---------+-------+
> | Field     | Type             | Null | Key | Default | Extra |
> +-----------+------------------+------+-----+---------+-------+
> | recordid  | int(10) unsigned | YES  | MUL | NULL    |       |
> | chanid    | int(10) unsigned | YES  |     | NULL    |       |
> | starttime | datetime         | YES  |     | NULL    |       |
> | manualid  | int(10) unsigned | YES  |     | NULL    |       |
> +-----------+------------------+------+-----+---------+-------+
> 
> It doesn't make sense that if there are is a kChannelRecord rule
> that asks for WHERE title='Teen Titans' that it would find chanid
> and starttime for another title.
> 
> Therefore, I suspect that you have a corrupt recordmatch table or
> program table (or a remote possibility of a timezone/timestamp
> issue but with this example that looks less likely).
> 
> Please do the following:
> 
> $ killall mythbackend;
> $ mysqlcheck -ro -u mythtv -pmythtv mythconverg
> $ mysql -u mythtv -pmythtv mythconverg
> mysql> truncate table recordmatch;
> mysql> truncate table program;
> mysql> quit
> $ mythfilldatabase
> $ mysqlcheck -ro -u mythtv -pmythtv mythconverg
> $ mythbackend
> 
> --  bjm

did the above, just clearing recordmatch and running 

mythbackend --testsched 

fixed the upcoming shows.

before doing so i did some digging in recordmatch and in fact some of
the entries for the record rule were pointing at the wrong shows.

my guess is that the schedule is changing but the data in recordmatch
isn't getting cleared? that would be the only explanation that makes
sense. but following the event handling code, it seems that shouldn't
be possible.

i'll keep a manual eye out for the 2 rules that are causing me
problems (one on cartoon network, the other on comedy central). if it
happens again hopefully i'll have more data (program entries from each
day and recordmatch entries from each day)

henri


More information about the mythtv-dev mailing list