Video Disk Recorder (VDR) broken?

[Zaerc]

I guess my curiosity got the better of me again and I enabeled "VideoLan Client" and "VDR" under webadmin > Wizard > Media Directors > Software modules

Now after every reload of the router, the system tells me that "there are some devices on this Media Director that failed to start", and I find this in the DCERouter's screen session: "Starting Linux Video Disk Recorder: vdr - aborted (to enable the daemon, edit /etc/default/vdr)".

Being the good sport that I am I opened this file and found the following contents:

Code:

# /etc/default/vdr
#
# See also /usr/share/doc/README.Debian
#

# Change to 1 to enable vdr's init-script
ENABLED=0

# Change this to 1 if you want vdr to be able to shutdown the
# computer
ENABLE_SHUTDOWN=0

# Options that will be passed to vdr's commandline
# for example: OPTIONS="-w 15"
OPTIONS="-w 60"

If only I had a clue what would need changing, supposing that indeed that is the problem (the /usr/share/doc/README.Debian does not exist, not that I would expect it to contain anything useful anyway).

The screen session for VDR, doesn't tell me anything either:

Code:

+ /usr/pluto/bin/Spawn_Wrapper.sh ./VDR -d 58 -r 127.0.0.1 -l /var/log/pluto/58_VDR.log
VDR, v.2.0.0.44.0708032200
Visit www.plutohome.com for source code and license information

Now I have tried disabeling VDR and VLC again, but the system keep trying to start them and keeps telling me that devices failed to start.  So any hints on either fixing this or removing them from the system again would be greatly appreciated.

[Hoochster]

Haven't tried yet myself, but in that default script you would want to change Enable=1 instead of 0.  But dunno why you still have issues unchecking it heh that's no fun!  Mine finally finished downloading last night and I installed it, but haven't had a chance to play yet.  Hopefully today.

[Zaerc]

I don't mean to hassle you, but are you sure about changing that value?  Ah what the heck, I'll try it anyway.

Discoveries are made by not following the manual, and since we don't have a manual there will be a lot to discover...

[Hoochster]

I don't mean to hassle you, but are you sure about changing that value?  Ah what the heck, I'll try it anyway.

Discoveries are made by not following the manual, and since we don't have a manual there will be a lot to discover...

LMAO, as far as sure about enabling that value, YES, that is a standard config file to determine if a script should be ran or not.  If you look in that directory there should be more than just that one.  All your init scripts are supposed to I think heh, check there to find any other options to apply to the script so that users can adjust the 1 file instead of a large init file.  And to be able to enable or disable it on boot.  So that part is proper.  Whether that will get it running I still dunno, I would most likely still need to replace the vdr source with more updated or at least patched for my taste kinda like we did with myth.  But am interested to know what happens for ya!  Heh Guinea Pig!

[Zaerc]

Thanks for your suggestions Hoochster, I changed: "ENABLED=0" to "ENABLED=1" in the /etc/default/vdr file, and now the DCERouter screen session says: "Starting Linux Video Disk Recorder: vdr - seems to be running already.".  But unfortunately I still get the "there are some devices on this Media Director that failed to start" screen.

The startup screen with the progressbar also pauzes on "VideoLan Server" and "VideoLan Client", so I'm guessing they also fail to start (maybe they are the real problem).  There doesn't seem to be a "VideoLan" related screen session, which isn't surprising if it doesn't start  (and makes me realize that VDR was already running before in spite of the logged error).

58_VideoLan_Client.log:

Code:

== ATTEMPT FRESH START ==
1       08/09/07 21:06:20       Spawn_Device.sh 58 (spawning-device)    ESC[1;00
m15580 Dev: 58; Already Running list: 15,16,17,18,27,20,29,21,28,59,24,26,22,ESC
[1;00m
== FRESH START ==
1       08/09/07 21:06:20       Spawn_Device.sh 58 (spawning-device)    ESC[1;00
mdevice: 58 ip: 127.0.0.1 cmd_line: VideoLan_ClientESC[1;00m
3       08/09/07 21:06:20       Spawn_Device.sh 58 (spawning-device)    ESC[1;31
mCan't execute VideoLan_ClientESC[1;00m

59_VDR.log:

Code:

== ATTEMPT FRESH START ==
1       08/09/07 21:06:19       Spawn_Device.sh 59 (spawning-device)    ESC[1;00
m15582 Dev: 59; Already Running list: 15,16,17,18,27,20,29,21,28,ESC[1;00m
== FRESH START ==
1       08/09/07 21:06:19       Spawn_Device.sh 59 (spawning-device)    ESC[1;00
mdevice: 59 ip: 127.0.0.1 cmd_line: VDRESC[1;00m
0       08/09/07 21:06:19       59 (spawning-device)    ESC[1;00mEntering 59ESC[
1;00m
========== NEW LOG SECTION ==========
1       08/09/07 21:06:19       59 (spawning-device)    ESC[1;00mStarting... 1
ESC[1;00m
1       08/09/07 21:06:19       59 (spawning-device)    ESC[1;00mFound ./VDRESC[
1;00m

So I guess the problem now is: "Can't execute VideoLan_Client", gotta love eloquent errors like that. 

Found this in /var/log/pluto/Spawn_Device.log

Code:

15580 Thu Aug  9 21:06:20 CEST 2007 WaitLock 'Spawn_Device' (58)
15580 Thu Aug  9 21:06:20 CEST 2007 WaitLock 'Spawn_Device' (58) success
Thu Aug  9 21:06:20 CEST 2007 About to be run: 58
15580 Thu Aug  9 21:06:20 CEST 2007 Unlock 'Spawn_Device' (58)
15580 Thu Aug  9 21:06:20 CEST 2007 Unlock 'Spawn_Device' (58) success

The VLC player itself has no trouble starting on the KDE desktop. 

Just in case anyone is wondering, I haven't done any strange modifications like changing the way the system boots or updated any software on my own (yet).  This is on a vanilla LMCE-1.1-0704.  In the end I could just simply reinstall (haven't set everyting up yet anyway), but I would much rather get to the bottom of this. 

[Hoochster]

Heh, I will try and assist as soon as I can.  Some of us work for a living LMAO j/k!  But hopefully tonight I can try and play with a few things here and there.  So you aren't alone heh.

[totallymaxed]

I guess my curiosity got the better of me again and I enabeled "VideoLan Client" and "VDR" under webadmin > Wizard > Media Directors > Software modules

Now after every reload of the router, the system tells me that "there are some devices on this Media Director that failed to start", and I find this in the DCERouter's screen session: "Starting Linux Video Disk Recorder: vdr - aborted (to enable the daemon, edit /etc/default/vdr)".

Being the good sport that I am I opened this file and found the following contents:

Code:

# /etc/default/vdr
#
# See also /usr/share/doc/README.Debian
#

# Change to 1 to enable vdr's init-script
ENABLED=0

# Change this to 1 if you want vdr to be able to shutdown the
# computer
ENABLE_SHUTDOWN=0

# Options that will be passed to vdr's commandline
# for example: OPTIONS="-w 15"
OPTIONS="-w 60"

If only I had a clue what would need changing, supposing that indeed that is the problem (the /usr/share/doc/README.Debian does not exist, not that I would expect it to contain anything useful anyway).

The screen session for VDR, doesn't tell me anything either:

Code:

+ /usr/pluto/bin/Spawn_Wrapper.sh ./VDR -d 58 -r 127.0.0.1 -l /var/log/pluto/58_VDR.log
VDR, v.2.0.0.44.0708032200
Visit www.plutohome.com for source code and license information

Now I have tried disabeling VDR and VLC again, but the system keep trying to start them and keeps telling me that devices failed to start.  So any hints on either fixing this or removing them from the system again would be greatly appreciated.

Both vdr and vlc are not currently integrated properly. Vdr will be integrated properly in a future release of lmce so that it can be used as an alternative to mythtv and it will have tight integration with lmce. Be patient... ;-)

[Zaerc]

Both vdr and vlc are not currently integrated properly. Vdr will be integrated properly in a future release of lmce so that it can be used as an alternative to mythtv and it will have tight integration with lmce. Be patient... ;-)

Being patient is very nice and all, but that won't fix my broken system.  At the moment I can't go forward to fix this (no indication of what the actual problem is) nor backwards since switching the options off again doesn't seem to actually do anything.  If these things can't be fixed at the moment then at the very least I would like the system NOT to try to start them (and fail) on every reload.

[Hoochster]

I don't know this for a fact since I haven't done it to mine yet.  But as far as stuff that starts on bootup, should mostly be in the runlevel it starts in, which I believe is runlevel 2.  Just type runlevel to find out what it currently runs in.  N 2 means runlevel 2.  Then check in /etc/rc2.d  for runlevel 2 again heh, and look for a symlink for something for either VDR or VideoLan that is causing you the fits.  You should be able to move that symlink to your home directory for now till you are sure you can delete it which I am sure is fine, but always move to be safe for now heh.  Hopefully you will find what you are looking for in there.  Another spot would be to check that /etc/default directory for any config files for what is the problem and disable them like you enabled the vdr one.

Hope that helps Zaerc, let me know.  I will enable mine when I get home to see what it breaks so maybe I can better help.

[Zaerc]

Thanks, but please don't try this at home! (I have always wanted to say that )  I really appreciate the offer, but I think it's bad enough already that I'm going to have to reinstall at the end of this ride, let's try and save everyone else the trouble one way or the other.

I really really hate the idea of the web admin having booby-traps like this one, definately not cool. 

Now let's see about those symlinks.  Hadn't thought of those, because I reckoned it would be started by the DCERouter itself as they show up in a sort of startup/spash screen with a progressbar that lists the devices getting started (I rarely ever even noticed that screen when things went swimmingly).  Funny thing is, I updated a wiki page about manipulating those symlinks for other runlevels not long ago.

Anyway, here is what I got (see? no need to break your system, just look over my shoulder):

Code:

# ls -al /etc/rc2.d/
total 20
drwxr-xr-x   2 root root  4096 2007-08-09 20:37 .
drwxr-xr-x 120 root root 12288 2007-08-09 21:05 ..
-rw-r--r--   1 root root   556 2007-04-10 23:46 README
lrwxrwxrwx   1 root root    17 2007-08-08 03:46 S05vbesave -> ../init.d/vbesave
lrwxrwxrwx   1 root root    15 2007-08-08 03:46 S10acpid -> ../init.d/acpid
lrwxrwxrwx   1 root root    25 2007-08-08 03:46 S10powernowd.early -> ../init.d/
powernowd.early
lrwxrwxrwx   1 root root    18 2007-08-08 03:46 S10sysklogd -> ../init.d/sysklog
d
lrwxrwxrwx   1 root root    34 2007-08-08 03:46 S10xserver-xorg-input-wacom -> ../init.d/xserver-xorg-input-wacom
lrwxrwxrwx   1 root root    15 2007-08-08 03:46 S11klogd -> ../init.d/klogd
lrwxrwxrwx   1 root root    14 2007-08-08 03:46 S12dbus -> ../init.d/dbus
lrwxrwxrwx   1 root root    15 2007-08-08 05:11 S15bind9 -> ../init.d/bind9
lrwxrwxrwx   1 root root    23 2007-08-08 05:10 S17mysql-ndb-mgm -> ../init.d/mysql-ndb-mgm
lrwxrwxrwx   1 root root    19 2007-08-08 05:10 S18mysql-ndb -> ../init.d/mysql-ndb
lrwxrwxrwx   1 root root    13 2007-08-08 05:12 S18nis -> ../init.d/nis
lrwxrwxrwx   1 root root    17 2007-08-08 05:11 S18portmap -> ../init.d/portmap
lrwxrwxrwx   1 root root    16 2007-08-08 05:12 S19autofs -> ../init.d/autofs
lrwxrwxrwx   1 root root    16 2007-08-08 03:46 S19cupsys -> ../init.d/cupsys
lrwxrwxrwx   1 root root    15 2007-08-08 03:46 S19hplip -> ../init.d/hplip
lrwxrwxrwx   1 root root    15 2007-08-08 05:10 S19mysql -> ../init.d/mysql
lrwxrwxrwx   1 root root    14 2007-08-08 03:46 S20apmd -> ../init.d/apmd
lrwxrwxrwx   1 root root    16 2007-08-08 03:46 S20apport -> ../init.d/apport
lrwxrwxrwx   1 root root    16 2007-08-08 05:15 S20atftpd -> ../init.d/atftpd
lrwxrwxrwx   1 root root    18 2007-08-08 05:16 S20ddclient -> ../init.d/ddclient
lrwxrwxrwx   1 root root    13 2007-08-09 20:37 S20gpm -> ../init.d/gpm
lrwxrwxrwx   1 root root    22 2007-08-08 03:46 S20hotkey-setup -> ../init.d/hotkey-setup
lrwxrwxrwx   1 root root    22 2007-08-08 03:46 S20kde-guidance -> ../init.d/kde-guidance
lrwxrwxrwx   1 root root    17 2007-08-08 03:46 S20makedev -> ../init.d/makedev
lrwxrwxrwx   1 root root    20 2007-08-08 05:12 S20nbd-client -> ../init.d/nbd-client
lrwxrwxrwx   1 root root    20 2007-08-08 05:12 S20nbd-server -> ../init.d/nbd-server
lrwxrwxrwx   1 root root    27 2007-08-08 05:11 S20nfs-kernel-server -> ../init.d/nfs-kernel-server
lrwxrwxrwx   1 root root    23 2007-08-08 03:46 S20nvidia-kernel -> ../init.d/nvidia-kernel
lrwxrwxrwx   1 root root    23 2007-08-08 05:16 S20openbsd-inetd -> ../init.d/openbsd-inetd
lrwxrwxrwx   1 root root    16 2007-08-08 05:15 S20polipo -> ../init.d/polipo
lrwxrwxrwx   1 root root    19 2007-08-08 03:46 S20powernowd -> ../init.d/powernowd
lrwxrwxrwx   1 root root    15 2007-08-08 03:46 S20rsync -> ../init.d/rsync
lrwxrwxrwx   1 root root    15 2007-08-08 05:11 S20samba -> ../init.d/samba
lrwxrwxrwx   1 root root    13 2007-08-08 05:11 S20ssh -> ../init.d/ssh
lrwxrwxrwx   1 root root    13 2007-08-09 07:58 S20vdr -> ../init.d/vdr
lrwxrwxrwx   1 root root    20 2007-08-08 05:11 S21nfs-common -> ../init.d/nfs-common
lrwxrwxrwx   1 root root    24 2007-08-08 05:17 S23instcheck.sh -> /etc/init.d/instcheck.sh
lrwxrwxrwx   1 root root    13 2007-08-08 05:11 S23ntp -> ../init.d/ntp
lrwxrwxrwx   1 root root    24 2007-08-08 05:14 S24mythtv-backend -> ../init.d/mythtv-backend
lrwxrwxrwx   1 root root    19 2007-08-08 03:46 S25bluetooth -> ../init.d/bluetooth
lrwxrwxrwx   1 root root    15 2007-08-08 05:13 S25mdadm -> ../init.d/mdadm
lrwxrwxrwx   1 root root    22 2007-08-08 05:11 S40dhcp3-server -> ../init.d/dhcp3-server
lrwxrwxrwx   1 root root    14 2007-08-08 05:15 S40frox -> ../init.d/frox
lrwxrwxrwx   1 root root    17 2007-08-08 03:46 S89anacron -> ../init.d/anacron
lrwxrwxrwx   1 root root    13 2007-08-08 03:46 S89atd -> ../init.d/atd
lrwxrwxrwx   1 root root    14 2007-08-08 03:46 S89cron -> ../init.d/cron
lrwxrwxrwx   1 root root    17 2007-08-08 05:10 S91apache2 -> ../init.d/apache2
lrwxrwxrwx   1 root root    20 2007-08-08 05:17 S98LMCEUpdate -> ../init.d/LMCEUpdate
lrwxrwxrwx   1 root root    17 2007-08-08 03:46 S98usplash -> ../init.d/usplash
lrwxrwxrwx   1 root root    25 2007-08-08 05:20 S990start_avwizard -> ../init.d/0start_avwizard
lrwxrwxrwx   1 root root    22 2007-08-08 03:46 S99acpi-support -> ../init.d/acpi-support
lrwxrwxrwx   1 root root    13 2007-08-08 03:46 S99kdm -> ../init.d/kdm
lrwxrwxrwx   1 root root    18 2007-08-08 03:46 S99rc.local -> ../init.d/rc.local
lrwxrwxrwx   1 root root    19 2007-08-08 03:46 S99rmnologin -> ../init.d/rmnologin
lrwxrwxrwx   1 root root    24 2007-08-08 03:46 S99stop-readahead -> ../init.d/stop-readahead

It does have: "S20vdr -> ../init.d/vdr", but I think that is why "ENABLED=0" was set (probably so the DCERouter could start/stop it instead, just guessing here).  I'm unable to spot anything vlc related.  I could try removing the symlink, but that will probably have the same effect as setting "ENABELED=0" in its config file. 

At the moment I reckon having a dive into the database would be my best bet, as it's probably on a list somewhere of things to start at boottime.  I'll prolly drown or hose the whole system, but the only alternative so far is to reinstall anyway.  Excuse the long posts, I'm just trying to give as much info as I can find, and thanks again Hoochster for your support.

[totallymaxed]

Both vdr and vlc are not currently integrated properly. Vdr will be integrated properly in a future release of lmce so that it can be used as an alternative to mythtv and it will have tight integration with lmce. Be patient... ;-)

Being patient is very nice and all, but that won't fix my broken system.  At the moment I can't go forward to fix this (no indication of what the actual problem is) nor backwards since switching the options off again doesn't seem to actually do anything.  If these things can't be fixed at the moment then at the very least I would like the system NOT to try to start them (and fail) on every reload.

I agree that both vlc & vdr should really be removed from Web Admin. The current packages for both are broken and will always fail.

[Zaerc]

I agree that both vlc & vdr should really be removed from Web Admin. The current packages for both are broken and will always fail.

In my opinion the real issue here is not that they are available, but that they aren't properly removed when I deselect them in the web admin.  That way it wouldn't matter whether they'd function properly or not, the easy fix would then be to simply uninstall them again.  That is what I had expected (and you probably too if I read your original remark again).

[fibres]

Hi all

Not really on your points but didnt want to post a new thread.
Is there any imediate plans to integrate VDR as a TV player as it seems a lot better from playing DVB only media which is most used here in the UK and most of europe and I personally would like to try it as with previous work on pluto this seemed a good way to use DVB content in the UK

Regards

[Hoochster]

Zaerc, that symlink got created when you ticked that box for VDR.  So removing it should be ok.  You are correct in thinking that as long as the config file in /etc/default is set to Enabled=0 that it won't continue any further, but to remove it from even attempting you would take out that symlink, and later you can always add it back in by ticking that box heh.  As far as DCERouter starting it or stopping it, that shouldn't be relevant with that config file, if it is set to Disabled, it is Disabled if DCERouter is running the init script.  It still won't run, unless it is ran manually somehow like /usr/bin/vdr   etc..  I am fairly proficient with VDR, and that's how we have always setup the startup scripts for them, but the truth be told, that is just how init systems handle things.  I am still curious just cuz I am born that way lol, to see if I can make VDR run with it heh.  It wouldn't work off the bat on the MD's till you compiled VDR on them as well, and use the Streamdev plugin on both the Core and MD's.  But should work.  But it wouldn't work with MCE's interface though, which is how I had Myth going before as well, skipping the interface.  But hopefully with source we can alleviate that.  Time shall tell.  Good luck, hope ya don't have to re-install, at least not just yet heh, more stuff to break and test first before re-installing again lol.

[nite_man]

I spent some time to configure VDR under Plutohome about year ago. But without luck, unfortunately. What I'd like to suggest is check if vdr works as stand-alone application. The difference between integration MyhTV and VDR in the Plutohome/LinuxMCE is that MythTV is a part of the system. Possible Pluthome/LinuxMCE won't work without it at all. But VDR's integration is very pure and it supposes that VDR is installed and configured before run under Plutohome/LinuxMCE.

Actually, it'd be great to have a choice between MythTV and VDR. Here is a thread on German VDR forum about integration with Plutohome - http://www.vdr-portal.de/board/thread.php?threadid=32551  if somebody is interested in it.