dbox2 server won't work

grabtom

unread,

Jan 2, 2012, 9:13:15 PM1/2/12

to vtuner-en-user

I try run vtunerd.db2 on my dbox2 (latest Keywelt Image) and vtunerc
on Ubuntu 10.10. It connected but don't work.

Log from dbox (server):

/var/bin # export VTUNERD_DEBUG_LEVEL=4; vtunerd
vtunerd: [847 ../../vtuner-dvb-3.c:57] info: FE_GET_INFO dvb-type:0
vtuner-type:1
vtunerd: [847 ../../vtunerd.c:84] info: adapter:0, frontend:0, demux,
0, dvr:0 is type:1
vtunerd: [847 ../../vtunerd-service.c:35] debug: autodiscover socket
bound
vtunerd: [847 ../../vtunerd-service.c:261] info: waiting for
autodiscover packet ...
vtunerd: [847 ../../vtunerd-service.c:265] debug: request received
vtunerd: [847 ../../vtunerd.c:99] info: received discover request,
vtuner_type:1
vtunerd: [847 ../../vtunerd.c:103] debug: session status:0 session
type:1 tuner_type:1 match:1
vtunerd: [847 ../../vtunerd-service.c:261] info: waiting for
autodiscover packet ...
vtunerd: [850 ../../vtuner-dvb-3.c:57] info: FE_GET_INFO dvb-type:0
vtuner-type:1
vtunerd: [850 ../../vtunerd-service.c:67] info: anon stream socket
prepared 38
vtunerd: [850 ../../vtunerd-service.c:302] info: control socket bound
to 1472
vtunerd: [850 ../../vtunerd-service.c:67] info: anon stream socket
prepared 39
vtunerd: [850 ../../vtunerd-service.c:315] info: session prepared
control:1472 data:1473
vtunerd: [850 ../../vtunerd-service.c:318] debug: Answered discover
request
vtunerd: [852 ../../vtunerd-service.c:133] debug: tsdata_worker thread
started.
vtunerd: [852 ../../vtunerd-service.c:82] debug: setsockopt
TCP_NODELAY 1 successful
vtunerd: [852 ../../vtunerd-service.c:88] debug: setsockopt
SO_KEEPALIVE 1 successful
vtunerd: [852 ../../vtunerd-service.c:95] debug: setsockopt
TCP_KEEPIDLE 15 successful
vtunerd: [852 ../../vtunerd-service.c:102] debug: setsockopt
TCP_KEEPCNT 2 successful
vtunerd: [852 ../../vtunerd-service.c:109] debug: setsockopt
TCP_KEEPINTVL 2 successful
vtunerd: [850 ../../vtunerd-service.c:82] debug: setsockopt
TCP_NODELAY 1 successful
vtunerd: [850 ../../vtunerd-service.c:88] debug: setsockopt
SO_KEEPALIVE 1 successful
vtunerd: [850 ../../vtunerd-service.c:95] debug: setsockopt
TCP_KEEPIDLE 15 successful
vtunerd: [850 ../../vtunerd-service.c:102] debug: setsockopt
TCP_KEEPCNT 2 successful
vtunerd: [850 ../../vtunerd-service.c:109] debug: setsockopt
TCP_KEEPINTVL 2 successful
vtunerd: [850 ../../vtunerd-service.c:345] info: session running
vtunerd: [850 ../../vtunerd-service.c:350] debug: control message
received
vtunerd: [850 ../../vtunerd-service.c:450] warn: received out-of-state
control message: 33555456
vtunerd: [850 ../../vtunerd-service.c:350] debug: control message
received
vtunerd: [850 ../../vtunerd-service.c:450] warn: received out-of-state
control message: 33554440
vtunerd: [850 ../../vtunerd-service.c:350] debug: control message
received
vtunerd: [850 ../../vtunerd-service.c:450] warn: received out-of-state
control message: 33554441
...

Log from Ubuntu (client):

