easyVDR Kopie des easyVDR-Forums zum Nachschlagen
DVBSky S952 V3, streamdev: No device provides channel

easyVDR - >VARforumsname - >DVBSky S952 V3, streamdev: No device provides channel

KaiCrow  17.Feb.2016 21:47:23
Hallo,

ich habe eine DVBSky S952 V3 (Twin DVB-S2-Tuner) und ein aktuelles easyVDR als Headless laufen. Nach dem Booten des VDR scheitert Streamdev beim Versuch auf ein Programm umzuschalten:

streamdev: No device provides channel 2 (ZDF) at priority 0

Stoppe ich dann den VDR und starte ihn erneut (ohne Reboot), tritt dieser Effekt nicht mehr auf. Wo könnte das Problem liegen?

Log-Auszug vom Bootvorgang im Anhang.
log.txt
SurfaceCleanerZ  18.Feb.2016 07:21:57
Hi,
möglicherweise wird der VDR zu früh gestartet.

Teste mal das dynamite-Plugin.

MfG,
Stefan
Test-VDR1: HP rp5700 Fertigsystem, Core2Duo E6400, 2GB RAM, Mygica t230 Stick als Tuner, nvidia Slim-GT218 512MB PCIe x1     -   v3.5-64
VDR2 in Rente
VDR3 in Rente
VDR4: MSI G31M2 v2, Intel E5200, 6" t6963c gLCD, 2GB, WD Red 4TB, 2x TT3200, ASUS GT730-SL-2GD3-BRK, mod. Digitainergeh.       -   v3.5-64
VDR5: GIGABYTE GA-G31M-S2L, Intel E5200, GT630 passiv, 2GB, 3TB, 6"  t6963c gLCD, mod. Digitainergeh.          -   v3.5-64
VDR6: MSI MS-7236, Intel E2140, GT630 passiv, 2GB, WD Green 2TB, 6" t6963c gLCD, 2x TT3200    -    v2.5-64
[url=http://tinyurl.com/ycx4qsv]Hilfe gefällig? Dann brauchen wir ein easyInfo aus easyPortal!
KaiCrow  18.Feb.2016 20:44:36
Danke für den Hinweis. Habe das Plugin aktiviert, es wird scheinbar auch geladen, der Effekt bleibt aber leider der gleiche.

Feb 18 20:28:01 easyvdr vdr: initializing plugin: dynamite (0.2.1): Empfangsgeräte während des Betriebs ein- und aushängen
Feb 18 20:28:01 easyvdr vdr: dynamite: creating dynamic device slots as much as possible
Feb 18 20:28:01 easyvdr vdr: new device number 2
Feb 18 20:28:01 easyvdr vdr: new device number 3
Feb 18 20:28:01 easyvdr vdr: new device number 4
Feb 18 20:28:01 easyvdr vdr: new device number 5
Feb 18 20:28:01 easyvdr vdr: new device number 6
Feb 18 20:28:01 easyvdr vdr: new device number 7
Feb 18 20:28:01 easyvdr vdr: video directory scanner thread ended (pid=2949, tid=3006)
Feb 18 20:28:01 easyvdr vdr: new device number 8
Feb 18 20:28:01 easyvdr vdr: new device number 9
Feb 18 20:28:01 easyvdr vdr: new device number 10
Feb 18 20:28:01 easyvdr vdr: new device number 11
Feb 18 20:28:01 easyvdr vdr: new device number 12
Feb 18 20:28:01 easyvdr vdr: new device number 13
Feb 18 20:28:01 easyvdr vdr: new device number 14
Feb 18 20:28:01 easyvdr vdr: new device number 15
Feb 18 20:28:01 easyvdr vdr: new device number 16
Feb 18 20:28:01 easyvdr vdr: dynamite: probing /dev/dvb/adapter0/frontend0
Feb 18 20:28:01 easyvdr vdr: dynamite: probing /dev/dvb/adapter1/frontend0
Feb 18 20:28:01 easyvdr vdr: dynamite: /dev/dvb/adapter0/frontend0 is a dvb adapter trying to set card index to 0
Feb 18 20:28:01 easyvdr vdr: new sub-device number 2
Feb 18 20:28:01 easyvdr vdr: ERROR: can't open DVB device 0/0
Feb 18 20:28:01 easyvdr vdr: cTimeMs: using monotonic clock (resolution is 1 ns)
Feb 18 20:28:01 easyvdr vdr: dynamite: attached device /dev/dvb/adapter0/frontend0 to dynamic device slot 1
Feb 18 20:28:01 easyvdr vdr: dynamite: /dev/dvb/adapter1/frontend0 is a dvb adapter trying to set card index to 1
Feb 18 20:28:01 easyvdr vdr: new sub-device number 3
Feb 18 20:28:01 easyvdr vdr: ERROR: can't open DVB device 1/0
Feb 18 20:28:01 easyvdr vdr: dynamite: attached device /dev/dvb/adapter1/frontend0 to dynamic device slot 2
Feb 18 20:28:01 easyvdr vdr: device 3 section handler thread started (pid=2949, tid=3013, prio=low)
Feb 18 20:28:01 easyvdr vdr: setting primary device to 3
Feb 18 20:28:01 easyvdr vdr: device 3 has no MPEG decoder
Feb 18 20:28:01 easyvdr vdr: trying device number 1 instead
Feb 18 20:28:01 easyvdr vdr: setting primary device to 1
Feb 18 20:28:01 easyvdr vdr: assuming manual start of VDR
Feb 18 20:28:01 easyvdr vdr: SVDRP listening on port 6419
Feb 18 20:28:01 easyvdr vdr: setting current skin to "sttng"
Feb 18 20:28:01 easyvdr vdr: loading /var/lib/vdr/themes/sttng-default.theme
Feb 18 20:28:01 easyvdr vdr: starting plugin: burn
Feb 18 20:28:01 easyvdr vdr: burn: setting fixed storemode to ISO
Feb 18 20:28:01 easyvdr kernel: [  15.360065] Registered IR keymap rc-dvbsky
Feb 18 20:28:01 easyvdr kernel: [  15.360244] input: IR (DVBSky S952 V3) as /devices/pci0000:00/0000:00:0c.0/0000:03:00.0/rc/rc0/input11
Feb 18 20:28:01 easyvdr kernel: [  15.360359] rc0: IR (DVBSky S952 V3) as /devices/pci0000:00/0000:00:0c.0/0000:03:00.0/rc/rc0
Feb 18 20:28:01 easyvdr kernel: [  15.360397] DVBSky SMI PCIe driver 0000:03:00.0: irq 48 for MSI/MSI-X
Feb 18 20:28:01 easyvdr vdr: burn-chain manager thread started (pid=2949, tid=3014, prio=high)
Feb 18 20:28:01 easyvdr vdr: burn: loaded skin Vorgabe using /var/lib/vdr/plugins/burn/menu-bg.png and /var/lib/vdr/plugins/burn/menu-button.png
Feb 18 20:28:01 easyvdr vdr: video directory scanner thread ended (pid=2949, tid=3005)
Feb 18 20:28:01 easyvdr vdr: burn: loaded skin fo-doku using /var/lib/vdr/plugins/burn/skins/fo-doku/menu-bg.png and /var/lib/vdr/plugins/burn/menu-button.png
Feb 18 20:28:01 easyvdr vdr: device 2 section handler thread started (pid=2949, tid=3012, prio=low)
Feb 18 20:28:01 easyvdr vdr: burn: loaded skin fo-kino using /var/lib/vdr/plugins/burn/skins/fo-kino/menu-bg.png and /var/lib/vdr/plugins/burn/menu-button.png
Feb 18 20:28:01 easyvdr vdr: burn: loaded skin fo-musik using /var/lib/vdr/plugins/burn/skins/fo-musik/menu-bg.png and /var/lib/vdr/plugins/burn/menu-button.png
Feb 18 20:28:01 easyvdr vdr: burn: loaded skin fo-kinder using /var/lib/vdr/plugins/burn/skins/fo-kinder/menu-bg.png and /var/lib/vdr/plugins/burn/menu-button.png
Feb 18 20:28:01 easyvdr vdr: burn: loaded skin fo-sport using /var/lib/vdr/plugins/burn/skins/fo-sport/menu-bg.png and /var/lib/vdr/plugins/burn/menu-button.png
Feb 18 20:28:01 easyvdr vdr: burn: loaded skin fo-natur using /var/lib/vdr/plugins/burn/skins/fo-natur/menu-bg.png and /var/lib/vdr/plugins/burn/menu-button.png
Feb 18 20:28:01 easyvdr vdr: starting plugin: devstatus
Feb 18 20:28:01 easyvdr vdr: starting plugin: extrecmenu
Feb 18 20:28:01 easyvdr vdr: starting plugin: femon
Feb 18 20:28:01 easyvdr vdr: starting plugin: live
Feb 18 20:28:01 easyvdr vdr: LIVE: initial file cache has 82 entries and needs 377394 bytes of data!
Feb 18 20:28:01 easyvdr vdr: starting plugin: markad
Feb 18 20:28:01 easyvdr vdr: starting plugin: streamdev-server
Feb 18 20:28:01 easyvdr vdr: loading /var/lib/vdr/plugins/streamdev-server/streamdevhosts.conf
Feb 18 20:28:01 easyvdr vdr: extrecmenu worker thread thread started (pid=2949, tid=3022, prio=high)
Feb 18 20:28:01 easyvdr vdr: INFO: attempt to listen on ip = '0.0.0.0'
Feb 18 20:28:01 easyvdr vdr: starting plugin: svdrposd
Feb 18 20:28:01 easyvdr vdr: starting plugin: systeminfo
Feb 18 20:28:01 easyvdr vdr: starting plugin: text2skin
Feb 18 20:28:01 easyvdr vdr: streamdev server thread started (pid=2949, tid=3041, prio=high)
Feb 18 20:28:01 easyvdr vdr: Streamdev: Listening (HTTP) on port 3000
Feb 18 20:28:01 easyvdr vdr: text2skin: loading /var/lib/vdr/plugins/text2skin/anthra_1920_FSt/anthra_1920_FSt.colors
Feb 18 20:28:01 easyvdr vdr: parsing /var/lib/vdr/plugins/text2skin/anthra_1920_FSt/anthra_1920_FSt.skin
Feb 18 20:28:01 easyvdr nvidia-persistenced: Started (3074)
Feb 18 20:28:01 easyvdr nvidia-persistenced: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 127 has read and write permissions for those files.
Feb 18 20:28:01 easyvdr nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced
Feb 18 20:28:01 easyvdr nvidia-persistenced: Shutdown (3074)
Feb 18 20:28:01 easyvdr kernel: [  15.603291] NVRM: The NVIDIA GeForce 7050 PV / nForce 630a GPU installed in this system is
Feb 18 20:28:01 easyvdr kernel: [  15.603291] NVRM:  supported through the NVIDIA 304.xx Legacy drivers. Please
Feb 18 20:28:01 easyvdr kernel: [  15.603291] NVRM:  visit http://www.nvidia.com/object/unix.html for more
Feb 18 20:28:01 easyvdr kernel: [  15.603291] NVRM:  information.  The 340.46 NVIDIA driver will ignore
Feb 18 20:28:01 easyvdr kernel: [  15.603291] NVRM:  this GPU.  Continuing probe...
Feb 18 20:28:01 easyvdr kernel: [  15.603309] NVRM: No NVIDIA graphics adapter found!
Feb 18 20:28:01 easyvdr kernel: [  15.603494] NVRM: NVIDIA init module failed!
Feb 18 20:28:01 easyvdr easyvdr-autostart: wait for X initialization
Feb 18 20:28:02 easyvdr vdr: starting plugin: vdrmanager
Feb 18 20:28:02 easyvdr vdr: starting plugin: xvdr
Feb 18 20:28:02 easyvdr vdr: XVDR: XVDR Server started
Feb 18 20:28:02 easyvdr vdr: XVDR: Channel streaming timeout: 3 seconds
Feb 18 20:28:02 easyvdr vdr: starting plugin: dummydevice
Feb 18 20:28:02 easyvdr vdr: starting plugin: setup
Feb 18 20:28:02 easyvdr vdr: starting plugin: dynamite
Feb 18 20:28:02 easyvdr vdr: dynamite: startup channel is 1
Feb 18 20:28:02 easyvdr vdr: created non SSL server socket on port 6420
Feb 18 20:28:02 easyvdr vdr: SSL key files /etc/vdr/plugins/vdrmanager/vdrmanager.pem and /etc/vdr/plugins/vdrmanager/vdrmanager.pem can't be read. SSL disabled.
Feb 18 20:28:02 easyvdr vdr: dynamite: /dev/dvb/adapter0/frontend0 is a dvb adapter trying to set card index to 0
Feb 18 20:28:02 easyvdr vdr: dynamite: /dev/dvb/adapter0/frontend0 is already attached
Feb 18 20:28:02 easyvdr vdr: dynamite: /dev/dvb/adapter1/frontend0 is a dvb adapter trying to set card index to 1
Feb 18 20:28:02 easyvdr vdr: dynamite: /dev/dvb/adapter1/frontend0 is already attached
Feb 18 20:28:02 easyvdr vdr: remote control LIRC - keys known
Feb 18 20:28:02 easyvdr vdr: remote control KBD - keys known
Feb 18 20:28:02 easyvdr vdr: switching to channel 1 (Das Erste)
Feb 18 20:28:02 easyvdr vdr: info: Kanal nicht verfügbar!
Feb 18 20:28:02 easyvdr lircd-0.9.0: accepted new client on /var/run/lirc/lircd
Feb 18 20:28:02 easyvdr vdr: VDR XVDR Server thread started (pid=2949, tid=3163, prio=high)
Feb 18 20:28:02 easyvdr vdr: LIRC remote control thread started (pid=2949, tid=3166, prio=high)
Feb 18 20:28:02 easyvdr vdr: KBD remote control thread started (pid=2949, tid=3167, prio=high)
Feb 18 20:28:02 easyvdr mdadm: DegradedArray event detected on md device /dev/md/md0
Feb 18 20:28:02 easyvdr postfix/pickup: 4C596E85FE: uid=0 from=
Feb 18 20:28:02 easyvdr postfix/cleanup: 4C596E85FE: message-id=<20160218192802.4C596E85FE@martin-13.04-64-Dev>
Feb 18 20:28:02 easyvdr postfix/qmgr: 4C596E85FE: from=, size=790, nrcpt=1 (queue active)
Feb 18 20:28:02 easyvdr postfix/local: 4C596E85FE: to=, orig_to=, relay=local, delay=0.06, delays=0.04/0.02/0/0.01, dsn=2.0.0, status=sent (delivered to mailbox)
Feb 18 20:28:02 easyvdr postfix/qmgr: 4C596E85FE: removed
Feb 18 20:28:02 easyvdr vdr: epg data reader thread ended (pid=2949, tid=3007)
Feb 18 20:28:02 easyvdr kernel: [  16.403230] init: plymouth-stop pre-start process (3271) terminated with status 1
Feb 18 20:28:02 easyvdr easyvdr-autostart: mount -a
Feb 18 20:28:02 easyvdr easyvdr-autostart: wait for X initialization
Feb 18 20:28:03 easyvdr easyvdr-systemstart: wait for vdr
Feb 18 20:28:03 easyvdr vdr: connect from 127.0.0.1, port 59207 - accepted
Feb 18 20:28:03 easyvdr vdr: closing SVDRP connection
Feb 18 20:28:03 easyvdr easyvdr-systemstart: step 1/2 job easyvdr-vdr is running
Feb 18 20:28:03 easyvdr easyvdr-systemstart: step 2/2 starting job easyvdr-frontend
Feb 18 20:28:03 easyvdr kernel: [  17.099710] init: easyvdr-frontend main process (3304) killed by TERM signal
Feb 18 20:28:03 easyvdr easyvdr-systemstart: ready
Feb 18 20:28:03 easyvdr easyvdr-autostart: wait for X initialization
Feb 18 20:28:04 easyvdr ntpdate: adjust time server 91.189.94.4 offset -0.258250 sec
Feb 18 20:28:04 easyvdr easyvdr-autostart: wait for X initialization
Feb 18 20:28:05 easyvdr easyvdr-autostart: wait for X initialization
Feb 18 20:28:06 easyvdr easyvdr-autostart: wait for X initialization
Feb 18 20:28:07 easyvdr vdr: ERROR: libmcsimple.so: cannot open shared object file: No such file or directory
Feb 18 20:28:07 easyvdr vdr: dynamite udev monitor for subsystem dvb thread started (pid=3463, tid=3466, prio=high)
Feb 18 20:28:07 easyvdr vdr: dynamite udev monitor for subsystem dvb thread ended (pid=3463, tid=3466)
Feb 18 20:28:08 easyvdr easyvdr-autostart: wait for X initialization
Feb 18 20:28:08 easyvdr vdr: setting watchdog timer to 500 seconds
Feb 18 20:28:08 easyvdr vdr: OSD size changed to 720x480 @ 1
Feb 18 20:28:09 easyvdr easyvdr-autostart: wait for X initialization
Feb 18 20:28:09 easyvdr NetworkManager: WiFi hardware radio set enabled
Feb 18 20:28:09 easyvdr vdr: max. latency time 1 seconds
Feb 18 20:28:10 easyvdr easyvdr-autostart: wait for X initialization
Feb 18 20:28:10 easyvdr ntpdate: adjust time server 91.189.94.4 offset -0.257712 sec
Feb 18 20:28:11 easyvdr easyvdr-autostart: wait for X initialization
Feb 18 20:28:17 easyvdr easyvdr-autostart: wait for X initialization
Feb 18 20:28:18 easyvdr easyvdr-autostart: wait for X initialization
Feb 18 20:28:18 easyvdr postfix/pickup: 3B026E85FE: uid=888 from=
Feb 18 20:28:18 easyvdr postfix/cleanup: 3B026E85FE: message-id=<20160218192818.3B026E85FE@martin-13.04-64-Dev>
Feb 18 20:28:18 easyvdr postfix/qmgr: 3B026E85FE: from=, size=533, nrcpt=1 (queue active)
Feb 18 20:28:18 easyvdr postfix/local: 3B026E85FE: to=, orig_to=, relay=local, delay=0.02, delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (delivered to mailbox)
Feb 18 20:28:18 easyvdr postfix/qmgr: 3B026E85FE: removed
Feb 18 20:28:19 easyvdr easyvdr-autostart: wait for X initialization
Feb 18 20:28:19 easyvdr NetworkManager: (eth0): IP6 addrconf timed out or failed.
Feb 18 20:28:19 easyvdr NetworkManager: Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Feb 18 20:28:19 easyvdr NetworkManager: Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Feb 18 20:28:19 easyvdr NetworkManager: Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Feb 18 20:28:19 easyvdr vdr: connect from 127.0.0.1, port 59208 - accepted
Feb 18 20:28:19 easyvdr vdr: closing SVDRP connection
Feb 18 20:28:20 easyvdr easyvdr-autostart: wait for X initialization
Feb 18 20:28:21 easyvdr easyvdr-autostart: wait for X initialization
Feb 18 20:28:21 easyvdr ntpdate: adjust time server 91.189.94.4 offset -0.251608 sec
Feb 18 20:28:22 easyvdr easyvdr-autostart: wait for X initialization
Feb 18 20:28:23 easyvdr easyvdr-autostart: wait for X initialization
Feb 18 20:28:24 easyvdr postfix/pickup: 3041CE85FE: uid=888 from=
Feb 18 20:28:24 easyvdr postfix/cleanup: 3041CE85FE: message-id=<20160218192824.3041CE85FE@martin-13.04-64-Dev>
Feb 18 20:28:24 easyvdr postfix/qmgr: 3041CE85FE: from=, size=533, nrcpt=1 (queue active)
Feb 18 20:28:24 easyvdr postfix/local: 3041CE85FE: to=, orig_to=, relay=local, delay=0.02, delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (delivered to mailbox)
Feb 18 20:28:24 easyvdr postfix/qmgr: 3041CE85FE: removed
Feb 18 20:28:24 easyvdr easyvdr-autostart: wait for X initialization
Feb 18 20:28:25 easyvdr easyvdr-autostart: wait for X initialization
Feb 18 20:28:26 easyvdr easyvdr-autostart: wait for X initialization
Feb 18 20:28:27 easyvdr easyvdr-autostart: wait for X initialization
Feb 18 20:28:27 easyvdr easyvdr-autostart: Wait more than 30 seconds for X initialization - give up
Feb 18 20:28:29 easyvdr easyvdr-autostart: starting easyvdr-power-save
Feb 18 20:28:29 easyvdr easyvdr-autostart: set homedir perms started
Feb 18 20:28:29 easyvdr easyvdr-autostart: set homedir perms finished
Feb 18 20:28:55 easyvdr vdr: Streamdev: Accepted new client (HTTP) 192.168.178.25:50010
Feb 18 20:28:55 easyvdr vdr: streamdev: No device provides channel 3 (RTL Television) at priority 0
Feb 18 20:28:55 easyvdr vdr: streamdev-server: closing HTTP connection to 192.168.178.25:50010
Feb 18 20:28:55 easyvdr vdr: Streamdev: Accepted new client (HTTP) 192.168.178.25:50011
Feb 18 20:28:55 easyvdr vdr: streamdev: No device provides channel 3 (RTL Television) at priority 0
Feb 18 20:28:55 easyvdr vdr: streamdev-server: closing HTTP connection to 192.168.178.25:50011
Feb 18 20:28:55 easyvdr vdr: Streamdev: Accepted new client (HTTP) 192.168.178.25:50012
Feb 18 20:28:55 easyvdr vdr: streamdev: No device provides channel 3 (RTL Television) at priority 0
Feb 18 20:28:55 easyvdr vdr: streamdev-server: closing HTTP connection to 192.168.178.25:50012

Was ich auch merkwürdig finde - und wo es vielleicht auch einen Zusammenhang gibt: Ich hatte kurzzeitig mal mit dem
Ausgabedevice rumgespielt - es später jedoch wieder deaktiviert, da der Server Headless arbeiten sollte. In der sysconfig steht also

VDR_FRONTEND="keines" Via sudo setup habe ich easyvdr wieder auf Headless gestellt.

Dennoch erscheint ständig der Hinweis "wait for X initialization" bzw. der Versuch, die NVIDIA-Treiber zu laden.

Kann sein, dass das eine mit dem anderen nichts zu tun hat - ich meine aber einen gewissen zeitlichen Zusammenhang erkannt zu haben...ich bin verwirrt.
Bleifuss2  18.Feb.2016 21:07:21
Dennoch erscheint ständig der Hinweis "wait for X initialization" bzw. der Versuch, die NVIDIA-Treiber zu laden.

Da hast du noch einen Bug gefunden, hast du was in der Autostart Datei geändert? Wird vielleicht noch was gemountet?
Wenn nicht dann ist das nicht das Problem, ich passe es demnächst aber an.

Den Nvidia würde ich aber deinstallieren:
sudo apt-get purge nvidia*

Gruß
Bleifuss
Produktiv-VDR:
Board GA H77-DS3H, Intel Intel(R) Core(TM) i5-3470, Cine S2 DVB, WD 3TB Green, WDC WD20EARS-00J  2TB, Geforce 750Ti oder Intel HD
Easyvdr 3.0
KaiCrow  18.Feb.2016 21:47:35
[quote='Bleifuss2 link' pid='18022' dateline='1455826041']

hast du was in der Autostart Datei geändert? Wird vielleicht noch was gemountet?


Was für eine Autostart-Datei meinst du?
Gemountet habe ich noch ein Raid.

Das dynamite-Plugin scheint doch geholfen zu haben - nach einem Reboot scheint es erstmal zu funktionieren.
Bleifuss2  19.Feb.2016 15:23:37
Das hier:

[url=http://wiki.easy-vdr.de/index.php?title=Easyvdr-autostart]http://wiki.easy-vdr.de/index.php?title=Easyvdr-autostart

Da wird nochmal gemountet, wenn das Netz läuft, nur wenn du kein X hast geht es so nicht richtig.
Man denkt nicht immer an alles ...
Update kommt noch.

Gruß
Bleifuss
Produktiv-VDR:
Board GA H77-DS3H, Intel Intel(R) Core(TM) i5-3470, Cine S2 DVB, WD 3TB Green, WDC WD20EARS-00J  2TB, Geforce 750Ti oder Intel HD
Easyvdr 3.0
KaiCrow  26.Feb.2016 21:49:12
Ich muss das Thema leider nochmal aufgreifen. Ich habe "[url=http://www.easy-vdr.de/forum/index.php?topic=18370.0]aus Gründen" im VDR-Setup mochmals als Video-Ausgabe "Headless als Server ohne Ausgabedevice" ausgewählt.
Nun habe ich diesen Effekt erneut. Das dynamite-Plugin scheint auch nicht (mehr) zu helfen. Was könnte ich damit "angerichtet" haben?

Wie gesagt: Stoppe und starte ich den vdr, dann ist wieder alles in bester Ordnung.
mango  26.Feb.2016 22:21:01
Hi,

[quote='KaiCrow link' pid='18022' dateline='1456519752']
Wie gesagt: Stoppe und starte ich den vdr, dann ist wieder alles in bester Ordnung.
Bitte easyInfo anhängen!

Gruss
Wolfgang
[spoiler="My VDR Stuff"]DVB-S/S2: Silverstone LC17 mit 8,4" TFT Display, ASUS P5KPL SE, E6300, 2GB, NT-Fanlees, System SSD 40GB, Media 2TB, GT630, DVD-LG, SkyStar S2, Nova-T, FB X10 Medion-Scroll, "Arch-Linux - VDR 2.3.8"
Test-VDR: ASRock ALiveNF6G, AMD X2 3800+ (35W),4GB, GT 630 - nvidia-384, SSD 64GB, SkyStar S2, Cinergy T RC USB, easyVDR 3.5(Kernel-4.4.0) - VDR-2.3.8 - KODI-18.0 - FB X10 Medion-Scroll
Client: Evo N600c, Puppy-Slacko 6.3 - VDR-2.2.0 - FB X10 Medion_OR25V
Spielwiese: RPI2 als Client mit LibreELEC-9.80-Milhouse(Kodi-19.0) - MLD-5.4 VDR2VDR
KaiCrow  29.Feb.2016 21:23:35
Hallo Mango,

habe die easyinfo angehängt.

Nochmal zur Info (kurz nach 21 Uhr gerade getestet...siehe Log):
Headless VDR bootet, ich kann ein Programm via Live (Browser-Straming) schauen. Nehme ich zeitgleich ein anderes Programm auf, stoppt das Live-TV.
Stoppe ich das VDR-Programm und starte es wieder neu (via SSH + setup) klappt der Zugriff auf beide Tuner (Aufnahme + Live-TV).

Bin für jeden Hinweis dankbar.

Grüße,
KaiCrow
easyinfo_16-02-29_2110_mod.log
mango  29.Feb.2016 23:09:51
Hi,


Feb 29 21:05:09 easyvdr vdr: registered source parameters for 'T - DVB-T'
Feb 29 21:05:09 easyvdr vdr: ERROR (dvbdevice.c,1253): /dev/dvb/adapter0/frontend0: Keine Berechtigung
Feb 29 21:05:09 easyvdr vdr: no DVB device found
Feb 26 21:22:20 easyvdr vdr: ERROR: libmcsimple.so: cannot open shared object file: No such file or directory
war da mal ein Sundtek-Stick installiert??  ..."libmcsimple.so" gibt es nur im Paket "dvb-driver-sundtek-libs"

Feb 29 21:09:36 easyvdr vdr: XVDR-Error: Unable to open channel cache data file (/var/cache/vdr/plugins/xvdr/channelcache.data) !
Fehler lässt sich mit
sudo touch /var/cache/vdr/plugins/xvdr/channelcache.data
sudo chown vdr:vdr /var/cache/vdr/plugins/xvdr/channelcache.data
beheben.

Feb 26 21:21:24 easyvdr kernel: [    6.831538] systemd-udevd: starting version 204
Feb 26 21:21:24 easyvdr kernel: [    6.952926] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
Feb 26 21:21:24 easyvdr kernel: [    6.959205] lp: driver loaded but no devices found
--
Feb 26 21:21:24 easyvdr kernel: [    7.382995] Key type cifs.idmap registered
Feb 26 21:21:24 easyvdr kernel: [    7.387397] CIFS VFS: Error connecting to socket. Aborting operation.
Feb 26 21:21:24 easyvdr kernel: [    7.387573] CIFS VFS: cifs_mount failed w/return code = -101
Feb 26 21:21:24 easyvdr kernel: [    7.436090] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Feb 26 21:21:24 easyvdr kernel: [    7.458774] CIFS VFS: Error connecting to socket. Aborting operation.
Feb 26 21:21:24 easyvdr kernel: [    7.459745] CIFS VFS: cifs_mount failed w/return code = -101
--
Feb 26 21:21:24 easyvdr kernel: [    7.911495] k8temp 0000:00:18.3: Temperature readouts might be wrong - check erratum #141
Feb 26 21:21:24 easyvdr kernel: [    8.156390] CIFS VFS: Error connecting to socket. Aborting operation.
Feb 26 21:21:24 easyvdr kernel: [    8.156532] CIFS VFS: cifs_mount failed w/return code = -101
--
Feb 26 21:21:24 easyvdr vdr: dynamite udev monitor for subsystem dvb thread ended (pid=715, tid=782)
Feb 26 21:21:24 easyvdr kernel: [    8.672841] CIFS VFS: Error connecting to socket. Aborting operation.
Feb 26 21:21:24 easyvdr kernel: [    8.675077] CIFS VFS: cifs_mount failed w/return code = -101
--
Feb 26 21:21:26 easyvdr lircd-0.9.0: lircd(audio_alsa) ready, using /var/run/lirc/lircd
Feb 26 21:21:26 easyvdr kernel: [  10.246064] CIFS VFS: Error connecting to socket. Aborting operation.
Feb 26 21:21:26 easyvdr kernel: [  10.253835] CIFS VFS: cifs_mount failed w/return code = -101
--
Feb 26 21:21:27 easyvdr avahi-daemon: Registering new address record for fe80::219:66ff:feaa:7568 on eth0.*.
Feb 26 21:21:27 easyvdr kernel: [  10.935947] CIFS VFS: Error connecting to socket. Aborting operation.
Feb 26 21:21:27 easyvdr kernel: [  10.937167] CIFS VFS: cifs_mount failed w/return code = -101
cifs_mount failed ..da stimmt wohl der Eintrag in fstab nicht!

Feb 26 21:21:31 easyvdr vdr: ERROR: unknown config parameter: JumpPlay = 1
Feb 26 21:21:31 easyvdr vdr: ERROR: unknown config parameter: PauseLastMark = 1
Feb 26 21:21:31 easyvdr vdr: ERROR: unknown config parameter: PlayJump = 1
diese Parameter kannst du in der "/var/lib/vdr/setup.conf" löschen.(nur kosmetik)

Gruss
Wolfgang
[spoiler="My VDR Stuff"]DVB-S/S2: Silverstone LC17 mit 8,4" TFT Display, ASUS P5KPL SE, E6300, 2GB, NT-Fanlees, System SSD 40GB, Media 2TB, GT630, DVD-LG, SkyStar S2, Nova-T, FB X10 Medion-Scroll, "Arch-Linux - VDR 2.3.8"
Test-VDR: ASRock ALiveNF6G, AMD X2 3800+ (35W),4GB, GT 630 - nvidia-384, SSD 64GB, SkyStar S2, Cinergy T RC USB, easyVDR 3.5(Kernel-4.4.0) - VDR-2.3.8 - KODI-18.0 - FB X10 Medion-Scroll
Client: Evo N600c, Puppy-Slacko 6.3 - VDR-2.2.0 - FB X10 Medion_OR25V
Spielwiese: RPI2 als Client mit LibreELEC-9.80-Milhouse(Kodi-19.0) - MLD-5.4 VDR2VDR
KaiCrow  03.Mar.2016 20:45:30
Danke für die Hinweise.

"Plötzlich" hat es wieder funktioniert, ohne dass ich was geändert habe.

Habe deine Anmerkungen dennoch umgesetzt.

Ein "Sundtek-Stick" war nicht installiert. Wo die Meldung herkommt weiß ich nicht.

Grüße,
KaiCrow