Mailing List Archive: MythTV: Users

0.26 recording rules - "not listed"

Index | Next | Previous | View Threaded

sgtbundy at gmail

Aug 19, 2012, 5:46 AM

Post #1 of 8 (604 views)
Permalink

0.26 recording rules - "not listed"

Picked up a slightly annoying bug with 0.26 tonight - my wife was
watching a show and decided to manually record the following program in
case this one ran overtime. She went to the guide, picked the next show
and did a manual record. Instantly the two other shows in scheduled to
be recorded tonight disappeared from upcoming recordings.

If I look at the upcoming recordings there is nothing there to say they
are in conflict or anything, there are plenty of free tuners and it
seemed happy to record it before.
If I pick the show in the guide it has nothing to say it wants to record it.
If I do a manual record in on the show, it shows up in upcoming
recordings and the guide as "Not Listed" (WTF does that mean, yes it is,
its right there).
If I look at the recording rules it is there and I see nothing that
would prevent it recording, and preview changes shows it as "this will
be recorded" but it never appears in upcoming recordings.

Viewing via the frontend of mythweb seem to show nothing different, and
I can find no errors or messages in the logs relating to this.

Any ideas what is going on here? The only work around seems to be to
switch to the show when it starts and hit record.

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

sgtbundy at gmail

Aug 19, 2012, 5:54 AM

Post #2 of 8 (580 views)
Permalink

Re: 0.26 recording rules - "not listed" [In reply to]

On 19/08/2012 10:46 PM, Adrian Saul wrote:
>
> Picked up a slightly annoying bug with 0.26 tonight - my wife was
> watching a show and decided to manually record the following program
> in case this one ran overtime. She went to the guide, picked the next
> show and did a manual record. Instantly the two other shows in
> scheduled to be recorded tonight disappeared from upcoming recordings.
>
> If I look at the upcoming recordings there is nothing there to say
> they are in conflict or anything, there are plenty of free tuners and
> it seemed happy to record it before.
> If I pick the show in the guide it has nothing to say it wants to
> record it.
> If I do a manual record in on the show, it shows up in upcoming
> recordings and the guide as "Not Listed" (WTF does that mean, yes it
> is, its right there).
> If I look at the recording rules it is there and I see nothing that
> would prevent it recording, and preview changes shows it as "this will
> be recorded" but it never appears in upcoming recordings.
>
> Viewing via the frontend of mythweb seem to show nothing different,
> and I can find no errors or messages in the logs relating to this.
>
> Any ideas what is going on here? The only work around seems to be to
> switch to the show when it starts and hit record.
>

Actually I think this is related to the new timezone setup in 0.26 - if
I look at the recording rule in the database, the last scheduled
recording times etc are all local time, but the view in the frontend
shows the last recorded at Aug 15 07:33AM when in fact it was Aug 14
09:33PM (I am GMT+10, so it seems to think the times in the DB are GMT
not AEST).

Also the frontend seems to think the show is scheduled for 10AM-10AM in
the rules overview. The rule in the database has the startdate and
enddate of today at 0:00, so +10 would make it be 10am.

I am not sure this should really affect it, because it is a "record any
time on this channel" rule, and nothing to do with timeslots etc.

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

carl.lewis at dpipwe

Aug 20, 2012, 12:11 AM

Post #3 of 8 (566 views)
Permalink

Re: 0.26 recording rules - "not listed" [In reply to]

On 19/08/12 22:54, Adrian Saul wrote:
> On 19/08/2012 10:46 PM, Adrian Saul wrote:
>>
>> Picked up a slightly annoying bug with 0.26 tonight - my wife was watching a show and decided to manually record the following program in case this one ran overtime. She went to the guide, picked
>> the next show and did a manual record. Instantly the two other shows in scheduled to be recorded tonight disappeared from upcoming recordings.
>>
>> If I look at the upcoming recordings there is nothing there to say they are in conflict or anything, there are plenty of free tuners and it seemed happy to record it before.
>> If I pick the show in the guide it has nothing to say it wants to record it.
>> If I do a manual record in on the show, it shows up in upcoming recordings and the guide as "Not Listed" (WTF does that mean, yes it is, its right there).
>> If I look at the recording rules it is there and I see nothing that would prevent it recording, and preview changes shows it as "this will be recorded" but it never appears in upcoming recordings.
>>
>> Viewing via the frontend of mythweb seem to show nothing different, and I can find no errors or messages in the logs relating to this.
>>
>> Any ideas what is going on here? The only work around seems to be to switch to the show when it starts and hit record.
>>
>
> Actually I think this is related to the new timezone setup in 0.26 - if I look at the recording rule in the database, the last scheduled recording times etc are all local time, but the view in the
> frontend shows the last recorded at Aug 15 07:33AM when in fact it was Aug 14 09:33PM (I am GMT+10, so it seems to think the times in the DB are GMT not AEST).
>
> Also the frontend seems to think the show is scheduled for 10AM-10AM in the rules overview. The rule in the database has the startdate and enddate of today at 0:00, so +10 would make it be 10am.
>
> I am not sure this should really affect it, because it is a "record any time on this channel" rule, and nothing to do with timeslots etc.
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://www.mythtv.org/mailman/listinfo/mythtv-users
Adrian, I've also been seeing this since performing
1) the Mysql timezone load, and
2) removing my daily mythbackend reboot as no longer necessary (wrong!).

