Bug #2476
TVHeadend does not detect any muxes on new setup
0%
Description
This is true for the preset muxes of "Ziggo-netherlands"
Syslog - Ubuntu LTS 14.04 - 64bit
Nov 13 16:49:02 server01 tvheadend6083: HTTP: 192.168.178.21: /api/mpegts/input/network_list -- 400
Nov 13 16:49:02 server01 tvheadend6083: HTTP: 192.168.178.21: /api/mpegts/input/network_list -- 400
Nov 13 16:49:03 server01 tvheadend6083: mpegts: 356MHz in Ziggo - scan no data, failed
Nov 13 16:49:03 server01 tvheadend6083: subscription: 0003: "scan" unsubscribing
Nov 13 16:49:03 server01 tvheadend6083: mpegts: 372MHz in Ziggo - tuning on Sundtek DVB-C : DVB-C #0
Nov 13 16:49:07 server01 tvheadend6083: subscription: 0004: "scan" subscribing to mux, weight: 5, adapter: "Sundtek DVB-C : DVB-C #0", network: "Ziggo", mux: "372MHz"
, hostname: "<N/A>", username: "<N/A>", client: "<N/A>"
Nov 13 16:49:07 server01 tvheadend6083: HTTP: 192.168.178.21: /api/mpegts/input/network_list -- 400
Nov 13 16:49:08 server01 tvheadend6083: mpegts: 372MHz in Ziggo - scan no data, failed
Nov 13 16:49:08 server01 tvheadend6083: subscription: 0004: "scan" unsubscribing
Nov 13 16:49:08 server01 tvheadend6083: mpegts: 369MHz in Ziggo - tuning on Sundtek DVB-C : DVB-C #0
Nov 13 16:49:12 server01 tvheadend6083: subscription: 0005: "scan" subscribing to mux, weight: 5, adapter: "Sundtek DVB-C : DVB-C #0", network: "Ziggo", mux: "369MHz"
, hostname: "<N/A>", username: "<N/A>", client: "<N/A>"
Nov 13 16:49:12 server01 tvheadend6083: HTTP: 192.168.178.21: /api/mpegts/input/network_list -- 400
Nov 13 16:49:12 server01 tvheadend6083: HTTP: 192.168.178.21: /api/mpegts/input/network_list -- 400
Nov 13 16:49:13 server01 tvheadend6083: mpegts: 369MHz in Ziggo - scan no data, failed
Nov 13 16:49:13 server01 tvheadend6083: subscription: 0005: "scan" unsubscribing
Nov 13 16:49:13 server01 tvheadend6083: HTTP: 192.168.178.21: /api/mpegts/input/network_list -- 400
Nov 13 16:49:14 server01 tvheadend6083: mpegts: 369MHz in Ziggo - tuning on Sundtek DVB-C : DVB-C #0
Nov 13 16:49:18 server01 tvheadend6083: subscription: 0006: "epggrab" subscribing to mux, weight: 3, adapter: "Sundtek DVB-C : DVB-C #0", network: "Ziggo", mux: "369M
Hz", hostname: "<N/A>", username: "<N/A>", client: "<N/A>"
Nov 13 16:49:39 server01 tvheadend6083: subscription: 0006: "epggrab" unsubscribing
Nov 13 16:49:50 server01 tvheadend6083: mpegts: 372MHz in Ziggo - tuning on Sundtek DVB-C : DVB-C #0
Nov 13 16:49:54 server01 tvheadend6083: subscription: 0007: "epggrab" subscribing to mux, weight: 3, adapter: "Sundtek DVB-C : DVB-C #0", network: "Ziggo", mux: "372M
Hz", hostname: "<N/A>", username: "<N/A>", client: "<N/A>"
Nov 13 16:50:15 server01 tvheadend6083: subscription: 0007: "epggrab" unsubscribing
Nov 13 16:50:26 server01 tvheadend6083: mpegts: 356MHz in Ziggo - tuning on Sundtek DVB-C : DVB-C #0
Nov 13 16:50:30 server01 tvheadend6083: subscription: 0008: "epggrab" subscribing to mux, weight: 3, adapter: "Sundtek DVB-C : DVB-C #0", network: "Ziggo", mux: "356M
Hz", hostname: "<N/A>", username: "<N/A>", client: "<N/A>"
Nov 13 16:50:51 server01 tvheadend6083: subscription: 0008: "epggrab" unsubscribing
Nov 13 16:51:02 server01 tvheadend6083: mpegts: 514MHz in Ziggo - tuning on Sundtek DVB-C : DVB-C #0
Nov 13 16:51:07 server01 tvheadend6083: subscription: 0009: "epggrab" subscribing to mux, weight: 3, adapter: "Sundtek DVB-C : DVB-C #0", network: "Ziggo", mux: "514M
Hz", hostname: "<N/A>", username: "<N/A>", client: "<N/A>"
Nov 13 16:51:27 server01 tvheadend6083: subscription: 0009: "epggrab" unsubscribing
History
Updated by
Updated by Bas S about 10 years ago
Updated by Jaroslav Kysela wrote:
Which last version works for you ?
Last one I used was: 4bf8754ef33d925a382f48858cd3d3fd2dc31319
I updated because I was upgrading the server...
So I do not think this info will help much since it is quite an enormous timespan.
But hope to see it fixed soon, the wife gets grumpy 
Updated by Bas S about 10 years ago
Additional, the problems started after I deleted my working mux.
This did I because I had blocks in my Discovery Channel HD and was not seeing any error packets in the status screen.
So that it does not work cannot be related to other system upgrades/updates...
Updated by Jaroslav Kysela about 10 years ago
Have you checked, if the mux parameters are same as before ? Perhaps, the scanfile parser is broken somehow..
Updated by Bas S about 10 years ago
I found the problem. Ziggo updated its main multiplexer. Probably all 4 are not needed anymore and are replaced by the one included in the page below:
https://www.ziggo.nl/klantenservice/televisie-radio/installeren/frequenties-netwerknummers
I am not a developper so please check in advance. However this frequency gives me all myxes again. So I think the
tvheadend/data/dvb-scan/dvb-c/nl-Ziggo
need to be updated.
Updated by Bas S about 10 years ago
Jaroslav Kysela wrote:
Have you checked, if the mux parameters are same as before ? Perhaps, the scanfile parser is broken somehow..
Thnx for the tip, assumption was that so many people use this, it would probably be already be found as incorrect.
Now it is
Updated by Jaroslav Kysela about 10 years ago
- Category changed from Muxers to Configuration
- Status changed from New to Rejected
- Assignee changed from John Törnblom to Jaroslav Kysela
The nl-Ziggo file is grabbed from the dtv-scan-tables.git - http://www.linuxtv.org/wiki/index.php/Dtv-scan-tables . I would suggest to send this information to Mauro Carvalho Chehab to correct this. Marking as rejected, because it's not a direct tvh bug..