LinuxMCE Forums

General => Installation issues => Topic started by: maverick0815 on February 19, 2016, 11:39:31 pm

Title: VDR not starting
Post by: maverick0815 on February 19, 2016, 11:39:31 pm
I made a fresh install today -actually two, but thats a different story.
I could tune and create a channels.conf. So far so good, however VDR is not starting.
I found this in /var/log/syslog:
Quote
Feb 19 23:31:18 dcerouter vdr: [12105] VDR version 2.2.0 started
Feb 19 23:31:18 dcerouter vdr: [12105] switched to user 'vdr'
Feb 19 23:31:18 dcerouter vdr: [12105] codeset is 'UTF-8' - known
Feb 19 23:31:18 dcerouter vdr: [12105] found 28 locales in /usr/share/locale
Feb 19 23:31:18 dcerouter vdr: [12105] loading plugin: /usr/lib/vdr/plugins/libvdr-remotetimers.so.2.2.0
Feb 19 23:31:18 dcerouter vdr: [12105] loading plugin: /usr/lib/vdr/plugins/libvdr-streamdev-client.so.2.2.0
Feb 19 23:31:18 dcerouter vdr: [12105] loading plugin: /usr/lib/vdr/plugins/libvdr-streamdev-server.so.2.2.0
Feb 19 23:31:18 dcerouter vdr: [12105] loading plugin: /usr/lib/vdr/plugins/libvdr-svdrpservice.so.2.2.0
Feb 19 23:31:18 dcerouter vdr: [12105] loading plugin: /usr/lib/vdr/plugins/libvdr-xineliboutput.so.2.2.0
Feb 19 23:31:18 dcerouter vdr: [12105] [xine..put] Listening on address '127.0.0.1' port 37890
Feb 19 23:31:18 dcerouter vdr: [12105] loading /var/lib/vdr/setup.conf
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: ChannelBlocker = 0
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: ChannelBlockerList =
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: ChannelBlockerMode = 0
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: CutTimePatchEnabled = 0
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: DisableVPS = 0
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: DolbyTransferFix = 1
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: DoubleEpgAction = 0
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: DoubleEpgTimeDelta = 15
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: HardLinkCutter = 0
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: JumpPlay = 0
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: MaxRecordingSize = 100
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: MenuCmdPosition = 0
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: MixEpgAction = 0
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: noEPGList =
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: noEPGMode = 0
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: NoQamOnDecoder = 0
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: PauseLastMark = 0
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: PlayJump = 0
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: PrimaryLimit = 0
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: RecordDolbyDigital = 1
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: ReloadMarks = 0
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: ShowProgressBar = 0
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: ShowRecDate = 1
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: ShowRecLength = 0
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: ShowRecTime = 1
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: TurnOffPrimary = 0
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: UseSyncEarlyPatch = 0
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: streamdev-server.SuspendMode = 1
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: unknown config parameter: xineliboutput.Video.FieldOrder = 0
Feb 19 23:31:18 dcerouter vdr: [12105] loading /var/lib/vdr/sources.conf
Feb 19 23:31:18 dcerouter vdr: [12105] loading /var/lib/vdr/diseqc.conf
Feb 19 23:31:18 dcerouter vdr: [12105] loading /var/lib/vdr/scr.conf
Feb 19 23:31:18 dcerouter vdr: [12105] loading /var/lib/vdr/channels.conf
Feb 19 23:31:18 dcerouter vdr: [12105] loading /var/lib/vdr/timers.conf
Feb 19 23:31:18 dcerouter vdr: [12105] loading /var/lib/vdr/commands.conf
Feb 19 23:31:18 dcerouter vdr: [12105] loading /var/lib/vdr/reccmds.conf
Feb 19 23:31:18 dcerouter vdr: [12105] loading /var/lib/vdr/svdrphosts.conf
Feb 19 23:31:18 dcerouter vdr: [12105] loading /var/lib/vdr/remote.conf
Feb 19 23:31:18 dcerouter vdr: [12105] loading /var/lib/vdr/keymacros.conf
Feb 19 23:31:18 dcerouter vdr: [12106] video directory scanner thread started (pid=12105, tid=12106, prio=high)
Feb 19 23:31:18 dcerouter vdr: [12105] registered source parameters for 'A - ATSC'
Feb 19 23:31:18 dcerouter vdr: [12106] video directory scanner thread ended (pid=12105, tid=12106)
Feb 19 23:31:18 dcerouter vdr: [12105] registered source parameters for 'C - DVB-C'
Feb 19 23:31:18 dcerouter vdr: [12105] registered source parameters for 'S - DVB-S'
Feb 19 23:31:18 dcerouter vdr: [12105] registered source parameters for 'T - DVB-T'
Feb 19 23:31:18 dcerouter vdr: [12105] probing /dev/dvb/adapter0/frontend0
Feb 19 23:31:18 dcerouter vdr: [12105] creating cDvbDevice
Feb 19 23:31:18 dcerouter vdr: [12105] new device number 1
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: can't open DVB device 0/0
Feb 19 23:31:18 dcerouter vdr: [12105] cTimeMs: using monotonic clock (resolution is 1 ns)
Feb 19 23:31:18 dcerouter vdr: [12105] found 1 DVB device
Feb 19 23:31:18 dcerouter vdr: [12105] initializing plugin: remotetimers (1.0.2): Edit timers on remote VDR
Feb 19 23:31:18 dcerouter vdr: [12105] initializing plugin: streamdev-client (0.6.1-git): VTP Streaming Client
Feb 19 23:31:18 dcerouter vdr: [12105] initializing plugin: streamdev-server (0.6.1-git): VDR Streaming Server
Feb 19 23:31:18 dcerouter vdr: [12105] initializing plugin: svdrpservice (1.0.0): SVDRP client
Feb 19 23:31:18 dcerouter vdr: [12105] initializing plugin: xineliboutput (2.0.0-cvs): X11/xine-lib output plugin
Feb 19 23:31:18 dcerouter vdr: [12105] new device number 2
Feb 19 23:31:18 dcerouter vdr: [12105] [xine..put] cTimePts: clock_gettime(CLOCK_MONOTONIC): clock resolution 0 us
Feb 19 23:31:18 dcerouter vdr: [12105] [xine..put] cTimePts: using monotonic clock
Feb 19 23:31:18 dcerouter vdr: [12105] [xine..put] RTP SSRC: 0x5cde7444
Feb 19 23:31:18 dcerouter vdr: [12105] setting primary device to 2
Feb 19 23:31:18 dcerouter vdr: [12105] assuming manual start of VDR
Feb 19 23:31:18 dcerouter vdr: [12105] SVDRP listening on port 6419
Feb 19 23:31:18 dcerouter vdr: [12105] setting current skin to "sttng"
Feb 19 23:31:18 dcerouter vdr: [12105] loading /var/lib/vdr/themes/sttng-default.theme
Feb 19 23:31:18 dcerouter vdr: [12107] video directory scanner thread started (pid=12105, tid=12107, prio=high)
Feb 19 23:31:18 dcerouter vdr: [12107] video directory scanner thread ended (pid=12105, tid=12107)
Feb 19 23:31:18 dcerouter vdr: [12105] starting plugin: remotetimers
Feb 19 23:31:18 dcerouter vdr: [12105] starting plugin: streamdev-client
Feb 19 23:31:18 dcerouter vdr: [12105] starting plugin: streamdev-server
Feb 19 23:31:18 dcerouter vdr: [12105] loading /var/lib/vdr/plugins/streamdev-server/streamdevhosts.conf
Feb 19 23:31:18 dcerouter vdr: [12109] device 1 section handler thread started (pid=12105, tid=12109, prio=low)
Feb 19 23:31:18 dcerouter vdr: [12108] epg data reader thread started (pid=12105, tid=12108, prio=high)
Feb 19 23:31:18 dcerouter vdr: [12108] reading EPG data from /var/cache/vdr/epg.data
Feb 19 23:31:18 dcerouter vdr: [12105] starting plugin: svdrpservice
Feb 19 23:31:18 dcerouter vdr: [12105] starting plugin: xineliboutput
Feb 19 23:31:18 dcerouter vdr: [12110] [xine..put] Have CAP_SYS_NICE capability
Feb 19 23:31:18 dcerouter vdr: [12112] streamdev server thread started (pid=12105, tid=12112, prio=high)
Feb 19 23:31:18 dcerouter vdr: [12111] remotetimers update file watcher thread started (pid=12105, tid=12111, prio=high)
Feb 19 23:31:18 dcerouter vdr: [12108] epg data reader thread ended (pid=12105, tid=12108)
Feb 19 23:31:18 dcerouter vdr: [12111] remotetimers update file watcher now monitoring '/srv/vdr/video/.update'
Feb 19 23:31:18 dcerouter vdr: [12113] Remote decoder/display server (cXinelibServer) thread started (pid=12105, tid=12113, prio=high)
Feb 19 23:31:18 dcerouter vdr: [12113] [xine..put] Have CAP_SYS_NICE capability
Feb 19 23:31:18 dcerouter vdr: [12113] [xine..put] cXinelibServer priority set successful SCHED_RR 2 [1,99]
Feb 19 23:31:18 dcerouter vdr: [12113] [xine..put] Binding server to 127.0.0.1:37890
Feb 19 23:31:18 dcerouter vdr: [12112] Streamdev: Couldn't listen (VTP) 0.0.0.0:2004: Address already in use
Feb 19 23:31:18 dcerouter vdr: [12113] [xine..put] cXinelibServer: bind error 127.0.0.1 port 37890: Address already in use
Feb 19 23:31:18 dcerouter vdr: [12113] [xine..put]    (ERROR (frontend_svr.c,861): Address already in use)
Feb 19 23:31:18 dcerouter vdr: [12112] Streamdev: Couldn't listen (HTTP) 0.0.0.0:3000: Address already in use
Feb 19 23:31:18 dcerouter vdr: [12112] ERROR: no streamdev server activated, exiting
Feb 19 23:31:18 dcerouter vdr: [12112] streamdev server thread ended (pid=12105, tid=12112)
Feb 19 23:31:18 dcerouter vdr: [12113] [xine..put] Listening for UDP broadcasts on port 37890
Feb 19 23:31:18 dcerouter vdr: [12113] Remote decoder/display server (cXinelibServer) thread ended (pid=12105, tid=12113)
Feb 19 23:31:18 dcerouter vdr: [4336] [discovery] BROADCAST: VDR xineliboutput DISCOVERY 1.0#015#012Server port: 37890#015#012Server address: 127.0.0.1#015#012Server version: xineliboutput-2.0.0-cvs#015#012#015
Feb 19 23:31:18 dcerouter vdr: [12105] [xine..put] cXinelibDevice::Start(): Server init failed
Feb 19 23:31:18 dcerouter vdr: [12105] stopping plugin: svdrpservice
Feb 19 23:31:18 dcerouter vdr: [12105] stopping plugin: streamdev-server
Feb 19 23:31:18 dcerouter vdr: [12105] stopping plugin: streamdev-client
Feb 19 23:31:18 dcerouter vdr: [12105] stopping plugin: remotetimers
Feb 19 23:31:18 dcerouter vdr: [12111] remotetimers update file watcher thread ended (pid=12105, tid=12111)
Feb 19 23:31:18 dcerouter vdr: [12105] [xine..put] cXinelibOsdProvider: shutting down !
Feb 19 23:31:19 dcerouter vdr: [12109] device 1 section handler thread ended (pid=12105, tid=12109)
Feb 19 23:31:19 dcerouter vdr: [12105] [xine..put] cXinelibDevice::StopDevice(): Stopping device ...
Feb 19 23:31:19 dcerouter vdr: [12105] deleting plugin: xineliboutput
Feb 19 23:31:19 dcerouter vdr: [12105] deleting plugin: svdrpservice
Feb 19 23:31:19 dcerouter vdr: [12105] deleting plugin: streamdev-server
Feb 19 23:31:19 dcerouter vdr: [12105] deleting plugin: streamdev-client
Feb 19 23:31:19 dcerouter vdr: [12105] deleting plugin: remotetimers
Feb 19 23:31:19 dcerouter vdr: [12105] exiting, exit code 2
Feb 19 23:31:19 dcerouter runvdr: stopping after fatal fail ()


