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

Michael T. Dean mtdean at thirdcontact.com
Wed Mar 8 04:50:45 UTC 2006


On 03/07/06 22:43, Bruce Markey wrote:

>It would be "Reschedule requested for id -1.". Look in the log
>to see if this message appear when mfdb ran the look to see if
>the scheduler run succeeded or of there is a DB error or connection
>failure:
>
>2006-03-07 01:25:10.266 MainServer::HandleAnnounce Monitor
>2006-03-07 01:25:10.272 adding: nordtv as a client (events: 0)
>2006-03-07 01:25:10.466 Reschedule requested for id -1.
>2006-03-07 01:25:10.507 Unknown socket closing
>2006-03-07 01:25:15.189 Scheduled 301 items in 4.7 = 3.79 match + 0.91 place
>
>Mfdb connected from "nordtv", requested the reschedule then closed.
>The high "match" time is rematching everything.
>  
>

I hadn't been seeing the "Reschedule requested for id -1."--I explicitly 
looked for it.  As a matter of fact, that's what caused me to realize 
that I had a problem with my videosource configuration for my "External" 
source (which didn't have a grabber).  I initially set it to /bin/true 
(when we had the ability to edit the combobox), but I had since changed 
it (I think I failed to notice the change when I went into the Input 
Connections page of mythtv-setup one time).  So, after you (Bruce) 
mentioned the lack of a method for setting up a videosource with no 
grabber in the GUI, I created the patch in #1425 and--at the same 
time--fixed my configuration.

I gave up hunting the mfdb reschedule issue because my invalid 
configuration was causing mfdb errors, so I didn't have valid data to 
use in diagnosing the problem.  Now, having been running with that patch 
for several days (and, therefore, having run mfdb several times), I can 
say that I am definitely seeing "Reschedule requested for id -1."  So it 
seems that the entire issue on my side was due to the improper 
configuration for my second videosource's grabber (which caused 
fillData() to return false).  Now, having seen the reschedule requests 
succeeding, I'm confident that the issue will not recur.

So, henri, if you're getting failures in mfdb, you need to determine 
why.  With a proper configuration, you shouldn't have any failures, so 
the reschedule request should succeed.  If you need help, feel free to 
post your mfdb log to the -users list.  If not, it may be related to the 
connection issues...

However, this issue begs the question of whether it may not be wise to 
request a reschedule even if mfdb has failures.  Although fixing the 
underlying cause is the right course of action, there's something to be 
said for succeeding in the face of failure (but it may mask 
configuration problems, so...).  Even if mfdb isn't changed, having seen 
this issue, I'll be able to help the next person to see it...  ;)

Mike


More information about the mythtv-dev mailing list