Hello
Vdr is launched in the background, but vdr-sxfe can't connect :
[1142] [input_vdr] Connecting (control) to tcp://127.0.0.1:37890 ... [1142] [input_vdr] Server not replying [1142] [input_vdr] Can't connect to tcp://127.0.0.1:37890 [1142] [input_vdr] Connections closed. [1142] [vdr-fe] fe_xine_open: xine_open("xvdr://127.0.0.1#nocache") failed Error opening xvdr://127.0.0.1
/var/log/messages seems OK :
Nov 5 22:32:09 vdrbox user.err vdr: [1105] starting plugin: xineliboutput Nov 5 22:32:09 vdrbox user.err vdr: [1111] Remote decoder/display server (cXinelibServer) thread started (pid=1105, tid=1111) Nov 5 22:32:09 vdrbox user.debug vdr: [1111] [xine..put] Have CAP_SYS_NICE capability Nov 5 22:32:09 vdrbox user.debug vdr: [1111] [xine..put] cXinelibServer priority set successful SCHED_RR 2 [1,99] Nov 5 22:32:09 vdrbox user.info vdr: [1111] [xine..put] Listening on port 37890 Nov 5 22:32:09 vdrbox user.info vdr: [1111] [xine..put] Listening for UDP broadcasts on port 37890 Nov 5 22:32:09 vdrbox user.debug vdr: [1111] [discovery] BROADCAST: VDR xineliboutput DISCOVERY 1.0^M Server port: 37890^M Server version: xi neliboutput-1.0.90-cvs^M ^M Nov 5 22:32:09 vdrbox user.debug vdr: [1105] [xine..put] cXinelibDevice::StartDevice(): Device started
I checked with netstat :
vdrbox:/# netstat -nptl Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 1003/vsftpd tcp 2 0 0.0.0.0:37890 0.0.0.0:* LISTEN 1105/vdr tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN 1120/X tcp 0 0 :::22 :::* LISTEN 1002/dropbear tcp 0 0 :::6000 :::* LISTEN 1120/X
What am I missing ? Thanks for helping.
Damien
Le 09/11/2011 00:39, Mika Laitio a écrit :
Yes I put 127.0.0.1 in /video/plugins/xineliboutput/allowed_hosts.conf with no result.
Here are the strace output for both vdr-sxfe and vdr :
http://dl.free.fr/jHubExEA3 http://dl.free.fr/g7WNGLEOn
Damien
Your vdr-xineliboutput might not be the primary output device, you must first change that before you see live video/audio.
On 9 November 2011 12:02, Damien Bally biribi@free.fr wrote:
Le 09/11/2011 11:19, Theunis Potgieter a écrit :
Your vdr-xineliboutput might not be the primary output device, you must first change that before you see live video/audio.
I tried the following command line : vdr-P"xineliboutput --local=none --primary --remote=37890"
No success.
Damien
Am Mittwoch, 9. November 2011, 15:09:16 schrieb Damien Bally:
The output of vdr-sxfe is in the attached file.
[1163] [input_vdr] Server not replying [1163] [input_vdr] Can't connect to tcp://127.0.0.1:37890
so
netstat -tulpn | grep 37890
probably does not show anything either - it should be something like tcp 0 0 0.0.0.0:37890 0.0.0.0:* LISTEN 3592/vdr udp 0 0 255.255.255.255:37890 0.0.0.0:* 3592/vdr
if netstat does show this, maybe your firewall blocks calls to this port even on localhost?
the log of vdr itself might also be interesting
Le 09/11/2011 15:48, Wolfgang Rohdewald a écrit :
LISTEN 3592/vdr
udp 0 0 255.255.255.255:37890 0.0.0.0:*
3592/vdr
This is exactly what it shows. As it is a home-made busybox environment, there is no firewall.
In attached file.
By investigating a little more, I found something odd :
As said before, launching vdr in the background with this command :
vdr -P"xineliboutput --local=none --remote=37890 --primary"
is problematic : no vdr-sxfe connection, sdvrpsend 127.0.0.1 6419 HELP gets no reply either.
However, if I start vdr and frontend together in a command like "vdr -P"xineliboutput --local=sxfe" svdrpsend now gets a reply, and I'm finally able to connect a second vdr-sxfe frontend, which is not the expected behaviour !
Damien
-
Damien Bally -
Joerg Riechardt -
Mika Laitio -
Theunis Potgieter -
VDR User -
Wolfgang Rohdewald