Bug #2740
TVHeadend don't stop finding services
0%
Description
Hello,
My installation don't stop finding services, right now I have exactly 2082 services and if I go look tomorrow, it will be twice as that.
The only thing I could see different in my logs is "Raw PID Subscription" like these:
2015-03-26 12:00:59.009 subscription: 0029: "epggrab" subscribing on "none", weight: 4, adapter: "TurboSight TBS 6205 DVBC frontend : DVB-C #0", network: "NET", mux: "219MHz", provider: "", service: "Raw PID Subscription" 2015-03-26 12:01:04.000 mpegts: 219MHz in NET - scan complete 2015-03-26 12:01:04.000 mpegts: 309MHz in NET - scan complete 2015-03-26 12:02:21.328 subscription: 0023: "epggrab" unsubscribing 2015-03-26 12:02:22.010 mpegts: 147MHz in NET - tuning on TurboSight TBS 6205 DVBC frontend : DVB-C #0 2015-03-26 12:02:22.010 subscription: 002C: "epggrab" subscribing on "none", weight: 4, adapter: "TurboSight TBS 6205 DVBC frontend : DVB-C #0", network: "NET", mux: "147MHz", provider: "", service: "Raw PID Subscription" 2015-03-26 12:02:27.000 mpegts: 147MHz in NET - scan complete
My setup is the follow:
DVB Card: TBS 6205 + DVB-C Provider
Tvheadend: 3.9.2652~g3fab60a
S.O.: Ubuntu 14.10
Files
History
Updated by Jaroslav Kysela over 9 years ago
Could you describe more? Services are duplicated ? Assigned to wrong muxes etc?
Updated by Bruno Bastos over 9 years ago
Jaroslav Kysela wrote:
Could you describe more? Services are duplicated ? Assigned to wrong muxes etc?
Yes, there are a lot of duplicated services with super-high services ids and blank service names like in this picture: http://i.imgur.com/SIMHbZi.png
The mux page seems normal: http://i.imgur.com/8Cmid85.png
Updated by Jaroslav Kysela over 9 years ago
Compile tvh with --enable-trace and use '--debug all --trace pat,pmt,sdt,nit,bat -l <logfile>' to create the <logfile>. Wait until you see 'mpegts: add service' messages and if this service is wrong, provide the logfile to analyze.
Updated by Bruno Bastos over 9 years ago
- File tvheadend.log tvheadend.log added
Log attached.
Thank you.
Updated by Jaroslav Kysela over 9 years ago
Bruno Bastos wrote:
Log attached.
Thank you.
There are no newly added services in the log. The 'add service' lines at tvh start just means that services are loaded from the configuration files.
Updated by Bruno Bastos over 9 years ago
Jaroslav Kysela wrote:
Bruno Bastos wrote:
Log attached.
Thank you.
There are no newly added services in the log. The 'add service' lines at tvh start just means that services are loaded from the configuration files.
Sorry, I'll let it running until I see the message you told me. Is it ok to use the following command monitor the output?
$ tail -f /tmp/tvheadend.log | grep 'mpegts: add service'
Just for information, now I have 8854 services found: http://i.imgur.com/KyDDQJm.png
Updated by Bruno Bastos over 9 years ago
- File tvheadend.log tvheadend.log added
EDIT: Added another log.
Updated by Jaroslav Kysela over 9 years ago
It's same. I see only added services when tvh starts. No other services were added later. Perhaps, you may try to remove all services without name (unused) in the service grid and restart tvh.
2015-03-31 15:51:08.566 [ DEBUG]:mpegts: 411MHz in NET - add service 0052 (null) 2015-03-31 15:51:08.622 [ DEBUG]:mpegts: 249MHz in NET - add service 0052 Animal Planet 2015-03-31 15:51:08.707 [ DEBUG]:mpegts: 237MHz in NET - add service 0052 (null) 2015-03-31 15:51:08.775 [ DEBUG]:mpegts: 399MHz in NET - add service 0052 (null) 2015-03-31 15:51:09.025 [ DEBUG]:mpegts: 309MHz in NET - add service 0052 (null)
But see above. It seems that services are detected for all muxes. I saw this behaviour when the linuxdvb driver (kernel driver) do not flush the buffers from previous tuning correctly, so data from previous mux were received and tvh parsers were confused, because they had information "hey, the current mux has these services", but it was not true. There is option in the tuner settings like "multiple tuning". You may try it. Eventually, you may discuss this with the driver author.
Updated by Bruno Bastos over 9 years ago
- File tvheadend.log tvheadend.log added
Ok, did what you have suggested, I've deleted all invalid services and waited for invalid services be added.
Updated by Jaroslav Kysela over 9 years ago
Thanks. It's now opposite situation - I tried to verify some added services, but they appear are good. OK. Let's try to finish the scan of all muxes after the null services removal (of all muxes) and try to provide next log for newly added services after the scan to check only those.
Updated by Bruno Bastos over 9 years ago
- File tvheadend.log tvheadend.log added
Jaroslav Kysela wrote:
Thanks. It's now opposite situation - I tried to verify some added services, but they appear are good. OK. Let's try to finish the scan of all muxes after the null services removal (of all muxes) and try to provide next log for newly added services after the scan to check only those.
Thank you @Jaroslav.
I've cleaned all null services again and forced a full scan of all muxes through tvh interface. Log is attached.
Updated by Jaroslav Kysela over 9 years ago
- Status changed from New to Fixed
I think that I fixed the null service issues with commit v4.1-78-gb5f23b3 . The problem was that CRC (4 byte) was parsed like a new service in PAT. Closing, re-open if you see null services in recent tvh.