Reinstating the daily mythbackend process restart is a workaround and temporarily removes the problem, for about 24h.
I had thought it may have been shepherd (and given your GMT+10 I'm guessing you also might be in Australia)
but disabling program guide updates had no effect, I've only seen complaints on the mailing list from GMT+10 which is why I was looking at shepherd.
Setting every don't do EIT flag I could find (overall, tuner, channel) has also had no effect.

Something else is confusing mythbackends time sense.

In the past this sort of problem is usually solved by someone else the moment I start digging into the code. I might have to try invoking that method again and see if it works.

--
Carl Lewis
Manager ICT
Department of Primary Industries, Parks, Water and Environment
*Ph*: 0362125150 *email:* Carl.Lewis [at] dpipwe <mailto:Carl.Lewis [at] dpipwe>

sgtbundy at gmail

Aug 20, 2012, 2:44 AM

Post #4 of 8 (568 views)
Permalink

Re: 0.26 recording rules - "not listed" [In reply to]

Adrian, I've also been seeing this since performing
> 1) the Mysql timezone load, and
> 2) removing my daily mythbackend reboot as no longer necessary (wrong!).
>
> Reinstating the daily mythbackend process restart is a workaround and
> temporarily removes the problem, for about 24h.
> I had thought it may have been shepherd (and given your GMT+10 I'm
> guessing you also might be in Australia)
> but disabling program guide updates had no effect, I've only seen
> complaints on the mailing list from GMT+10 which is why I was looking
> at shepherd.
> Setting every don't do EIT flag I could find (overall, tuner, channel)
> has also had no effect.
>
> Something else is confusing mythbackends time sense.
>
> In the past this sort of problem is usually solved by someone else the
> moment I start digging into the code. I might have to try invoking
> that method again and see if it works.
>

I have been using the IceTV service, not shepherd so it rules that out.
I also have EIT disabled on the tuners.

Having burned many late nights over the last week on upgrading to 0.26 I
am not keen to spend dive into debugging this via code reading, but I
fear thats the only way as I can't see anything obvious in what appears
in the database or logs. The most annoying part is that you can only
catch this if you see something disappear.

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

david at istwok

Aug 21, 2012, 8:07 AM

Post #5 of 8 (541 views)
Permalink

Re: 0.26 recording rules - "not listed" [In reply to]

On Sun, Aug 19, 2012 at 10:54:25PM +1000, Adrian Saul wrote:
> On 19/08/2012 10:46 PM, Adrian Saul wrote:
> >
> >Picked up a slightly annoying bug with 0.26 tonight - my wife was
> >watching a show and decided to manually record the following
> >program in case this one ran overtime. She went to the guide,
> >picked the next show and did a manual record. Instantly the two
> >other shows in scheduled to be recorded tonight disappeared from
> >upcoming recordings.
> >
> >If I look at the upcoming recordings there is nothing there to say
> >they are in conflict or anything, there are plenty of free tuners
> >and it seemed happy to record it before.
> >If I pick the show in the guide it has nothing to say it wants to
> >record it.
> >If I do a manual record in on the show, it shows up in upcoming
> >recordings and the guide as "Not Listed" (WTF does that mean, yes
> >it is, its right there).
> >If I look at the recording rules it is there and I see nothing
> >that would prevent it recording, and preview changes shows it as
> >"this will be recorded" but it never appears in upcoming
> >recordings.
> >
> >Viewing via the frontend of mythweb seem to show nothing
> >different, and I can find no errors or messages in the logs
> >relating to this.
> >
> >Any ideas what is going on here? The only work around seems to
> >be to switch to the show when it starts and hit record.
> >
>
> Actually I think this is related to the new timezone setup in 0.26 -
> if I look at the recording rule in the database, the last scheduled
> recording times etc are all local time, but the view in the frontend
> shows the last recorded at Aug 15 07:33AM when in fact it was Aug 14
> 09:33PM (I am GMT+10, so it seems to think the times in the DB are
> GMT not AEST).
>
> Also the frontend seems to think the show is scheduled for 10AM-10AM
> in the rules overview. The rule in the database has the startdate
> and enddate of today at 0:00, so +10 would make it be 10am.
>
> I am not sure this should really affect it, because it is a "record
> any time on this channel" rule, and nothing to do with timeslots
> etc.