in additon to this, I also found out that /etc/vdr/plugins/xineliboutput/config is a broken link the config in /var/lib/vdr/plugins/xineliboutput is missing
Title: Re: VDR not starting
Post by: posde on February 20, 2016, 12:16:22 am
Quote
Feb 19 23:31:18 dcerouter vdr: [12105] new device number 1
Feb 19 23:31:18 dcerouter vdr: [12105] ERROR: can't open DVB device 0/0

looks wrong.

And it looks as if you have two vdr instances running. Remove the vdr.conf in /etc/init/ (the upstart control file), reboot the system, and things should look better.
Title: Re: VDR not starting
Post by: maverick0815 on February 20, 2016, 12:57:03 pm
while that does look better, I still have no playback.
/var/log/pluto/32_vdr.log shows this, when I try watching TV:
Quote
========== NEW LOG SECTION ==========
1   02/20/16 12:27:59   32 (spawning-device)   Starting... 1
1   02/20/16 12:28:00   32 (spawning-device)   Found ./VDR
05   02/20/16 12:30:27.302      Connect() failed, Error Code 111 (Connection refused)) <0xb5bffb40>
05   02/20/16 12:30:28.303      Connect() failed, Error Code 111 (Connection refused)) <0xb5bffb40>
05   02/20/16 12:30:29.304      Connect() failed, Error Code 111 (Connection refused)) <0xb5bffb40>
05   02/20/16 12:30:29.304      ClientSocket::Connect() not successful <0xb5bffb40>
05   02/20/16 12:30:29.305      void ClientSocket::Disconnect() on this socket: 0xb5bfec8c (m_Socket: 8) <0xb5bffb40>
05   02/20/16 12:30:40.197      Connect() failed, Error Code 111 (Connection refused)) <0xb5bffb40>
05   02/20/16 12:30:41.197      Connect() failed, Error Code 111 (Connection refused)) <0xb5bffb40>
05   02/20/16 12:30:42.198      Connect() failed, Error Code 111 (Connection refused)) <0xb5bffb40>
05   02/20/16 12:30:42.198      ClientSocket::Connect() not successful <0xb5bffb40>
05   02/20/16 12:30:42.198      void ClientSocket::Disconnect() on this socket: 0xb5bfec8c (m_Socket: 8) <0xb5bffb40>
== ATTEMPT FRESH START ==
1   02/20/16 12:34:44   Spawn_Device.sh 32 (spawning-device)   26011 Dev: 32; Already Running list: 15,16,17,18,20,25,21,24,
== FRESH START ==
1   02/20/16 12:34:44   Spawn_Device.sh 32 (spawning-device)   device: 32 ip: 127.0.0.1 cmd_line: VDR
0   02/20/16 12:34:44   32 (spawning-device)   Entering 32
========== NEW LOG SECTION ==========
1   02/20/16 12:34:45   32 (spawning-device)   Starting... 1
1   02/20/16 12:34:45   32 (spawning-device)   Found ./VDR
05   02/20/16 12:37:18.243      Connect() failed, Error Code 111 (Connection refused)) <0xb5bffb40>
05   02/20/16 12:37:19.244      Connect() failed, Error Code 111 (Connection refused)) <0xb5bffb40>
05   02/20/16 12:37:20.244      Connect() failed, Error Code 111 (Connection refused)) <0xb5bffb40>
05   02/20/16 12:37:20.245      ClientSocket::Connect() not successful <0xb5bffb40>
05   02/20/16 12:37:20.245      void ClientSocket::Disconnect() on this socket: 0xb5bfec8c (m_Socket: 8) <0xb5bffb40>
05   02/20/16 12:50:49.036      Connect() failed, Error Code 111 (Connection refused)) <0xb5bffb40>
05   02/20/16 12:50:50.038      Connect() failed, Error Code 111 (Connection refused)) <0xb5bffb40>
05   02/20/16 12:50:51.038      Connect() failed, Error Code 111 (Connection refused)) <0xb5bffb40>
05   02/20/16 12:50:51.038      ClientSocket::Connect() not successful <0xb5bffb40>
05   02/20/16 12:50:51.038      void ClientSocket::Disconnect() on this socket: 0xb5bfec8c (m_Socket: 8) <0xb5bffb40>

