Sat > IP:configuration fails

Added by Christian Karmel over 9 years ago

Hi all,

I'm writing my first post here, but tried to read every related post before.

I've got a GSS.box (Sat > IP Server) which works very well in my network with different clients (SatIP DVBViewer, DVBLink, Elegato App), but I can't get it to work with TVH.
I installed build 3.9.2479-1 from http://syno.dierkse.nl/ on my Synology Diskstation (x64).

The gss.box was found, i created network and mux entry. But mux scan always fails (Scan Result = fail).
Here is the full log:

2015-02-11 08:13:12.358 [  DEBUG]:settings: saving to /volume1/@appstore/tvheadend-testing/var/input/satip/adapters/d72d26bfcd28fe94bee703db18ef49c0
2015-02-11 08:15:05.413 [  DEBUG]:mpegts: Sat 2 IP (19,2) - adding mux 10744H in Sat 2 IP (19,2) to scan queue weight 6 flags 0080
2015-02-11 08:15:05.413 [   INFO]:mpegts: 10744H in Sat 2 IP (19,2) - tuning on SAT>IP DVB-S Tuner #1 (192.168.0.100)
2015-02-11 08:15:05.413 [  DEBUG]:satip: SAT>IP DVB-S Tuner #1 (192.168.0.100) - starting 10744H in Sat 2 IP (19,2)
2015-02-11 08:15:05.413 [  DEBUG]:mpegts: 10744H in Sat 2 IP (19,2) - started
2015-02-11 08:15:05.416 [  DEBUG]:mpegts: 10744H in Sat 2 IP (19,2) - open PID 0012 (18) [3/0xca8c90]
2015-02-11 08:15:05.416 [  DEBUG]:eit: installed table handlers
2015-02-11 08:15:05.416 [  DEBUG]:eit: grab started
2015-02-11 08:15:05.416 [  DEBUG]:mpegts: 10744H in Sat 2 IP (19,2) - open PID 0BBA (3002) [2/0xcaa100]
2015-02-11 08:15:05.416 [  DEBUG]:mpegts: 10744H in Sat 2 IP (19,2) - open PID 0BBB (3003) [2/0xcab570]
2015-02-11 08:15:05.416 [  DEBUG]:uk_freesat: installed table handlers
2015-02-11 08:15:05.416 [  DEBUG]:uk_freesat: grab started
2015-02-11 08:15:05.416 [  DEBUG]:mpegts: 10744H in Sat 2 IP (19,2) - open PID 0039 (57) [2/0xcac9e0]
2015-02-11 08:15:05.416 [  DEBUG]:viasat_baltic: installed table handlers
2015-02-11 08:15:05.416 [  DEBUG]:viasat_baltic: grab started
2015-02-11 08:15:05.416 [   INFO]:subscription: 005D: "scan" subscribing to mux, weight: 6, adapter: "SAT>IP DVB-S Tuner #1 (192.168.0.100)", network: "Sat 2 IP (19,2)", mux: "10744H", hostname: "<N/A>", username: "<N/A>", client: "<N/A>" 
2015-02-11 08:15:05.451 [  ERROR]:satip: getaddrinfo: : No address associated with hostname
2015-02-11 08:15:05.464 [  DEBUG]:mpegts: 10744H in Sat 2 IP (19,2) - open PID 0000 (0) [3/0xcade50]
2015-02-11 08:15:05.464 [  DEBUG]:mpegts: 10744H in Sat 2 IP (19,2) - open PID 0001 (1) [2/0xcaf2c0]
2015-02-11 08:15:05.464 [  DEBUG]:mpegts: 10744H in Sat 2 IP (19,2) - open PID 0010 (16) [2/0xcb0730]
2015-02-11 08:15:05.464 [  DEBUG]:mpegts: 10744H in Sat 2 IP (19,2) - open PID 0011 (17) [3/0xcb1ba0]
2015-02-11 08:15:05.464 [  DEBUG]:mpegts: 10744H in Sat 2 IP (19,2) - open PID 0011 (17) [2/0xcb3010]
2015-02-11 08:15:15.000 [  DEBUG]:mpegts: 10744H in Sat 2 IP (19,2) - close PID 0011 (17) [3/0xcb1ba0]
2015-02-11 08:15:15.000 [  DEBUG]:mpegts: 10744H in Sat 2 IP (19,2) - close PID 0010 (16) [2/0xcb0730]
2015-02-11 08:15:15.000 [  DEBUG]:mpegts: 10744H in Sat 2 IP (19,2) - close PID 0001 (1) [2/0xcaf2c0]
2015-02-11 08:15:15.000 [  DEBUG]:mpegts: 10744H in Sat 2 IP (19,2) - close PID 0000 (0) [3/0xcade50]
2015-02-11 08:15:15.000 [   INFO]:mpegts: 10744H in Sat 2 IP (19,2) - scan no data, failed
2015-02-11 08:15:15.000 [   INFO]:subscription: 005D: "scan" unsubscribing
2015-02-11 08:15:15.000 [  DEBUG]:mpegts: 10744H in Sat 2 IP (19,2) - stopping mux
2015-02-11 08:15:15.000 [  DEBUG]:satip: SAT>IP DVB-S Tuner #1 (192.168.0.100) - stopping 10744H in Sat 2 IP (19,2)
2015-02-11 08:15:15.000 [  DEBUG]:mpegts: 10744H in Sat 2 IP (19,2) - close PID 0011 (17) [2/0xcb3010]
2015-02-11 08:15:15.000 [  DEBUG]:mpegts: 10744H in Sat 2 IP (19,2) - close PID 0012 (18) [3/0xca8c90]
2015-02-11 08:15:15.000 [  DEBUG]:mpegts: 10744H in Sat 2 IP (19,2) - close PID 0039 (57) [2/0xcac9e0]
2015-02-11 08:15:15.000 [  DEBUG]:mpegts: 10744H in Sat 2 IP (19,2) - close PID 0BBA (3002) [2/0xcaa100]
2015-02-11 08:15:15.000 [  DEBUG]:mpegts: 10744H in Sat 2 IP (19,2) - close PID 0BBB (3003) [2/0xcab570]
2015-02-11 08:15:15.000 [  DEBUG]:mpegts: Sat 2 IP (19,2) - removing mux 10744H in Sat 2 IP (19,2) from scan queue
2015-02-11 08:15:15.000 [  DEBUG]:mpegts: Sat 2 IP (19,2) - adding mux 10744H in Sat 2 IP (19,2) to scan queue weight 6 flags 00A0
2015-02-11 08:15:15.000 [  DEBUG]:epggrab: grab done for 10744H in Sat 2 IP (19,2) (stolen)
2015-02-11 08:15:15.000 [  DEBUG]:mpegts: Sat 2 IP (19,2) - removing mux 10744H in Sat 2 IP (19,2) from scan queue