sudo vtunerc -f S -v 4
vtunerc: vtuner client (vtunerc), part of vtuner project
Visit http://code.google.com/p/vtuner/ for more information
Copyright (C) 2009-11 Roland Mieslinger
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS
FOR A PARTICULAR PURPOSE.
vtunerc: Revision:63f73de8b63c/tip DVB:5.1 allow:5.x NetProto:2
MsgSize:96, Debug:4
vtunerc: [2187 ../../vtunerc.c:452] info: added frontend mode DVB-S
as mode 0, searching for tuner types 1
vtunerc: [2187 ../../vtunerc.c:533] info: Created pidfile /var/run/
vtunerc0.pid
vtunerc: [2187 ../../vtunerc.c:586] info: no server connected.
discover thread is 0 (DWS_IDLE:0, DWS_RUNNING:1)
vtunerc: [2187 ../../vtunerc.c:588] info: changing frontend mode to
DVB-S
vtunerc: [2187 ../../vtunerc.c:617] info: Start discover worker for
device type 1 groups ffff
vtunerc: [2187 ../../vtunerc.c:214] info: starting discover thread
vtunerc: [2187 ../../vtuner-network.c:168] debug: v0/0 1025 1
vtunerc: [2187 ../../vtuner-network.c:259] debug: 104 1000000
vtunerc: [2187 ../../vtunerc.c:258] info: Sending discover message
for device types 1
vtunerc: [2187 ../../vtuner-network.c:269] debug: v0/0 260 0
vtunerc: [2187 ../../vtuner-network.c:275] debug: 1025 0
vtunerc: [2187 ../../vtuner-network.c:360] debug:
vtunerc: [2187 ../../vtunerc.c:272] info: Received discover message
from 192.168.202.151 proto2 control 1482 data 1483
vtunerc: [2187 ../../vtunerc.c:637] info: connect control socket to
192.168.202.151:1482
vtunerc: [2187 ../../vtunerc.c:654] info: connected data socket to
192.168.202.151:1483
vtunerc: [2187 ../../vtuner-network.c:168] debug: v0/0 1024 1
vtunerc: [2187 ../../vtuner-network.c:259] debug: 4 1000000
vtunerc: [2187 ../../vtunerc.c:185] debug: decreased delay: bytesread:
0 rmax:130848, delay:50
vtunerc: [2187 ../../vtunerc.c:694] debug: vtuner message!
vtunerc: [2187 ../../vtuner-network.c:168] debug: v2/0 8 8
vtunerc: [2187 ../../vtuner-network.c:259] debug: 800 8000000
vtunerc: [2187 ../../vtuner-network.c:269] debug: v2/0 2048 0
vtunerc: [2187 ../../vtuner-network.c:275] debug: 8 0
vtunerc: [2187 ../../vtuner-network.c:360] debug:
vtunerc: [2187 ../../vtunerc.c:794] debug: msg: 8 completed
vtunerc: [2187 ../../vtunerc.c:694] debug: vtuner message!
vtunerc: [2187 ../../vtuner-network.c:168] debug: v2/0 9 9
vtunerc: [2187 ../../vtuner-network.c:259] debug: 900 9000000
vtunerc: [2187 ../../vtuner-network.c:269] debug: v2/0 2304 0
vtunerc: [2187 ../../vtuner-network.c:275] debug: 9 0
vtunerc: [2187 ../../vtuner-network.c:360] debug:
vtunerc: [2187 ../../vtunerc.c:794] debug: msg: 9 completed
vtunerc: [2187 ../../vtunerc.c:694] debug: vtuner message!
vtunerc: [2187 ../../vtuner-network.c:168] debug: v2/0 8 8
vtunerc: [2187 ../../vtuner-network.c:259] debug: 800 8000000
vtunerc: [2187 ../../vtuner-network.c:269] debug: v2/0 2048 0
vtunerc: [2187 ../../vtuner-network.c:275] debug: 8 0
vtunerc: [2187 ../../vtuner-network.c:360] debug:
vtunerc: [2187 ../../vtunerc.c:794] debug: msg: 8 completed
vtunerc: [2187 ../../vtunerc.c:694] debug: vtuner message!
vtunerc: [2187 ../../vtuner-network.c:168] debug: v2/0 9 9
vtunerc: [2187 ../../vtuner-network.c:259] debug: 900 9000000
vtunerc: [2187 ../../vtuner-network.c:269] debug: v2/0 2304 0
vtunerc: [2187 ../../vtuner-network.c:275] debug: 9 0
vtunerc: [2187 ../../vtuner-network.c:360] debug:
vtunerc: [2187 ../../vtunerc.c:794] debug: msg: 9 completed
vtunerc: [2187 ../../vtunerc.c:694] debug: vtuner message!
vtunerc: [2187 ../../vtuner-network.c:168] debug: v2/0 8 8
vtunerc: [2187 ../../vtuner-network.c:259] debug: 800 8000000
vtunerc: [2187 ../../vtuner-network.c:269] debug: v2/0 2048 0
vtunerc: [2187 ../../vtuner-network.c:275] debug: 8 0
vtunerc: [2187 ../../vtuner-network.c:360] debug:
vtunerc: [2187 ../../vtunerc.c:794] debug: msg: 8 completed
vtunerc: [2187 ../../vtunerc.c:694] debug: vtuner message!
vtunerc: [2187 ../../vtuner-network.c:168] debug: v2/0 9 9
vtunerc: [2187 ../../vtuner-network.c:259] debug: 900 9000000
vtunerc: [2187 ../../vtuner-network.c:269] debug: v2/0 2304 0
vtunerc: [2187 ../../vtuner-network.c:275] debug: 9 0
vtunerc: [2187 ../../vtuner-network.c:360] debug:
vtunerc: [2187 ../../vtunerc.c:794] debug: msg: 9 completed
vtunerc: [2187 ../../vtunerc.c:694] debug: vtuner message!
vtunerc: [2187 ../../vtuner-network.c:168] debug: v2/0 9 9
vtunerc: [2187 ../../vtuner-network.c:259] debug: 900 9000000
vtunerc: [2187 ../../vtuner-network.c:269] debug: v2/0 2304 0
vtunerc: [2187 ../../vtuner-network.c:275] debug: 9 0
vtunerc: [2187 ../../vtuner-network.c:360] debug:
vtunerc: [2187 ../../vtunerc.c:794] debug: msg: 9 completed
vtunerc: [2187 ../../vtunerc.c:694] debug: vtuner message!
vtunerc: [2187 ../../vtuner-network.c:168] debug: v2/0 1 1
vtunerc: [2187 ../../vtuner-network.c:173] debug: 1738000 2 27500000
5
vtunerc: [2187 ../../vtuner-network.c:179] debug: VT_S/VT_S2
vtunerc: [2187 ../../vtuner-network.c:259] debug: 100 1000000
vtunerc: [2187 ../../vtuner-network.c:269] debug: v2/0 256 0
vtunerc: [2187 ../../vtuner-network.c:275] debug: 1 0
vtunerc: [2187 ../../vtuner-network.c:285] debug: VT_S/VT_S2
vtunerc: [2187 ../../vtuner-network.c:308] debug: 1738000 2 27500000
5
vtunerc: [2187 ../../vtuner-network.c:360] debug:
vtunerc: [2187 ../../vtunerc.c:794] debug: msg: 1 completed
vtunerc: [2187 ../../vtunerc.c:694] debug: vtuner message!
vtunerc: [2187 ../../vtuner-network.c:168] debug: v2/0 3 3
vtunerc: [2187 ../../vtuner-network.c:205] debug: 1616859890
vtunerc: [2187 ../../vtuner-network.c:259] debug: 300 3000000
vtunerc: [2187 ../../vtuner-network.c:269] debug: v2/0 768 0
vtunerc: [2187 ../../vtuner-network.c:275] debug: 3 0
vtunerc: [2187 ../../vtuner-network.c:312] debug: -229482656
vtunerc: [2187 ../../vtuner-network.c:360] debug:
vtunerc: [2187 ../../vtunerc.c:794] debug: msg: 3 completed
vtunerc: [2187 ../../vtunerc.c:694] debug: vtuner message!