I'm sorry for those stupid smileys popping up there its actually an"8" and ")" but it seems I cannot mask it properly in the quote
Title: Re: VDR not starting
Post by: posde on February 20, 2016, 02:16:53 pm
Make sure that vdr listens on port 2001, ie. did you change VDR Admin connect to 2001 and does it successfully connect? Also, check that port 3000 works by connecting to it from say vlc http://dcerouter:3000/TS/1 should show you the first channel of live TV in VLC
Title: Re: VDR not starting
Post by: maverick0815 on February 20, 2016, 04:03:01 pm
I tried vlc and it cannot open the stream.
To access VDRadmin I needed to change svdrphosts.conf to allow for 192.168.80.0/24 to connect.
I checked in VDRadmin and found that livestreaming was set off...I set it on.
I verified that port 2001 is being used.
I will try to disable the core firewall to see, if something is blocking there.
VDRadmin also has a link to watch tv, but even there nothing happens.

I also found this in syslog when I tried to connect:
Quote
eb 20 16:05:15 dcerouter vdr: [16375] Streamdev: Accepted new client (HTTP) 192.168.80.132:64285
Feb 20 16:05:15 dcerouter vdr: [16375] streamdev: client 192.168.80.132:64285 not allowed to connect
Feb 20 16:05:15 dcerouter vdr: [16375] streamdev-server: closing HTTP connection to 192.168.80.132:64285
Feb 20 16:05:15 dcerouter vdr: [16375] Streamdev: Accepted new client (HTTP) 192.168.80.132:64286
Feb 20 16:05:15 dcerouter vdr: [16375] streamdev: client 192.168.80.132:64286 not allowed to connect
Feb 20 16:05:15 dcerouter vdr: [16375] streamdev-server: closing HTTP connection to 192.168.80.132:64286
Feb 20 16:05:15 dcerouter vdr: [16375] Streamdev: Accepted new client (HTTP) 192.168.80.132:64287
Feb 20 16:05:15 dcerouter vdr: [16375] streamdev: client 192.168.80.132:64287 not allowed to connect
Feb 20 16:05:15 dcerouter vdr: [16375] streamdev-server: closing HTTP connection to 192.168.80.132:64287
Feb 20 16:05:15 dcerouter vdr: [16375] Streamdev: Accepted new client (HTTP) 192.168.80.132:64288
Feb 20 16:05:15 dcerouter vdr: [16375] streamdev: client 192.168.80.132:64288 not allowed to connect
Feb 20 16:05:15 dcerouter vdr: [16375] streamdev-server: closing HTTP connection to 192.168.80.132:64288
Feb 20 16:05:15 dcerouter vdr: [16375] Streamdev: Accepted new client (HTTP) 192.168.80.132:64289
Feb 20 16:05:15 dcerouter vdr: [16375] streamdev: client 192.168.80.132:64289 not allowed to connect
Feb 20 16:05:15 dcerouter vdr: [16375] streamdev-server: closing HTTP connection to 192.168.80.132:64289
Feb 20 16:05:15 dcerouter vdr: [16375] Streamdev: Accepted new client (HTTP) 192.168.80.132:64290
Feb 20 16:05:15 dcerouter vdr: [16375] streamdev: client 192.168.80.132:64290 not allowed to connect
Feb 20 16:05:15 dcerouter vdr: [16375] streamdev-server: closing HTTP connection to 192.168.80.132:64290
Feb 20 16:05:15 dcerouter vdr: [16375] Streamdev: Accepted new client (HTTP) 192.168.80.132:64291
Feb 20 16:05:15 dcerouter vdr: [16375] streamdev: client 192.168.80.132:64291 not allowed to connect
Feb 20 16:05:15 dcerouter vdr: [16375] streamdev-server: closing HTTP connection to 192.168.80.132:64291
Feb 20 16:05:15 dcerouter vdr: [16375] Streamdev: Accepted new client (HTTP) 192.168.80.132:64292
Feb 20 16:05:15 dcerouter vdr: [16375] streamdev: client 192.168.80.132:64292 not allowed to connect
Feb 20 16:05:15 dcerouter vdr: [16375] streamdev-server: closing HTTP connection to 192.168.80.132:64292
Feb 20 16:05:15 dcerouter vdr: [16375] Streamdev: Accepted new client (HTTP) 192.168.80.132:64293
Feb 20 16:05:15 dcerouter vdr: [16375] streamdev: client 192.168.80.132:64293 not allowed to connect
Feb 20 16:05:15 dcerouter vdr: [16375] streamdev-server: closing HTTP connection to 192.168.80.132:64293
Feb 20 16:05:15 dcerouter vdr: [16375] Streamdev: Accepted new client (HTTP) 192.168.80.132:64294
Feb 20 16:05:15 dcerouter vdr: [16375] streamdev: client 192.168.80.132:64294 not allowed to connect
Feb 20 16:05:15 dcerouter vdr: [16375] streamdev-server: closing HTTP connection to 192.168.80.132:64294
Feb 20 16:05:15 dcerouter vdr: [16375] Streamdev: Accepted new client (HTTP) 192.168.80.132:64295
Feb 20 16:05:15 dcerouter vdr: [16375] streamdev: client 192.168.80.132:64295 not allowed to connect
Feb 20 16:05:15 dcerouter vdr: [16375] streamdev-server: closing HTTP connection to 192.168.80.132:64295
Title: Re: VDR not starting
Post by: maverick0815 on February 20, 2016, 04:33:28 pm
ok after editing streamdevhosts.conf in the same way as svdrphosts.conf by allowing 192.168.80.0/24 access, I can now use vlc to stream. TV however not yet.
I saw that there is another config file  for xlineliboutput, that perhaps needs the same setting...at least it looks the same. I will try and report my findings.
Title: Re: VDR not starting
Post by: maverick0815 on February 20, 2016, 05:07:36 pm
the allowed_hosts.conf for xineliboutput didn't do the trick. I can stream to vlc or gomplayer...no problem. TV (connected to the core/hybrid) no way
Title: Re: VDR not starting
Post by: pointman87 on February 20, 2016, 05:31:04 pm
You can try to run /usr/pluto/bin/StartVDRClient.sh from ssh on your MD after you have issued TV on the orbiter and see if TV starts. Have you rebooted? Is pluto-vdr installed on the MD? pluto-vdr-plugin on the core?

