[gelöst] Plugins werden nicht geladen

goldbär · 5. Oktober 2013

Hallo,

ich bin dabei den VDR neu aufzusetzen.

Beim Start werden offenbar keine Plugins geladen. Ich sehe dazu zumindest keine Meldungen im Syslog

Code

Oct  5 17:03:12 miraculix vdr: [5407] VDR version 2.1.1 started
Oct  5 17:03:12 miraculix vdr: [5407] switched to user 'vdr'
Oct  5 17:03:12 miraculix vdr: [5407] codeset is 'UTF-8' - known
Oct  5 17:03:12 miraculix vdr: [5407] found 28 locales in /usr/share/locale
Oct  5 17:03:12 miraculix vdr: [5407] loading /var/lib/vdr/setup.conf
Oct  5 17:03:12 miraculix vdr: [5407] loading /var/lib/vdr/sources.conf
Oct  5 17:03:12 miraculix vdr: [5407] loading /var/lib/vdr/diseqc.conf
Oct  5 17:03:12 miraculix vdr: [5407] loading /var/lib/vdr/scr.conf
Oct  5 17:03:12 miraculix vdr: [5407] loading /var/lib/vdr/channels.conf
Oct  5 17:03:12 miraculix vdr: [5407] loading /var/lib/vdr/commands.conf
Oct  5 17:03:12 miraculix vdr: [5407] loading /var/lib/vdr/reccmds.conf
Oct  5 17:03:12 miraculix vdr: [5407] loading /var/lib/vdr/svdrphosts.conf
Oct  5 17:03:12 miraculix vdr: [5407] loading /var/lib/vdr/remote.conf
Oct  5 17:03:12 miraculix vdr: [5407] loading /var/lib/vdr/keymacros.conf
Oct  5 17:03:12 miraculix vdr: [5465] video directory scanner thread started (pid=5407, tid=5465, prio=high)
Oct  5 17:03:12 miraculix vdr: [5465] video directory scanner thread ended (pid=5407, tid=5465)
Oct  5 17:03:12 miraculix vdr: [5407] registered source parameters for 'A - ATSC'
Oct  5 17:03:12 miraculix vdr: [5407] registered source parameters for 'C - DVB-C'
Oct  5 17:03:12 miraculix vdr: [5407] registered source parameters for 'S - DVB-S'
Oct  5 17:03:12 miraculix vdr: [5407] registered source parameters for 'T - DVB-T'
Oct  5 17:03:12 miraculix vdr: [5407] probing /dev/dvb/adapter0/frontend0
Oct  5 17:03:12 miraculix vdr: [5407] creating cDvbDevice
Oct  5 17:03:12 miraculix vdr: [5407] new device number 1
Oct  5 17:03:12 miraculix vdr: [5466] video directory scanner thread started (pid=5407, tid=5466, prio=high)
Oct  5 17:03:12 miraculix vdr: [5466] video directory scanner thread ended (pid=5407, tid=5466)
Oct  5 17:03:12 miraculix vdr: [5467] epg data reader thread started (pid=5407, tid=5467, prio=high)
Oct  5 17:03:12 miraculix vdr: [5467] reading EPG data from /var/cache/vdr/epg.data
Oct  5 17:03:12 miraculix vdr: [5467] epg data reader thread ended (pid=5407, tid=5467)
Oct  5 17:03:12 miraculix vdr: [5407] DVB API version is 0x0509 (VDR was built with 0x0509)
Oct  5 17:03:12 miraculix vdr: [5407] frontend 0/0 provides DVB-S,DVB-S2,DSS with QPSK ("STV090x Multistandard")
Oct  5 17:03:12 miraculix vdr: [5469] tuner on frontend 0/0 thread started (pid=5407, tid=5469, prio=high)
Oct  5 17:03:12 miraculix vdr: [5469] cTimeMs: using monotonic clock (resolution is 1 ns)
Oct  5 17:03:12 miraculix vdr: [5407] probing /dev/dvb/adapter1/frontend0
Oct  5 17:03:12 miraculix vdr: [5407] creating cDvbDevice
Oct  5 17:03:12 miraculix vdr: [5407] new device number 1
Oct  5 17:03:12 miraculix vdr: [5466] video directory scanner thread started (pid=5407, tid=5466, prio=high)
Oct  5 17:03:12 miraculix vdr: [5466] video directory scanner thread ended (pid=5407, tid=5466)
Oct  5 17:03:12 miraculix vdr: [5467] epg data reader thread started (pid=5407, tid=5467, prio=high)
Oct  5 17:03:12 miraculix vdr: [5467] reading EPG data from /var/cache/vdr/epg.data
Oct  5 17:03:12 miraculix vdr: [5467] epg data reader thread ended (pid=5407, tid=5467)
Oct  5 17:03:12 miraculix vdr: [5407] DVB API version is 0x0509 (VDR was built with 0x0509)
Oct  5 17:03:12 miraculix vdr: [5407] frontend 0/0 provides DVB-S,DVB-S2,DSS with QPSK ("STV090x Multistandard")
Oct  5 17:03:12 miraculix vdr: [5469] tuner on frontend 0/0 thread started (pid=5407, tid=5469, prio=high)
Oct  5 17:03:12 miraculix vdr: [5469] cTimeMs: using monotonic clock (resolution is 1 ns)
Oct  5 17:03:12 miraculix vdr: [5407] probing /dev/dvb/adapter1/frontend0
Oct  5 17:03:12 miraculix vdr: [5407] creating cDvbDevice
Oct  5 17:03:12 miraculix vdr: [5407] new device number 2
Oct  5 17:03:12 miraculix vdr: [5470] section handler thread started (pid=5407, tid=5470, prio=low)
Oct  5 17:03:12 miraculix vdr: [5407] frontend 1/0 provides DVB-S with QPSK ("Samsung S5H1420/PnpNetwork PN1010 DVB-S")
Oct  5 17:03:12 miraculix vdr: [5472] tuner on frontend 1/0 thread started (pid=5407, tid=5472, prio=high)
Oct  5 17:03:12 miraculix vdr: [5407] found 2 DVB devices
Oct  5 17:03:12 miraculix vdr: [5407] setting primary device to 1
Oct  5 17:03:12 miraculix vdr: [5407] device 1 has no MPEG decoder
Oct  5 17:03:12 miraculix vdr: [5407] assuming manual start of VDR
Oct  5 17:03:12 miraculix vdr: [5407] SVDRP listening on port 6419
Oct  5 17:03:12 miraculix vdr: [5407] setting current skin to "lcars"
Oct  5 17:03:12 miraculix vdr: [5407] loading /var/lib/vdr/themes/lcars-default.theme
Oct  5 17:03:12 miraculix vdr: [5407] remote control LIRC - keys known
Oct  5 17:03:12 miraculix vdr: [5474] LIRC remote control thread started (pid=5407, tid=5474, prio=high)
Oct  5 17:03:12 miraculix vdr: [5407] switching to channel 1
Oct  5 17:03:12 miraculix vdr: [5407] setting watchdog timer to 60 seconds
Oct  5 17:03:12 miraculix vdr: [5473] section handler thread started (pid=5407, tid=5473, prio=low)
Oct  5 17:03:12 miraculix vdr: [5407] OSD size changed to 720x480 @ 1
Oct  5 17:03:12 miraculix vdr: [5407] ERROR: no OSD provider available - using dummy OSD!
Oct  5 17:03:13 miraculix vdr: [5407] max. latency time 1 seconds