Also I have debian server with DVB-S card, and this one work great.
Any suggestion about dbox2 situation?

Honza Petrouš

unread,

Jan 3, 2012, 2:00:58 AM1/3/12

to vtuner-...@googlegroups.com

Hi

>
> Also I have debian server with DVB-S card, and this one work great.
> Any suggestion about dbox2 situation?

I think it is because of not having 100% backward compatibility
between vtuner network protocol original version and introduced
version2.

Same issue like http://code.google.com/p/vtuner/issues/detail?id=10

I'm going to sync binaries on code.google.com with new sources.
Unfortunatelly I don't have dbox2 hardware so I can't check myself.
Hopefully tonight I will work on updated binaries and if all goes
well I upload them to the code.google.com later today.

Honza

DJ Mastera

unread,

Oct 29, 2012, 10:32:08 AM10/29/12

to vtuner-...@googlegroups.com

Hello,

same here with dbox2 and latest binaries...

Just testing with a stand-alone server with usb dtt tuner and a dbox2 sat.

with server/dtt and dm800se as client works without issues, but dbox2 as vtuner server with issue posted above.

any news about it, a fix perhaps? :)

thanks

Honza Petrouš

unread,

Oct 31, 2012, 3:03:15 AM10/31/12

to vtuner-...@googlegroups.com

