Bug #2391
bad tune followed by continuity errors, new in 3.9.1777 and 1871
0%
Description
I have not seen these errors in 3.9.1743, but after my new git pull last weekend I have been having bad tunes again.
they may be linked with having a streaming connection active, when a recording starts. here is one from last night:
23:20:17 I start a streaming connection, tuned to NPO2, using adapter 3.
23:49:30 a recording start on Channel, using adapter 2.
25:59:30 another recording starts for Net5 HD, on adapter 4. This one fails with
2014-10-17 23:59:31.341 [ DEBUG]:linuxdvb: STV090x Multistandard : DVB-S #4 - status BAD (SIGNAL | CARRIER)
2014-10-17 23:59:37.073 [ DEBUG]:linuxdvb: STV090x Multistandard : DVB-S #4 - status NONE ()
2014-10-17 23:59:37.545 [ DEBUG]:linuxdvb: STV090x Multistandard : DVB-S #4 - status BAD (SIGNAL | CARRIER)
2014-10-17 23:59:40.303 [ DEBUG]:service: 23.5E/12187H/NET5 HD: Status changed to [Graceperiod expired] [Data timeout]
2014-10-17 23:59:40.616 [ DEBUG]:capmt: oscam, CA_SET_DESCR adapter 3 par 0 idx 0 fe227292a5b8fc59
2014-10-17 23:59:42.299 [ DEBUG]:mpegts: 12187H in 23.5E - stopping mux
2014-10-17 23:59:42.299 [ DEBUG]:linuxdvb: STV090x Multistandard : DVB-S #4 - stopping 12187H in 23.5E
2014-10-17 23:59:42.299 [ DEBUG]:epggrab: grab done for 12187H in 23.5E (stolen)
Adapter 4 is definitely not bad or lazy, other recordings for Net5 HD start perfectly on adapter4.
So after tvh discarded adapter 4, he tries adapter 5, and gets continuity errors.
Files
History
Updated by Rob vh about 10 years ago
Updated by - File syslogB.txt syslogB.txt added
- File debugB.txt debugB.txt added
Here is another one.
recording for Elementary on Net5 HD scheduled to start at 20:24 has continuous continuity errors.
the second episode starts perfectly.
Along with the CCE, I see
Oct 16 20:30:19 sat tvheadend4583: descrambler: SBS6 HD even stream key is not valid
Oct 16 20:31:49 sat tvheadend4583: descrambler: SBS6 HD odd stream key is not valid
Updated by Rob vh about 10 years ago
in both cases, signal and SNR were very good, while the TE and CE counters were ticking up.
Updated by Anders Falk about 10 years ago
Updated by Rob vh wrote:
in both cases, signal and SNR were very good, while the TE and CE counters were ticking up.
Hi
I have noticed the same. Did an upgrade this week fron 17xx to the latest 18xx. Have also gotten continuity error that weren't there before.
//Anders
Updated by
Updated by Rob vh about 10 years ago
here is a trace of descrambler. First I had a segfault starting a recording, then tvh restarted and the recording ran into CE messages. Plus pid errors for eit (that normally, on that mux don't happen).
Updated by Jaroslav Kysela about 10 years ago
Rob vh wrote:
here is a trace of descrambler. First I had a segfault starting a recording, then tvh restarted and the recording ran into CE messages. Plus pid errors for eit (that normally, on that mux don't happen).
It's not exactly issue as reported and I wanted to look into.. There are no descrambler errors.. I would blame the driver/hw for this one (concurrent streaming, linuxdvb device close/open)..
Also, I meant to enable traces for descrambler - something like '-l /tmp/tvheadend.log --trace descrambler' on the command like or appropriate fields in the debug config in webui..
Updated by Rob vh about 10 years ago
please consider this fixed, it hasn't occurred in a week now.