Alles anzeigen

Code

svdrpsend PLUG
220 miraculix SVDRP VideoDiskRecorder 2.1.1; Sat Oct  5 17:15:15 2013; UTF-8
214-Available plugins:
214 End of plugin list
221 miraculix closing connection

Gestartet wird der VDR so:

Code

ps axu | grep bin/vdr
vdr       5407  0.0  0.3 438224  6424 ?        S<sl 17:03   0:00 /usr/bin/vdr --lirc=/var/run/lirc/lircd -v /var/lib/video.00 -c /var/lib/vdr -L /usr/lib/vdr/plugins -r /usr/lib/vdr/vdr-recordingaction -s /usr/lib/vdr/vdr-shutdown.wrapper -E /var/cache/vdr/epg.data -u vdr -g /tmp --port=6419  -P "softhddevice -D -d :1 -a hw:1,3" -P dbus2vdr -w 60

Woran kann das liegen?

MegaX · 5. Oktober 2013

Lass mal das Leerzeichen hinter -P weg, also so:

Code

...-P"softhddevice -D -d :1 -a hw:1,3" -Pdbus2vdr -w 60

Vielleicht klappts dann ja.

MegaX

M-Reimer · 5. Oktober 2013

Meine erste Vermutung: Der VDR wurde verpatcht. Deshalb taugt auch der Logauszug wenig.

Bitte mal VDR ohne Patches übersetzen. Dann nochmal probieren. Dann Logauszug posten.

Wenn hier nicht mindestens dieser Patch, der den VDR auch bei nichtexistenten Plugins starten lässt, angewendet wäre, dann hätte der VDR schon relativ früh mit aussagekräftiger Fehlermeldung beendet werden müssen.

goldbär · 5. Oktober 2013

Hallo,

MegaX hat das Problem erkannt. Vielen Dank!
Ohne die Leerzeichen werden die Plugins geladen.

Wahrscheinliche Ursache:
Ich habe mir aus dem yavdr Repository testing-vdr
die Datei debian/plugin-loader2.cpp geklaut.

In dieser Datei wird das Leerzeichen zwischen "-P" und Name des Plugin gesetzt:

Code

if (parameters.empty())
     parameters = " -P " + plugin;
  else
     parameters = " -P \"" + plugin + parameters + "\"";
  return parameters;

Werde das morgen nochmal genauer untersuchen.

goldbär · 6. Oktober 2013

Ne, das wars nicht

Der Fehler war ein fehlendes "eval" beim Aufruf.
So geht es jetzt.

Code

eval exec $DAEMON --lirc=$LIRC -v $VIDEO_DIR -c $CFG_DIR -L $PLUGIN_DIR \
    -r $REC_CMD -s $VDRSHUTDOWN -E $EPG_FILE -u $USER -g /tmp --port=$SVDRP_PORT \
    "$PLUGINS" $OPTIONS $REDIRECT &> /var/log/vdr/startup.log

[gelöst] Plugins werden nicht geladen

Jetzt mitmachen!

Teilen