BR Daniel
Title: Re: VDR not starting
Post by: posde on February 20, 2016, 05:46:24 pm
If you can access the stream from VLC you have crossed most of the hurdles. VDR is running, it tunes to channels, and streamdev-server is working as well.

Please show me the contents of /etc/vdradmin-am/vdradmind.conf
Title: Re: VDR not starting
Post by: posde on February 20, 2016, 05:47:21 pm
Oh, and before I forget: When you come into IRC, stick around, and don't exit out after a few minutes. When you ask in IRC, don't ask if someone can help you, but your real question.
Title: Re: VDR not starting
Post by: maverick0815 on February 20, 2016, 06:06:40 pm
Quote
=
AT_DESC = 0
AT_FUNC = 0
AT_LIFETIME = 99
AT_MARGIN_BEGIN = 10
AT_MARGIN_END = 10
AT_OFFER = 1
AT_PRIORITY = 99
AT_SENDMAIL = 0
AT_SORTBY = pattern
AT_TOOLTIP = 1
AUTO_SAVE_CONFIG = 1
CACHE_BG_UPDATE = 1
CACHE_LASTUPDATE = 1455983588
CACHE_REC_ENABLED = 1
CACHE_REC_LASTUPDATE = 0
CACHE_REC_TIMEOUT = 60
CACHE_TIMEOUT = 5
CHANNELS_WANTED =
CHANNELS_WANTED_AUTOTIMER = 0
CHANNELS_WANTED_PRG = 0
CHANNELS_WANTED_PRG2 = 0
CHANNELS_WANTED_SUMMARY = 0
CHANNELS_WANTED_TIMELINE = 0
CHANNELS_WANTED_WATCHTV = 0
CHANNELS_WITHOUT_EPG = 1
CMD_LINES = 20
EPGIMAGES = /var/cache/vdr/epgimages
EPG_PRUNE = 0
EPG_START_TIME = 00:00
EPG_SUBTITLE = 1
EPG_SUMMARY = 0
ES_DESC = 0
ES_SORTBY = pattern
GUEST_ACCOUNT = 0
GUI_POPUP_HEIGHT = 250
GUI_POPUP_WIDTH = 500
LANG =
LANGUAGE = English
LOCAL_NET = 0.0.0.0/32
LOGFILE = vdradmind.log
LOGGING = 0
LOGINPAGE = 0
LOGLEVEL = 4
MAIL_AUTH_PASS =
MAIL_AUTH_USER =
MAIL_FROM = autotimer@dcerouter
MAIL_SERVER = localhost
MAIL_TO = you@example.org
MOD_GZIP = 1
NO_EVENTID = 0
NO_EVENTID_ON =
PASSWORD = linvdr
PASSWORD_GUEST = guest
PROG_SUMMARY_COLS = 3
PS_VIEW = sml
RECORDINGS = 1
REC_DESC = 0
REC_EXT = m3u
REC_MIMETYPE = video/x-mpegurl
REC_SORTBY = name
SERVERHOST = 0.0.0.0
SERVERPORT = 8001
SKIN = default
SRCH1_ACTIVE = 1
SRCH1_TITLE = Lookup movie in the Internet-Movie-Database (IMDb)
SRCH1_URL = http://akas.imdb.com/Tsearch?title=%TITLE%
SRCH2_ACTIVE = 0
SRCH2_TITLE =
SRCH2_URL =
ST_FUNC = 1
ST_LIVE_ON = 1
ST_REC_ON = 0
ST_STREAMDEV_HOST =
ST_STREAMDEV_PORT = 3000
ST_URL =
ST_VIDEODIR =
ST_XINELIB_PORT = 37890
TEMPLATE = default
TIMES = 18:00, 20:00, 21:00, 22:00
TL_TOOLTIP = 1
TM_DESC = 0
TM_LIFETIME = 99
TM_MARGIN_BEGIN = 10
TM_MARGIN_END = 10
TM_PRIORITY = 99
TM_SORTBY = day
TM_TT_LIST = 1
TM_TT_TIMELINE = 1
TV_EXT = m3u
TV_INTERVAL = 5
TV_MIMETYPE = video/x-mpegurl
TV_SIZE = half
USERNAME = linvdr
USERNAME_GUEST = guest
VDRCONFDIR = /var/lib/vdr
VDR_HOST = localhost
VDR_PORT = 6419
VIDEODIR = /var/lib/video
ZEITRAHMEN = 1
there you go

