Bug #4868: Timers are not scheduled - Tvheadend

Custom queries

Accepted bugs by category
Bugs by category
Bugs by priority
Bugs by status
Bugs by target version
Features by category
Features by target version
Issues by category
Issues by status
Issues by target version
Need feedback by date
New issues
Status for next release

Actions

Copy link

Bug #4868

closed

Timers are not scheduled

Added by ian stuart over 7 years ago. Updated about 7 years ago.

Status:

Fixed

Priority:

Normal

Assignee:

Adam Sutton

Category:

PVR / DVR

Target version:

Start date:

2018-01-18

Due date:

% Done:

100%

Estimated time:

Found in version:

4.3-982

Affected Versions:

Description

Hi,

Updated from 4.3-754 to latest, timers are not scheduled (and not recorded).

Tested:
tvheadend_4.3-971~g9e6b063~xenial_amd64.deb
tvheadend_4.3-982~gbe4a32a~xenial_amd64.deb

downgrading to 4.3-754 fix the problem, if you need i will test each builds tonight to know the faulty build.

Thanks

Autorec still works.

Files

Download all files

log1.txt (1.04 MB) log1.txt	dvr trace	ian stuart, 2018-01-21 17:09
log4.txt (1.17 MB) log4.txt		ian stuart, 2018-01-23 17:53
Screen Shot 2018-02-01 at 16.38.13.png (9.97 KB) Screen Shot 2018-02-01 at 16.38.13.png		ian stuart, 2018-02-01 16:39

History
Notes
Property changes

Actions

Copy link

Updated by Jaroslav Kysela over 7 years ago

I cannot confirm that. Could you show the '--trace dvr' ?

Actions

Copy link

Updated by ian stuart about 7 years ago

File log1.txt log1.txt added

Jaroslav Kysela wrote:

I cannot confirm that. Could you show the '--trace dvr' ?

Done.

Few tests:
- if i disable / enable the timer (from web interface), nothing are displayed in the log with dvr trace.
With "all" flag, i see the http / htsp action (kodi display "enable / disable timer...") but nothing else.

Actions

Copy link

Updated by Jaroslav Kysela about 7 years ago

This issue is really weird.

2018-01-21 17:02:44.701 [  TRACE]:dvr: entry f22220c2dcc46a985a128d6da83ce320 - assign broadcast 67306629
2018-01-21 17:02:44.701 [  TRACE]:dvr: entry f22220c2dcc46a985a128d6da83ce320 start 2018-01-21;16:29:30(+0100) stop 2018-01-21;17:55:00(+0100) - set timer
2018-01-21 17:02:44.701 [  TRACE]:dvr: entry f22220c2dcc46a985a128d6da83ce320 start 2018-01-21;16:29:30(+0100) - set timer - schedule
2018-01-21 17:02:44.702 [   INFO]:dvr: entry f22220c2dcc46a985a128d6da83ce320 "Americars" on "Discovery Channel" starting at 2018-01-21 16:29:30, with broadcast id "tvh://channel-5c0aa1f0e5c95c1b4c8808c318e86818/bcast-67306629/episode", scheduled for recording by "192.168.0.195" 
2018-01-21 17:02:44.702 [  TRACE]:dvr: entry f22220c2dcc46a985a128d6da83ce320 start 2018-01-21;16:29:30(+0100) stop 2018-01-21;17:55:00(+0100) - set timer
2018-01-21 17:02:44.702 [  TRACE]:dvr: entry f22220c2dcc46a985a128d6da83ce320 start 2018-01-21;16:29:30(+0100) - set timer - schedule
2018-01-21 17:02:44.737 [  TRACE]:dvr: entry bf6bc94bf6c3715296103d865e807590 - assign broadcast 67308421
2018-01-21 17:02:44.737 [  TRACE]:dvr: entry bf6bc94bf6c3715296103d865e807590 start 2018-01-21;16:29:30(+0100) stop 2018-01-21;17:50:00(+0100) - set timer
2018-01-21 17:02:44.737 [  TRACE]:dvr: entry bf6bc94bf6c3715296103d865e807590 start 2018-01-21;16:29:30(+0100) - set timer - schedule
2018-01-21 17:02:44.737 [  TRACE]:dvr: entry bf6bc94bf6c3715296103d865e807590 start 2018-01-21;16:29:30(+0100) stop 2018-01-21;17:50:00(+0100) - set timer
2018-01-21 17:02:44.737 [  TRACE]:dvr: entry bf6bc94bf6c3715296103d865e807590 start 2018-01-21;16:29:30(+0100) - set timer - schedule
2018-01-21 17:02:44.828 [  TRACE]:dvr: entry bf6bc94bf6c3715296103d865e807590 - unassign broadcast 67308421
2018-01-21 17:02:44.828 [  TRACE]:dvr: entry f22220c2dcc46a985a128d6da83ce320 - unassign broadcast 67306629

Only the last two lines are suspicious (the EPG event was unassigned from the DVR entry).

I need to add more logs to somewhere.

Actions

Copy link

Updated by ian stuart about 7 years ago

Jaroslav Kysela wrote:

This issue is really weird.

[...]

Only the last two lines are suspicious (the EPG event was unassigned from the DVR entry).

I need to add more logs to somewhere.

Ok i have tested all builds on doozer...

The bug was introduced between 4.3-932~g459e106 (works) and 4.3-936~g1c38450

Actions

Copy link

Updated by Jaroslav Kysela about 7 years ago

Could you describe more exactly, how do you create DVR entries ?

Actions

Copy link

Updated by ian stuart about 7 years ago

Jaroslav Kysela wrote:

Could you describe more exactly, how do you create DVR entries ?

Via the web interface, timers, create new...
It’s don’t works with timers created 1-2 years ago, nor new timers created for test since this bug

Actions

Copy link

Updated by Jaroslav Kysela about 7 years ago

Use '--enable gtimer_check' for ./configure and show '--trace dvr,gtimer' log.

Actions

Copy link

Updated by ian stuart about 7 years ago

File log4.txt log4.txt added

Jaroslav Kysela wrote:

Use '--enable gtimer_check' for ./configure and show '--trace dvr,gtimer' log.

Do you think compilation with
AUTOBUILD_CONFIGURE_EXTRA="--enable gtimer_check" ./Autobuild.sh
are good ?

Because i see nothing much in log... And, as i had installed a working version, all timers are already created... i have deleted one for testing but i ever don't see "unassign broadcast" anymore.

BTW, log are there

Actions

Copy link