It would not surpise me if there are some lingering UTC/timezone
related bugs. Unfortunately, your descriptions leave way too much
room for interpretation on exactly what your are doing. If you can
provide detailed, step-by-step instructions on how to reproduce the
problem, I'd be happy to look into it. Also, in your later email, you
said you weren't using EIT. Could you please double check that.

David
--
David Engel
david [at] istwok
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

carl.lewis at dpipwe

Sep 2, 2012, 6:11 PM

Post #6 of 8 (469 views)
Permalink

Re: 0.26 recording rules - "not listed" [In reply to]

On 22/08/12 01:07, David Engel wrote:
> On Sun, Aug 19, 2012 at 10:54:25PM +1000, Adrian Saul wrote:
>> On 19/08/2012 10:46 PM, Adrian Saul wrote:
>>>
>>> Picked up a slightly annoying bug with 0.26 tonight - my wife was
>>> watching a show and decided to manually record the following
>>> program in case this one ran overtime. She went to the guide,
>>> picked the next show and did a manual record. Instantly the two
>>> other shows in scheduled to be recorded tonight disappeared from
>>> upcoming recordings.
>>>
>>> If I look at the upcoming recordings there is nothing there to say
>>> they are in conflict or anything, there are plenty of free tuners
>>> and it seemed happy to record it before.
>>> If I pick the show in the guide it has nothing to say it wants to
>>> record it.
>>> If I do a manual record in on the show, it shows up in upcoming
>>> recordings and the guide as "Not Listed" (WTF does that mean, yes
>>> it is, its right there).
>>> If I look at the recording rules it is there and I see nothing
>>> that would prevent it recording, and preview changes shows it as
>>> "this will be recorded" but it never appears in upcoming
>>> recordings.
>>>
>>> Viewing via the frontend of mythweb seem to show nothing
>>> different, and I can find no errors or messages in the logs
>>> relating to this.
>>>
>>> Any ideas what is going on here? The only work around seems to
>>> be to switch to the show when it starts and hit record.
>>>
>>
>> Actually I think this is related to the new timezone setup in 0.26 -
>> if I look at the recording rule in the database, the last scheduled
>> recording times etc are all local time, but the view in the frontend
>> shows the last recorded at Aug 15 07:33AM when in fact it was Aug 14
>> 09:33PM (I am GMT+10, so it seems to think the times in the DB are
>> GMT not AEST).
>>
>> Also the frontend seems to think the show is scheduled for 10AM-10AM
>> in the rules overview. The rule in the database has the startdate
>> and enddate of today at 0:00, so +10 would make it be 10am.
>>
>> I am not sure this should really affect it, because it is a "record
>> any time on this channel" rule, and nothing to do with timeslots
>> etc.
>
> It would not surpise me if there are some lingering UTC/timezone
> related bugs. Unfortunately, your descriptions leave way too much
> room for interpretation on exactly what your are doing. If you can
> provide detailed, step-by-step instructions on how to reproduce the
> problem, I'd be happy to look into it. Also, in your later email, you
> said you weren't using EIT. Could you please double check that.
>
> David
>
David, I knobbled EIT directly in the appropriate database tables and verified with mythv-setup.
It's possible I may still have missed something as I'm basing what I'm setting on a couple of postings
to the mailing list. I've just looked (grep -i eit) through the last week of syslog output and there
are no mentions of EIT. I'm not sure if there would be mentions if it was running as I've never had it intentionally
going. Until relatively recently EIT listings in Australia, particularly outside of the mainland capital cities,
were .... unreliable. Consequently they were routinely disabled.

But to reproduce the problem (regardless of program guide updates being enabled or not)
1) Leave mythbackend running for > 24 hours (my be less, but it's hard to narrow down)
2) Go to the program guide and press record on a program coming up.
3) "No Listing" error message.

If mythbackend has been restarted recently the problem doesn't occur. I'll get the wife to try a few records
today just before the currently scheduled 2pm restart in order to make sure it's a duration (24h) rather than a time of day
thing and post the results.