Sorry for not sticking around. I was trying several things at once and rebooted several times..so I probably forgot to log back in, after internet was back up.
I will pop back in iirc around 7pm,in case you are there. Perhaps we could track this down together.
Title: Re: VDR not starting
Post by: posde on February 20, 2016, 06:27:41 pm
Your VDR is still not listening to 2001 - Change vdr listen port to 2001.

You can verify it, by using
Code: [Select]
svdrpsend -p 2001 help
if that returns some help, you've got vdr setup correct, and LinuxMCE will be able to talk to it.

Remember to change vdradmin as well.
Title: Re: VDR not starting
Post by: maverick0815 on February 21, 2016, 02:33:25 pm
With the help of posde I was able to get VDR running now, but I've come across another issue with VDR, probably.
It's already the second time, that I found my core shutdown in the morning. I checked in syslog and found that at 1:28:26  I had an entry of
Quote
vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.custom as shell script
rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="703" x-info="http://www.rsyslog.com"} exiting on signal 15
Title: Re: VDR not starting
Post by: phenigma on February 21, 2016, 04:08:40 pm
iirc you turned on the auto-shutdown in the vdr config the other day.  I believe posde mentioned this in irc.

J.
Title: Re: VDR not starting
Post by: maverick0815 on February 21, 2016, 05:01:07 pm
Nah, I didn't...I believe its still with the standard configuration....I checked on the net.
in /etc/vdr/setup.conf there is an entry MinUserInactivity that should be set to 0 if no automatic shutdown should occur.
I set that now, lets see.
Title: Re: VDR not starting
Post by: phenigma on February 21, 2016, 05:19:32 pm
Code: [Select]
<Maverick0815> @posde vrd is running, needed to edit /etc/default/vdr and set enabled to 1 and enableshutdown to 1

You said you did.  ;)

J.
Title: Re: VDR not starting
Post by: maverick0815 on February 21, 2016, 05:50:32 pm
You got it 50% right....posde also told me its strongly advised, not to set it....so I set it back to 0
Title: Re: VDR not starting
Post by: phenigma on February 21, 2016, 05:55:05 pm
That's not a piece of information that you shared, since you made no indication that you had changed it back I, of course, assume it is set as you said it was.  ;)  Specific information is *very* important in troubleshooting.

J.
Title: Re: VDR not starting
Post by: posde on February 21, 2016, 06:48:27 pm
check etc/vdr/conf.d/00-vdr.conf if that contains something re shutdown enabling.
Title: Re: VDR not starting
Post by: S4Howie on February 27, 2016, 09:07:30 pm
For your information,MythTV is running like a charm for me.I cant understand how the dev´s not use it.I run 2x Nexus S DVB-S Cards and installed 3x IPTV Freebox Virtual Cards with a m3u file linked to the Channels of my provider,HD channels over IPTV. I check the Mythtv Plugin to not beeing Auto Configurated by LinuxMCE on the Web admin page. Then i run mythsetup on my core and install all Cards and do a channel search. After that you can add MD to your Core and boot them up.The first time you start mythsetup on a MD it will ask you for Language Settings and the Database and Password settings,here you need to fill in the same information like on your Core found on Gerneral Settings in Setup.In my case Coreip 192.168.80.1(better change this in Core also, not use dcerouter/localhost)and the password provided.Then mythsetup on MD will connect to the Master Backend and save the settings.If you dont want to add extra Cards on the MD leave the setup and your done. All Cards are shared,all Records are shared all in sync.Works like a charm.I can connect from Windows PC with Mythtv player,i can connect from Kodi useing MythFronted Plugin,running Kodi on windows and on android(Amazon Fire TV Stick),i can connect from Android Phone useing MythFrontendBeta and watch all recordings away from home too.I see all recodings shared from myth upnp,and watch recodings over html from browser also works,with a small delay of the file beeing transcoded.I have up running 3x MD´s.I see all my Harddrives in MythTv Status Page and all the record folder links are correct.

Please never let MythTV die in LinuxMCE,its the most used thing in my Setup.

Howie
Title: Re: VDR not starting
Post by: posde on February 27, 2016, 10:42:07 pm
It will not die. It is just not receiving a lot of love these days.

Feel free to jump in, and take the lead in getting MythTV going even better for the LinuxMCE user base.
Title: Re: VDR not starting
Post by: maverick0815 on February 28, 2016, 06:25:35 pm
@posde:
this is the current content of etc/vdr/conf.d/00-vdr.conf

Quote
#
# This file contains the arguments for VDR if invoked without arguments on the
# command line.
#
# See `man vdr`.
#

[vdr]
--record=/usr/lib/vdr/vdr-recordingaction
--user=vdr
--grab=/tmp
--port=2001
--watchdog=0
--shutdown=/usr/lib/vdr/vdr-shutdown.wrapper
--dirnames=,,1

all in all it is running much better than mythtv, however it seems not be quite stable either. it has taken to restarting sometime while watching TV, or just hanging. Two or three times I had to reboot the server, because it totally crashed.
Title: Re: VDR not starting
Post by: posde on February 28, 2016, 07:48:20 pm
Take out the shutdown line. If you use the original Upstart start configuration, it would otherwise shutdown your system.

I had issues with HD channels during bad reception. In the end I moved away from the xineliboutput to the softhddevice. But that hasn't been updated into git yet, as I am still in the process of making it work more stable.

One thing that I have noticed is: If the TV appears to hang, try switching channels. I very rarely had issue with recording playback. And, most importantly, Rule #1 applies :)

Another thing that has helped me recover a crash is: Don't power-off (the TV process from the OrbiteR), but select TV again.
Title: Re: VDR not starting
Post by: maverick0815 on March 05, 2016, 11:46:32 am
I am happy to report, that after taking out the shutdown-line, everything appears to be running nicely :-)
Title: Re: VDR not starting
Post by: posde on March 05, 2016, 12:19:49 pm
Thanks for the feedback. I guess it is time for me to amend the pluto-vdr postinst to the latest way of doing things.

Oh, and a side note: I've completed my first recording into pluto_media script successfully, meaning, as soon as a recording has finished, it will appear in the regular list of Videos, and not only as recordings inside of VDR.