[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mythtv-users
Subject:    Re: [mythtv-users] scheduling conflict oddity
From:       Jerome Yuzyk <jerome () supernet ! ab ! ca>
Date:       2016-08-31 17:33:53
Message-ID: 9886973.t0P95Sry0p () desk
[Download RAW message or body]

On Tuesday, August 30, 2016 02:28:48 PM Michael T. Dean wrote:
> On 08/30/2016 02:04 PM, Jerome Yuzyk wrote:
> > [0.27.6 on Fedora 20]
> > 
> > I've used MythWeb for my scheduling management from shortly after I started using \
> > Myth almost a decade ago. This morning on the Upcoming Recordings page I see 2 \
> > programs scheduled for the same time with the same tuner, an obvious conflict. \
> > Details for each program show the proper list of what the conflicts would be, but \
> > Upcoming Recordings doesn't acknowledge the conflict like it does all the others. \
> > A conflict between the same 2 shows is flagged a week later though. Both \
> > recording rules are "Record at any time" so there are no override settings. 
> > I've never seen this before - could it signal a DB problem or something?
> > 
> 
> No, all the scheduling is done in memory in the backend.  A broken 
> database wouldn't do anything like that--a broken database could only 
> prevent MythTV from doing any scheduling.  I'm pretty sure it could only 
> be either a misinterpretation of what's to be done (likely 
> misinterpreted by MythWeb--where only one of the 2 is actually being 
> recorded, but MythWeb is showing both as being recorded, so everything 
> will work just fine, but you can't see what's actually happening through 
> MythWeb) or perhaps some really weird data--like your show starts at 
> 8:00:00 and ends at 8:00:30 and then the other show starts at 8:00:30 
> and ends at 8:30:00 or something.
> 
> If MythWeb is misinterpreting things, you would likely see a proper 
> indication of what's happening in mythfrontend's Upcoming Recordings screen.
> 
> If you can (if it's not past the time for the shows to air), please do a:
> 
> mythbackend -v schedule --loglevel debug --printsched
> 
> and put all its output in an attachment or on a pastebin'ed post linked 
> from a reply e-mail and we can look to see what's going on.

Thanks. I waited for another round of mythfilldatabase to see if that corrected it \
but it didn't.

The ZIP is 15k which is probably too big to go through the list but I could send it \
privately.

-- 
A little of Jerome's MythTV World: http://mythtv.bss.ab.ca
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org


[prev in list] [next in list] [prev in thread] [next in thread]