I'm running v0.26pre with a last commit in the log of:
commit ec2ac418bd2d15264ffb99f62d78afa78ec0aa72
Author: Raymond Wagner <rwagner [at] mythtv>
Date: Wed Jul 18 01:50:46 2012 -0400

I've been keeping a sporadic eye on mythtv-commits but seen nothing that looked like a fix
and so haven't updated in a while, but am happy to do so. It's non-ratings period so there are multiple evenings
where nothing is recording.

Carl

--
Carl Lewis
Manager ICT
Department of Primary Industries, Parks, Water and Environment
*Ph*: 0362125150 *email:* Carl.Lewis [at] dpipwe <mailto:Carl.Lewis [at] dpipwe>
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

sgtbundy at gmail

Sep 13, 2012, 5:39 AM

Post #7 of 8 (442 views)
Permalink

Re: 0.26 recording rules - "not listed" [In reply to]

On 3/09/2012 11:11 AM, Carl Lewis wrote:
>
> But to reproduce the problem (regardless of program guide updates
> being enabled or not)
> 1) Leave mythbackend running for > 24 hours (my be less, but it's hard
> to narrow down)
> 2) Go to the program guide and press record on a program coming up.
> 3) "No Listing" error message.
>
> If mythbackend has been restarted recently the problem doesn't occur.
> I'll get the wife to try a few records
> today just before the currently scheduled 2pm restart in order to make
> sure it's a duration (24h) rather than a time of day
> thing and post the results.
>
> I'm running v0.26pre with a last commit in the log of:
> commit ec2ac418bd2d15264ffb99f62d78afa78ec0aa72
> Author: Raymond Wagner <rwagner [at] mythtv>
> Date: Wed Jul 18 01:50:46 2012 -0400
>
> I've been keeping a sporadic eye on mythtv-commits but seen nothing
> that looked like a fix
> and so haven't updated in a while, but am happy to do so. It's
> non-ratings period so there are multiple evenings
> where nothing is recording.
>

Just an update on this issue, with much patient help from David (thanks)
I think we have nailed it down.

The conditions:
- using 0.26
- in a GMT+8 or greater offset time zone
- when the scheduler runs, there are programs ending in less than TZ
offset - 8 hours time (i.e GMT+10 = programs ending in the next 2 hours)
- the scheduler is idle for 8 hours or more (or whatever wait_timeout
is set to in MySQL)

The timezone part of it is the scheduler has queries which filters out
programs with end times greater than 8 hours ago. The scheduler uses a
dedicated database connection, and if that happens to timeout with the
scheduler being idle, the connection is automatically reconnected.
However the reconnection code does not reset the database session
time_zone values, which in 0.26 is forced to UTC. You can see when this
occurs with this backend log entry (note it is for the Scheduler).

Sep 13 16:16:32 pvr mythlogserver: mythbackend[32223]: I Scheduler
mythdbcon.cpp:243 (Reconnect) MySQL reconnected successfully

The result being that the scheduler SQL queries start filtering
programs relative to local time and not UTC. In my case being GMT+10,
that means anything ending in the next 2 hours is filtered out from
consideration, with the result being those programs suddenly disappear
from the upcoming recordings without a trace. Every time the scheduler
runs from that point (pretty much every deletion or recording ending) it
will strip out anything ending in the next two hours from being recorded.

This also explains why a backend restart fixes it, mostly, not always
but I think that is due to database value changes being commited when
the problem occurs. The restart causes the session to be established
from scratch with the DB session time_zone set correctly by the initial
connection code.

Also I figure that if your GMT offset is less than +8 hours you won't
see this as the SQL clause wont fail as the calculated time will still
be in the past relative to the program endtime. Also, If your
scheduler activity is enough that the database session does not get to
wait_timeout or get interrupted you probably won't see this.

Possible workarounds:
- modify MySQL and set the wait_timeout value to a higher value (I
have not tested this directly yet).
- set the default database timezone to UTC (seems to work, but may
cause other issues)
- reset your backend during idle times to reduce the impact (painful)

Just an FYI for anyone else who is hitting this issue.

Cheers,
Adrian

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

mtdean at thirdcontact

Sep 13, 2012, 8:40 PM

Post #8 of 8 (429 views)
Permalink

Re: 0.26 recording rules - "not listed" [In reply to]

On 09/13/2012 08:39 AM, Adrian Saul wrote:
> Just an update on this issue, with much patient help from David
> (thanks) I think we have nailed it down.

BTW, thanks to you and David for finding and fixing this issue.

(And it's now fixed in current master, so no need to change your local
MySQL configuration or any of the other listed workarounds.)

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads