Solved - Network scanning fails
Added by Yann Ormanns about 6 years ago
Hi everyone,
I am using tvheadend 4.2.6-62 on my Kodi HTPC (LibreELEC), and now I want to switch the setup to a 24/7 system. This system runs on Gentoo, and I simply do not manage tvheadend to scan the network successfully.
I use a Fritz!Box 6490 with Fritz!OS 7 as a Sat>IP streaming server - so I pass the argument "--satip_xml http://10.0.0.1:49000/satipdesc.xml" to tvheadend.
Aside my HTPC, I have tested a few versions:
- 4.2.7-17 on Ubuntu
- 4.3-1216 on Gentoo
- 4.3-1517 on Gentoo
Everyone of them is unable to get some data in while scanning the network, as the following log lines from the newest build show:
2018-11-02 17:56:07.851 [ INFO]:subscription: 0074: "scan" subscribing to mux "402MHz", weight: 6, adapter: "SAT>IP DVB-C Tuner #1 (10.0.0.1@UDP)", network: "DVB-C Netzwerk", service: "Raw PID Subscription" 2018-11-02 17:56:07.851 [ INFO]:mpegts: 610MHz in DVB-C Netzwerk - tuning on SAT>IP DVB-C Tuner #2 (10.0.0.1@UDP) 2018-11-02 17:56:07.851 [ INFO]:subscription: 0075: "scan" subscribing to mux "610MHz", weight: 6, adapter: "SAT>IP DVB-C Tuner #2 (10.0.0.1@UDP)", network: "DVB-C Netzwerk", service: "Raw PID Subscription" 2018-11-02 17:56:07.851 [ INFO]:mpegts: 434MHz in DVB-C Netzwerk - tuning on SAT>IP DVB-C Tuner #3 (10.0.0.1@UDP) 2018-11-02 17:56:07.851 [ INFO]:subscription: 0076: "scan" subscribing to mux "434MHz", weight: 6, adapter: "SAT>IP DVB-C Tuner #3 (10.0.0.1@UDP)", network: "DVB-C Netzwerk", service: "Raw PID Subscription" 2018-11-02 17:56:07.851 [ INFO]:mpegts: 362MHz in DVB-C Netzwerk - tuning on SAT>IP DVB-C Tuner #4 (10.0.0.1@UDP) 2018-11-02 17:56:07.851 [ INFO]:subscription: 0077: "scan" subscribing to mux "362MHz", weight: 6, adapter: "SAT>IP DVB-C Tuner #4 (10.0.0.1@UDP)", network: "DVB-C Netzwerk", service: "Raw PID Subscription" 2018-11-02 17:56:12.850 [ INFO]:mpegts: 362MHz in DVB-C Netzwerk - scan no data, failed 2018-11-02 17:56:12.850 [ INFO]:subscription: 0077: "scan" unsubscribing 2018-11-02 17:56:12.851 [ INFO]:mpegts: 434MHz in DVB-C Netzwerk - scan no data, failed 2018-11-02 17:56:12.851 [ INFO]:subscription: 0076: "scan" unsubscribing 2018-11-02 17:56:12.851 [ INFO]:mpegts: 610MHz in DVB-C Netzwerk - scan no data, failed 2018-11-02 17:56:12.851 [ INFO]:subscription: 0075: "scan" unsubscribing 2018-11-02 17:56:12.851 [ INFO]:mpegts: 402MHz in DVB-C Netzwerk - scan no data, failed 2018-11-02 17:56:12.851 [ INFO]:subscription: 0074: "scan" unsubscribing
My config under the newest build (the tuners have a slightly different config, because I tested the impact of the "specinv" parameter):
{ "tunercfgu": "Auto", "tcp_mode": false, "fast_switch": true, "fullmux_ok": false, "sigscale": 240, "pids_max": 32, "pids_len": 127, "pids_deladd": false, "fe": true, "piloton": false, "pids21": true, "skip_ts": 0, "disableworkarounds": false, "device_uuid": "663d5d6c-f9f8-4bb4-84d4-444E6D2A2DDF", "frontends": { "DVB-C #1": { "delsys": 0, "transport_mode": 0, "udp_rtp_port": 0, "tdelay": 50, "play2": true, "grace_period": 0, "teardown_delay": false, "pass_weight": 1, "specinv": 1, "enabled": true, "priority": 0, "spriority": 0, "displayname": "SAT>IP DVB-C Tuner", "ota_epg": false, "initscan": false, "idlescan": false, "free_weight": 0, "remove_scrambled": false, "networks": [ "3d276401e06bc0c924cf3e94b581833b" ], "linked": "", "type": "DVB-C", "uuid": "783c66242e42be1959296f358a7668f8" }, "DVB-C #2": { "delsys": 0, "transport_mode": 0, "udp_rtp_port": 0, "tdelay": 50, "play2": true, "grace_period": 0, "teardown_delay": false, "pass_weight": 1, "specinv": 1, "tunerbindaddr": "", "enabled": true, "priority": 0, "spriority": 0, "displayname": "SAT>IP DVB-C Tuner", "ota_epg": false, "initscan": false, "idlescan": false, "free_weight": 0, "remove_scrambled": false, "networks": [ "3d276401e06bc0c924cf3e94b581833b" ], "linked": "", "type": "DVB-C", "uuid": "aca1f336b31c6552d43eb555ea1ca6b7" }, "DVB-C #3": { "delsys": 0, "transport_mode": 0, "udp_rtp_port": 0, "tdelay": 50, "play2": true, "grace_period": 0, "teardown_delay": false, "pass_weight": 1, "specinv": 2, "enabled": true, "priority": 0, "spriority": 0, "displayname": "SAT>IP DVB-C Tuner", "ota_epg": false, "initscan": false, "idlescan": false, "free_weight": 0, "remove_scrambled": false, "networks": [ "3d276401e06bc0c924cf3e94b581833b" ], "linked": "", "type": "DVB-C", "uuid": "4ac81c649fd42d421cbabed680f64c0b" }, "DVB-C #4": { "delsys": 0, "transport_mode": 0, "udp_rtp_port": 0, "tdelay": 50, "play2": true, "grace_period": 0, "teardown_delay": false, "pass_weight": 1, "specinv": 2, "enabled": true, "priority": 0, "spriority": 0, "displayname": "SAT>IP DVB-C Tuner", "ota_epg": false, "initscan": false, "idlescan": false, "free_weight": 0, "remove_scrambled": false, "networks": [ "3d276401e06bc0c924cf3e94b581833b" ], "linked": "", "type": "DVB-C", "uuid": "356e1cbe1d430d3bb6fcecdbcbac5fce" } } }
What can I do to locate the cause for this problem? If any information is missing, please let me know.
Kind regards,
Yann
Replies (26)
RE: Network scanning fails - Added by Yann Ormanns almost 6 years ago
...do I need any kernel modifications? Since I allow all traffic between the tvheadend system and my Fritz!Box, firewall rules should not be the cause for this problem.
Kind regards,
Yann
RE: Network scanning fails - Added by Al Bundy almost 6 years ago
I'm using also tuners from my fritzbox.
I think I have used one of the first results from google.
https://www.google.de/search?q=frotzbox+tvheadend&oq=frotzbox+tvheadend
You need to create one interface for each tuner and have to set your tuner count in the tvh webinterface.
RE: Network scanning fails - Added by Yann Ormanns almost 6 years ago
Which OS do you use? Binding the tuners to specific interfaces / IP addresses should not make any difference - since 1) AFAIK the "one stream per IP address" restriction was removed with Fritz!OS 7 and 2) my Kodi HTPC works out of the box with all 4 streams.
Kind regards,
Yann
RE: Network scanning fails - Added by Al Bundy almost 6 years ago
I'm running tvheadend on a raspberry pi with raspbian stretch.
If I remember correctly tvheadend showed the tuners automatically and I had to bind the tuners to an interface.
I'm not sure but I think I didn't have to add satip_xml somewhere.
RE: Network scanning fails - Added by Yann Ormanns almost 6 years ago
Without the satip-parameter, tvheadend does not find my tuners - if I remember correctly.
Kind regards,
Yann
RE: Network scanning fails - Added by Al Bundy almost 6 years ago
Btw. I'm running 4.3-1504~g1fc3b3c4c (build from github).
RE: Network scanning fails - Added by Al Bundy almost 6 years ago
According to https://tvheadend.org/boards/4/topics/29307 tvheadend showed the tuners in my case automatically.
I've checked /etc/init.d/tvheadend - there is no satip parameter set.
RE: Network scanning fails - Added by Yann Ormanns almost 6 years ago
I just retried it with 4.3-1517 - without the satip_xml parameter, tvheadend does not find any tuners.
According to the blog posting you referred to in your linked thread, this parameter has to be added ("First open /etc/init.d/tvheadend, find the line reading ARGS="-f" and append something like --satip_xml http://192.168.1.1:49000/satipdesc.xml within the quotes. save the file and restart Tvheadend.").
Kind regards,
Yann
RE: Network scanning fails - Added by Al Bundy almost 6 years ago
I know but as written in the other post tvheadend has shown the tuners automatically.
Before I bought the FritzBox I thought I had to use the Fritzapp to watch tv.
Only because tvheadend has shown the tuners I started to investigate how to use them.
Also my init-skript does not contain the argument.
I'm not sure if I have used the linked page because I thought it has looked different.
RE: Network scanning fails - Added by Al Bundy almost 6 years ago
Have you checked if you can watch tv with the fritzapp?
You can also check the streams in your fritzbox (dvb-c/live-tv)
RE: Network scanning fails - Added by Yann Ormanns almost 6 years ago
Well, since I can watch TV on my Kodi HTPC, the Fritz!Box should not be the problem :-)
I just want to move the tvheadend server to a different machine, which is running 24/7.
Kind regards,
Yann
RE: Network scanning fails - Added by Al Bundy almost 6 years ago
Was your htpc running while you've tried to scan the channels on the other pc?
You can also try to enable only one tuner in tvh and bind it to your ip.
RE: Network scanning fails - Added by Yann Ormanns almost 6 years ago
It had not effect, if the HTPC is running or not (I had both situations).
The HTPC can use up to all 4 streams simultaneously.
But for debugging purposes, I also tried using only one tuner, which had no effect at all.
Just to sum it up: I read a whole bunch of guides and tutorials, but at the point, where everybody scans the network and gets some content, I only get error messages.
Kind regards,
Yann
RE: Network scanning fails - Added by Al Bundy almost 6 years ago
What error messages?
Is your new pc in the same subnet as your fritzbox?
According to my webinterface the tuners are using udp.
You can also try to compare your tuner settings from yoir working htpc with you new machine.
RE: Network scanning fails - Added by Yann Ormanns almost 6 years ago
The error messages are quoted in the first posting of this thread:
2018-11-02 17:56:07.851 [ INFO]:subscription: 0074: "scan" subscribing to mux "402MHz", weight: 6, adapter: "SAT>IP DVB-C Tuner #1 (10.0.0.1@UDP)", network: "DVB-C Netzwerk", service: "Raw PID Subscription"
2018-11-02 17:56:07.851 [ INFO]:mpegts: 610MHz in DVB-C Netzwerk - tuning on SAT>IP DVB-C Tuner #2 (10.0.0.1@UDP)
2018-11-02 17:56:07.851 [ INFO]:subscription: 0075: "scan" subscribing to mux "610MHz", weight: 6, adapter: "SAT>IP DVB-C Tuner #2 (10.0.0.1@UDP)", network: "DVB-C Netzwerk", service: "Raw PID Subscription"
2018-11-02 17:56:07.851 [ INFO]:mpegts: 434MHz in DVB-C Netzwerk - tuning on SAT>IP DVB-C Tuner #3 (10.0.0.1@UDP)
2018-11-02 17:56:07.851 [ INFO]:subscription: 0076: "scan" subscribing to mux "434MHz", weight: 6, adapter: "SAT>IP DVB-C Tuner #3 (10.0.0.1@UDP)", network: "DVB-C Netzwerk", service: "Raw PID Subscription"
2018-11-02 17:56:07.851 [ INFO]:mpegts: 362MHz in DVB-C Netzwerk - tuning on SAT>IP DVB-C Tuner #4 (10.0.0.1@UDP)
2018-11-02 17:56:07.851 [ INFO]:subscription: 0077: "scan" subscribing to mux "362MHz", weight: 6, adapter: "SAT>IP DVB-C Tuner #4 (10.0.0.1@UDP)", network: "DVB-C Netzwerk", service: "Raw PID Subscription"
2018-11-02 17:56:12.850 [ INFO]:mpegts: 362MHz in DVB-C Netzwerk - scan no data, failed
2018-11-02 17:56:12.850 [ INFO]:subscription: 0077: "scan" unsubscribing
2018-11-02 17:56:12.851 [ INFO]:mpegts: 434MHz in DVB-C Netzwerk - scan no data, failed
2018-11-02 17:56:12.851 [ INFO]:subscription: 0076: "scan" unsubscribing
2018-11-02 17:56:12.851 [ INFO]:mpegts: 610MHz in DVB-C Netzwerk - scan no data, failed
2018-11-02 17:56:12.851 [ INFO]:subscription: 0075: "scan" unsubscribing
2018-11-02 17:56:12.851 [ INFO]:mpegts: 402MHz in DVB-C Netzwerk - scan no data, failed
2018-11-02 17:56:12.851 [ INFO]:subscription: 0074: "scan" unsubscribing
All affected systems are in the same subnet.
I already copied the config from the HTPC to the second system, but without success - the problem persisted. Tomorrow, I am going to check the running processes and used ports again,
Kind regards,
Yann
RE: Network scanning fails - Added by Yann Ormanns almost 6 years ago
Again, I copied the working config from my HTPC (4.2.6-62) to my Gentoo system (4.3-1517).
I get the errors I posted before, and some which I forgot to mention yet:
"[ ERROR] satip: SAT>IP DVB-C Tuner #1 (10.0.0.1@UDP) - RTSP cmd error 7 (Unbekannter Fehler -7) [8-408]"
So, I assume the cause for this problem either in missing kernel modules or in system config parameters.
Kind regards,
Yann
RE: Network scanning fails - Added by Al Bundy almost 6 years ago
If you search on google for this error you'll see that you are not alone.
Have you tried to setup tvheadend from scratch (without copying the config)?
Have also a look on this bug - sounds similar to your problem.
https://tvheadend.org/issues/5231
RE: Network scanning fails - Added by Yann Ormanns almost 6 years ago
Yep, I have reinstalled tvheadend for about 20 times now :-)
Kind regards,
Yann
RE: Network scanning fails - Added by Al Bundy almost 6 years ago
Without copying anything from existing installations?
Have you checked the linked issue?
My Fritzbox is also up-to-date, the mentioned setting is also done and I don't have this issue.
RE: Network scanning fails - Added by Yann Ormanns almost 6 years ago
Yeah, I re-installed tvheadend a couple of times and re-configured it from scratch everytime (deleted /etc/tvheadend or /root/.hts).
I also checked the "pass specinv" settings, as I wrote in my first posting: "My config under the newest build (the tuners have a slightly different config, because I tested the impact of the "specinv" parameter):".
That's why I am assuming a not fulfilled requirement in the kernel or OS.
Kind regards,
Yann
RE: Network scanning fails - Added by Al Bundy almost 6 years ago
Did you modify the settings in web interface or in the config-files?
I make my changes always in the web interface.
According to my adapter configurations specinv is set to 0.
If you think it's OS or kernel related you can try to install the same os on your htpc.
RE: Network scanning fails - Added by Yann Ormanns almost 6 years ago
I always configured tvheadend by using the web gui wizard.
Setting up LibreELEC on my fileserver is no solution - I will keep Gentoo ;-)
But at least, I managed to get tvheadend running on my Xubuntu laptop now. Before, scanning always failed, but now for some reason, it works. I am currently searching the differences between both systems.
Kind regards,
Yann
RE: Network scanning fails - Added by Yann Ormanns almost 6 years ago
What the hell - I let tvheadend once again scan for new muxes and left my pc alone. About 30 minutes later, I looked into my log files, and man many tv and radio stations were found. Seems like only the initial scan failed, but a second (automatic) scan worked. I will now check, if it really works...
Kind regards,
Yann
RE: Network scanning fails - Added by Al Bundy almost 6 years ago
Hmm - I had a similar issue these days.
In my case some channels where missing after scan.
After manually changing status on muxes from ACTIVE to IDLE and a rescan all channels where found.
RE: Network scanning fails - Added by Yann Ormanns almost 6 years ago
Unfortunately, it still does not work yet. Although tvheadend could scan successfully, every scan afterwars failed. So I am beginning from scratch again.
Kind regards,
Yann