hi DJ.

> same here with dbox2 and latest binaries...
>
> Just testing with a stand-alone server with usb dtt tuner and a dbox2 sat.
> with server/dtt and dm800se as client works without issues, but dbox2 as
> vtuner server with issue posted above.
>
> any news about it, a fix perhaps? :)

Oh, I totally forgot about syncing db2 binaries.

Let me check where to get tuxbox CDK to compile them.

/Honza

DJ Mastera

unread,

Oct 31, 2012, 5:21:25 AM10/31/12

to vtuner-...@googlegroups.com

hi honza, that would be great :)

thank you...if you need help, plz tell me ;)

greetz

Von meinem iPhone gesendet

DJ Mastera

unread,

Apr 30, 2013, 7:34:52 AM4/30/13

to vtuner-...@googlegroups.com

Hey Honza,

any news about vtunerd on dbox2? perhaps any chances to sync the code to latest one?

Connection is ok, but no services found after service search on client (e.g. dm800se)...

vtunerd output on db2:

vtunerd: [223 ../../vtuner-dvb-3.c:57] info: FE_GET_INFO dvb-type:1 vtuner-type:2

vtunerd: [223 ../../vtunerd.c:84] info: adapter:0, frontend:0, demux,0, dvr:0 is type:2

vtunerd: [223 ../../vtunerd-service.c:35] debug: autodiscover socket bound

vtunerd: [223 ../../vtunerd-service.c:261] info: waiting for autodiscover packet ...

-vtunerd: [223 ../../vtunerd-service.c:265] debug: request received

vtunerd: [223 ../../vtunerd.c:99] info: received discover request, vtuner_type:2

vtunerd: [223 ../../vtunerd.c:103] debug: session status:0 session type:2 tuner_type:2 match:1

vtunerd: [223 ../../vtunerd-service.c:261] info: waiting for autodiscover packet ...

vtunerd: [226 ../../vtuner-dvb-3.c:57] info: FE_GET_INFO dvb-type:1 vtuner-type:2

vtunerd: [226 ../../vtunerd-service.c:67] info: anon stream socket prepared 39

vtunerd: [226 ../../vtunerd-service.c:302] info: control socket bound to 1024

vtunerd: [226 ../../vtunerd-service.c:67] info: anon stream socket prepared 40

vtunerd: [228 ../../vtunerd-service.c:133] debug: tsdata_worker thread started.

vtunerd: [226 ../../vtunerd-service.c:315] info: session prepared control:1024 data:1025

vtunerd: [226 ../../vtunerd-service.c:318] debug: Answered discover request

vtunerd: [226 ../../vtunerd-service.c:82] debug: setsockopt TCP_NODELAY 1 successful

vtunerd: [226 ../../vtunerd-service.c:88] debug: setsockopt SO_KEEPALIVE 1 successful

vtunerd: [226 ../../vtunerd-service.c:95] debug: setsockopt TCP_KEEPIDLE 15 successful

vtunerd: [228 ../../vtunerd-service.c:82] debug: setsockopt TCP_NODELAY 1 successful

vtunerd: [228 ../../vtunerd-service.c:88] debug: setsockopt SO_KEEPALIVE 1 successful

vtunerd: [228 ../../vtunerd-service.c:95] debug: setsockopt TCP_KEEPIDLE 15 successful

vtunerd: [226 ../../vtunerd-service.c:102] debug: setsockopt TCP_KEEPCNT 2 successful

vtunerd: [226 ../../vtunerd-service.c:109] debug: setsockopt TCP_KEEPINTVL 2 successful

vtunerd: [226 ../../vtunerd-service.c:345] info: session running