(I already know that "[ERROR]:satip: getaddrinfo: : No address associated with hostname" is caused by the empty "Local bind IP address"-field from adapter config. But in my understanding this does not cause the fail.)

I now tried to make it run for 2 evenings and have no idea what to change anymore or what went wrong,

any help is greatly appreciated,
regards,
Christian

I attache images from my settings:

sat2ip_1_tvadapters.png (65.6 KB) sat2ip_1_tvadapters.png
sat2ip_2_tvadapters.png (74.2 KB) sat2ip_2_tvadapters.png
sat2ip_3_tvadapters.png (62.2 KB) sat2ip_3_tvadapters.png
sat2ip_4_networks.png (62.9 KB) sat2ip_4_networks.png
sat2ip_5_muxes.png (67.1 KB) sat2ip_5_muxes.png

Replies (2)

RE: Sat > IP:configuration fails - Added by Wouter Moeken over 9 years ago

Heya,

First of all, your symbol rate is missing 3 '0's. (Should be 22000000). I've had issues with this box in that it would discover all muxes, but fails to scan a single one of them. I think it's related to the fast scanning of the muxes as one would succeed and the next ones would fail.

I've attached my settings for the mux of which you attached the screenshot.
If after discovering most muxes fail to scan, try and do a single mux scan (by setting the scan state for the mux to pending) and see if that works.

19.2-10744H.png (27.1 KB) 19.2-10744H.png

10744H Mux

RE: Sat > IP:configuration fails - Added by Christian Karmel over 9 years ago

Thank you very much Wouter,

your 'by setting the scan state for the mux to pending' does the trick.
After adding muxes manually/automatically the first test failed all the time.
Even if I selected a network a pushed the "Force Scan" button for scanning all muxes didn't work.
(the Symbolrate was correct most the time, I tried some other values at the time of th screenshot)

I don't know why, but i tried changing to 'Pend' (and the coming 'Active') several times and suddenly it started working for nearly all muxes.

So, it is working now,
I'm happy,
best regards,
Christian

(1-2/2)

Project

General

Profile

Tvheadend