Bug #5474
Failed Recordings - Time Missed error
0%
Description
TVheadend is losing many of my recordings. They seem to start and end OK but are not available and have the status "Time missed".
An example of an autorec (series link) recording lost on my Ubuntu Bionic server below. An extract of the DVR log from the latest attempt below-
-
2019-01-02 19:29:30.004 [ TRACE]:dvr: entry 39cdfd44a980d61a7d005ef3f588dc78 - set state - state RECORDING rec_state PENDING error 'OK'
2019-01-02 19:29:30.004 [ INFO]:dvr: "Coronation Street" on "STV HD" recorder starting
2019-01-02 19:29:30.004 [ TRACE]:dvr: entry 39cdfd44a980d61a7d005ef3f588dc78 original stop 2019-01-02;20:00:00(+0000) stop 2019-01-02;20:00:00(+0000) - stop timer set
2019-01-02 19:29:30.005 [ INFO]:mpegts: 11067.5V in DVB-S Network - tuning on SAT>IP DVB-S Tuner #1 (192.168.1.17@UDP)
2019-01-02 19:29:30.005 [ INFO]:subscription: 0009: "DVR: Coronation Street" subscribing on channel "STV HD", weight: 300, adapter: "SAT>IP DVB-S Tuner #1 (192.168.1.17@UDP)", network: "DVB-S Ne$
2019-01-02 19:29:30.005 [ TRACE]:dvr: 39cdfd44a980d61a7d005ef3f588dc78 - recoding thread started for "Coronation Street"
2019-01-02 19:29:30.278 [ TRACE]:dvr: entry 39cdfd44a980d61a7d005ef3f588dc78 - set state - state RECORDING rec_state EPGWAIT error 'OK'
-
-
2019-01-02 20:00:00.006 [ TRACE]:dvr: entry 39cdfd44a980d61a7d005ef3f588dc78 rstart 1970-01-01;01:00:00(+0100) rstop 2019-01-02;19:27:25(+0000) - stop recording timer called
2019-01-02 20:00:00.006 [ INFO]:subscription: 0009: "DVR: Coronation Street" unsubscribing from "STV HD", username="tv"
2019-01-02 20:00:00.006 [ TRACE]:dvr: entry 39cdfd44a980d61a7d005ef3f588dc78 - set state - state MISSEDTM rec_state FINISHED error 'OK'
2019-01-02 20:00:00.006 [ TRACE]:dvr: entry 39cdfd44a980d61a7d005ef3f588dc78 when 1970-01-01;01:00:00(+0100) - retention arm
2019-01-02 20:00:00.006 [ INFO]:dvr: "Coronation Street" on "STV HD": End of program: Time missed
2019-01-02 20:00:00.006 [ TRACE]:dvr: entry 39cdfd44a980d61a7d005ef3f588dc78 start 2019-01-02;19:29:30(+0000) stop 2019-01-02;20:00:00(+0000) - set timer
2019-01-02 20:00:00.006 [ TRACE]:dvr: entry 39cdfd44a980d61a7d005ef3f588dc78 - set state - state COMPLETED rec_state FINISHED error 'OK'
2019-01-02 20:00:00.007 [ TRACE]:dvr: entry 39cdfd44a980d61a7d005ef3f588dc78 when 1970-01-01;01:00:00(+0100) - retention arm
2019-01-02 20:00:00.007 [ TRACE]:dvr: entry 39cdfd44a980d61a7d005ef3f588dc78 when 1970-01-01;01:00:00(+0100) - retention arm
2019-01-02 20:00:00.007 [ TRACE]:dvr: entry 39cdfd44a980d61a7d005ef3f588dc78 - retention timer - disarm
-
-
Files
History
Updated by da h4xX0rz1sT almost 6 years ago
Updated by Same here, still. Happens mostly when there is an decryption issue or continuty error right on start of recording, tvh seems to not recover from that.
I can also observe outgoing stream size is '0', file size stays at '---' in current recordings.
Is it happening on an encrypted channel (not visible from your log)? If yes, what decryption method is used?
HTH & happy new year to all,
/HXZ
Updated by Jaroslav Kysela almost 6 years ago
Updated by Do you see any EPG running updates (it should be in the DVR traces - it might be helpful to see the whole uncut log)? It seems that TVH stucks in the EPGWAIT state and the program is not recorded, because EPG did not signalize the start of the particular event.
Updated by Mos Mosmos almost 6 years ago
Updated by - File tvheadendlog old.txt tvheadendlog old.txt added
Uncut Log file attached.
I’ve also noticed an EPG grabber “Over-the-air: UK: Freesat (EIT)” which I don’t recall seeing when I last configured Tvheadend. What is the difference with the compared to “Over-the-air :EIT EPG Grabber”
Updated by Jaroslav Kysela almost 6 years ago
Add 'tbl-eit' to your trace log. It seems like a EITp/f signaling issue.
Updated by Mos Mosmos almost 6 years ago
Seems to be working ok with “Over-the-air: UK: Freesat (EIT)” EPG Grabber enabled. I'll provide a log wiith tbl-eit if the issue happens again.