Bug #2580
services get disabled when "missing in PAT"
0%
Description
In the last weeks, BBC 4 HD gets disabled repeatedly, thus I miss recordings (repeatedly).
In syslog I see messages like
Dec 27 15:47:03 sat tvheadend4881: mpegts: 10847V in 28.2E - tuning on STV090x Multistandard : DVB-S #3
Dec 27 15:47:03 sat tvheadend4881: subscription: 000A: "10.29.1.46 [ XBMC Media Center ]" subscribing on "BBC Three HD", we
ight: 150, adapter: "STV090x Multistandard : DVB-S #3", network: "28.2E", mux: "10847V", provider: "BSkyB", service: "BBC Thr
ee HD", hostname="10.29.1.46", username="<N/A>", client="XBMC Media Center"
Dec 27 15:47:04 sat tvheadend4881: subscription: 000A: "10.29.1.46 [ XBMC Media Center ]" unsubscribing from "BBC Three HD"
, hostname="10.29.1.46", username="<N/A>", client="XBMC Media Center"
Dec 27 15:47:04 sat tvheadend4881: mpegts: 11023.25H in 28.2E - tuning on STV090x Multistandard : DVB-S #3
Dec 27 15:47:05 sat tvheadend4881: subscription: 000B: "10.29.1.46 [ XBMC Media Center ]" subscribing on "BBC Four HD", wei
ght: 150, adapter: "STV090x Multistandard : DVB-S #3", network: "28.2E", mux: "11023.25H", provider: "BSkyB", service: "BBC F
our HD", hostname="10.29.1.46", username="<N/A>", client="XBMC Media Center"
Dec 27 15:47:05 sat tvheadend4881: mpegts: disabling service 28.2E/11023.25H/BBC Four HD (missing in PAT)
Dec 27 15:47:14 sat tvheadend4881: mpegts: 11023.25H in 28.2E - scan needs more time
Dec 27 15:47:26 sat tvheadend4881: mpegts: 11023.25H in 28.2E scan complete
Dec 27 15:47:28 sat tvheadend4881: subscription: 000B: "10.29.1.46 [ XBMC Media Center ]" unsubscribing from "BBC Four HD",
hostname="10.29.1.46", username="<N/A>", client="XBMC Media Center"
Manually enabling the service works, for a few days. Then "missing in PAT" reappears :-(
This happens for more services on 19.2E and 28.2E
History
Updated by Rafal Kupiec almost 10 years ago
Updated by Yes, thats annoying...
You can avoid that by editing service with 'missing in pat' and disable automatic checking for this specific service.
Anyway, when there are a lot of such services, this is still like a pain in the ass, TBH.
So imho there should be option, to disable automatic checking at least per MUX.
Updated by Rob vh almost 10 years ago
Updated by Thank you for the workaround...
This "issue" didn't occur a month ago and also, it seems to happen for some services more than others, e.g., I've lost BBC 4 HD twice now (and I see that BBC ARABIC, BBC CZ and BBCW SERVICE are gone too) but so far did not lose any other BBC service. I wonder if it is, dare I say, some unforeseen side effect in the code ;-).
Updated by Rafal Kupiec almost 10 years ago
Rob vh wrote:
Thank you for the workaround...
This "issue" didn't occur a month ago and also, it seems to happen for some services more than others, e.g., I've lost BBC 4 HD twice now (and I see that BBC ARABIC, BBC CZ and BBCW SERVICE are gone too) but so far did not lose any other BBC service. I wonder if it is, dare I say, some unforeseen side effect in the code ;-).
This is a new feature requested by someone here... dunno why implement. I dont understand its purpose... More cons than pros...
Updated by Jaroslav Kysela almost 10 years ago
Updated by Could you provide logs for '--trace pat --debug pat' around time the service is disabled ?
The PAT tables are mandatory, but sure - there might be somewhere a little bug in the table parsers..
Updated by Rafal Kupiec almost 10 years ago
Jaroslav Kysela wrote:
Could you provide logs for '--trace pat --debug pat' around time the service is disabled ?
The PAT tables are mandatory, but sure - there might be somewhere a little bug in the table parsers..
I have already reported few bugs. Always you closed them with info that they are caused by low quality drivers or hardware issue.
This is causing also 'missing in pat' problems. I dont think services should be disabled automatically...
Updated by Jaroslav Kysela almost 10 years ago
I added also SDT table checks to v3.9-2307-g1f62c46, so the service will be disabled only when it's missing in PAT and SDT now.
Updated by Jaroslav Kysela almost 10 years ago
Rafal Kupiec wrote:
Jaroslav Kysela wrote:
Could you provide logs for '--trace pat --debug pat' around time the service is disabled ?
The PAT tables are mandatory, but sure - there might be somewhere a little bug in the table parsers..
I have already reported few bugs. Always you closed them with info that they are caused by low quality drivers or hardware issue.
This is causing also 'missing in pat' problems. I dont think services should be disabled automatically...
Your logs contained data from another transpoder, so almost all parsers worked incorrectly, because it's serious bug in other layer than tvh.. You may try to use multiple tune requests to solve the tuning issue.
Updated by Rafal Kupiec almost 10 years ago
Jaroslav Kysela wrote:
Rafal Kupiec wrote:
Jaroslav Kysela wrote:
Could you provide logs for '--trace pat --debug pat' around time the service is disabled ?
The PAT tables are mandatory, but sure - there might be somewhere a little bug in the table parsers..
I have already reported few bugs. Always you closed them with info that they are caused by low quality drivers or hardware issue.
This is causing also 'missing in pat' problems. I dont think services should be disabled automatically...Your logs contained data from another transpoder, so almost all parsers worked incorrectly, because it's serious bug in other layer than tvh.. You may try to use multiple tune requests to solve the tuning issue.
Its not helping out.
And it will be missing in PAT and SDT then.
So best option is to avoid auto disable such services...
Updated by Anonymous almost 10 years ago
You can disable checking the PAT and SDT in services tab.
Updated by Rafal Kupiec almost 10 years ago
Janusze Biznesu wrote:
You can disable checking the PAT and SDT in services tab.
I know that.
Now lets imagine there are 20 muxes, each providing 8 services, that are caused by this.
So such ability (to disable checking) should be available per MUX or per network. NOT per service, like its actually done.
Updated by Jaroslav Kysela almost 10 years ago
Rafal Kupiec wrote:
Janusze Biznesu wrote:
You can disable checking the PAT and SDT in services tab.
I know that.
Now lets imagine there are 20 muxes, each providing 8 services, that are caused by this.
So such ability (to disable checking) should be available per MUX or per network. NOT per service, like its actually done.
Rafal, your environment is broken somehow. I have 9 sat positions and DVB-T without these symptomps. If you don't like it, just comment it in the source code. Add 'return' to the mpegts_mux_scan_service_check() function - src/input/mpegts/mpegts_mux.c (line 864). But for standard users, I don't see any reason to keep enabled the services which are not broadcasted and other - special - services can be excluded from this check but one by one now.
Updated by Rafal Kupiec almost 10 years ago
Jaroslav Kysela wrote:
Rafal Kupiec wrote:
Janusze Biznesu wrote:
You can disable checking the PAT and SDT in services tab.
I know that.
Now lets imagine there are 20 muxes, each providing 8 services, that are caused by this.
So such ability (to disable checking) should be available per MUX or per network. NOT per service, like its actually done.Rafal, your environment is broken somehow. I have 9 sat positions and DVB-T without these symptomps. If you don't like it, just comment it in the source code. Add 'return' to the mpegts_mux_scan_service_check() function - src/input/mpegts/mpegts_mux.c (line 864). But for standard users, I don't see any reason to keep enabled the services which are not broadcasted and other - special - services can be excluded from this check but one by one now.
But i have never say that this option should be disabled. Just that users should have a choice per MUX, as I dont seem to be the only person having such issues (most probably due to broken hardware / driver)...
Updated by Rob vh almost 10 years ago
with 3.9.2347, I no longer see BBC 4 HDs and friends going "disabled" so it looks like your algorithm to check SDT in combination with PAT was correct.
Updated by Anonymous over 9 years ago
The problem is still there. I see hundreds of enabling/disabling messages within
seconds. It is really strange that the service gets enabled - and immediatly got
disabled again. I do not see any problems with the reception signal: no Continuity
errors, no problems except the autodisabling.
The "Autodisabling" of services is - aeh - extremly unexpected.
2015-06-20T11:00:16.479024+02:00 server tvheadend1875: mpegts: enabling service Kabel Schland/450MHz/rbb Berlin HD (found in PAT)
2015-06-20T11:00:16.480182+02:00 server tvheadend1875: mpegts: enabling service Kabel Schland/450MHz/ZDF HD (found in PAT)
2015-06-20T11:00:16.480951+02:00 server tvheadend1875: mpegts: enabling service Kabel Schland/450MHz/ZDFinfo (found in PAT)
2015-06-20T11:00:16.481719+02:00 server tvheadend1875: mpegts: enabling service Kabel Schland/450MHz/zdf.kultur (found in PAT)
2015-06-20T11:00:19.348340+02:00 server tvheadend1875: mpegts: 450MHz in Kabel Schland scan complete
2015-06-20T11:00:19.349603+02:00 server tvheadend1875: mpegts: disabling service Kabel Schland/450MHz/ZDF HD [sid 2B66/11110] (missing in PAT/SDT)
2015-06-20T11:00:19.350392+02:00 server tvheadend1875: mpegts: disabling service Kabel Schland/450MHz/rbb Berlin HD [sid 286F/10351] (missing in PAT/SDT)
2015-06-20T11:00:19.351198+02:00 server tvheadend1875: mpegts: disabling service Kabel Schland/450MHz/ZDFinfo [sid 6D6B/28011] (missing in PAT/SDT)
2015-06-20T11:00:19.351961+02:00 server tvheadend1875: mpegts: disabling service Kabel Schland/450MHz/zdf.kultur [sid 6D70/28016] (missing in PAT/SDT)