[1] MLD-6.x / General / Neustart VDR auf RPI5 geht nicht mehr richtig
 

Online michaott

  • Newbie
  • *
  • Posts: 47
    • View Profile
Neustart VDR auf RPI5 geht nicht mehr richtig
« on: September 27, 2026, 18:28:39 »
Hallo,

gefühlt seit dem letzten Update von webif, ca. Anfang letzte Woche, startet beim Systemstart zuerst VDR und dann vtunerc/satip was dazu führt das VDR keinen Sender findet. Vorher, bis Anfang letzte Woche, lief ein Neustart immer korrekt.

Ein Neustart von VDR behebt das Problem.

Woran kann das liegen?

Grüße Michael

OctopusNet 8x DVB-S2
MLD 6.5, Raspberry 5, Argon ONE V3 M.2 Case, SSD 1TB

Offline clausmuus

  • Administrator
  • Expert Member
  • ********
  • Posts: 21565
    • View Profile
    • ClausMuus.de
Neustart VDR auf RPI5 geht nicht mehr richtig
« Reply #1 on: September 27, 2026, 22:18:01 »
Vor 'ner Woche habe ich das Warten auf vtuner satip überarbeitet, da es vorher vorkommen konnte, dass der VDR zu früh gestartet ist.
Da das Update bei Dir offensichtlich zu Problemen führt, bräuchte ich mal ein Debug-Log nach dem VDR Restart. Was ich da drin u.a. sehen möchte, ist ob das Webif Fehler Logt, und wie viele dvb Devices erkannt wurden.
MLD 5.5 - Raspberry PI - 7" Touch TFT - Squeeze Play
MLD 6.5 - lirc yaUsbIR - 4 x DD-Sat - Intel N100M - 4GB RAM - 64GB SSD + 12TB HDD + 22TB HDD - Lian Li PC-C37B - Samsung LE40A559

Online michaott

  • Newbie
  • *
  • Posts: 47
    • View Profile
Neustart VDR auf RPI5 geht nicht mehr richtig
« Reply #2 on: Today at 03:48:28 »

hier Auszug aus dem Log,

WebIF:
Sep 27 16:27:39 MLD systemd[1]: Starting The MLD webif...
Sep 27 16:27:40 MLD webif[903]: Listen on port 80 ...
Sep 27 16:27:40 MLD systemd[1]: Started The MLD webif.
Sep 27 16:27:40 MLD webif[903]: TypeError: Cannot read properties of undefined (reading 'startsWith')
Sep 27 16:27:40 MLD webif[903]:     at /usr/share/webif/modules/settings/display.js:30:45
Sep 27 16:27:40 MLD webif[903]:     at async /usr/share/webif/modules/settings/display.js:50:32
Sep 27 16:27:40 MLD webif[903]:     at async Object.get (/usr/share/webif/modules/api.js:28:22)
Sep 27 16:27:40 MLD webif[903]:     at async /usr/share/webif/modules/request.js:13:15
Sep 27 16:28:42 MLD webif[903]: TypeError: Cannot read properties of undefined (reading 'startsWith')
Sep 27 16:28:42 MLD webif[903]:     at /usr/share/webif/modules/settings/display.js:30:45
Sep 27 16:28:42 MLD webif[903]:     at async /usr/share/webif/modules/settings/display.js:50:32
Sep 27 16:28:42 MLD webif[903]:     at async Object.get (/usr/share/webif/modules/api.js:28:22)
Sep 27 16:28:42 MLD webif[903]:     at async /usr/share/webif/modules/request.js:13:15
Sep 28 03:41:05 MLD webif[903]: TypeError: Cannot read properties of undefined (reading 'startsWith')
Sep 28 03:41:05 MLD webif[903]:     at /usr/share/webif/modules/settings/display.js:30:45
Sep 28 03:41:05 MLD webif[903]:     at async /usr/share/webif/modules/settings/display.js:50:32
Sep 28 03:41:05 MLD webif[903]:     at async Object.get (/usr/share/webif/modules/api.js:28:22)
Sep 28 03:41:05 MLD webif[903]:     at async /usr/share/webif/modules/request.js:13:15

VDR Start, Devices:

Sep 28 03:41:15 MLD vdr[21142]: [21142] detected /dev/dvb/adapter0/frontend0
Sep 28 03:41:15 MLD vdr[21142]: [21142] detected /dev/dvb/adapter1/frontend0
Sep 28 03:41:15 MLD vdr[21142]: [21142] detected /dev/dvb/adapter2/frontend0
Sep 28 03:41:15 MLD vdr[21142]: [21142] detected /dev/dvb/adapter3/frontend0
Sep 28 03:41:15 MLD vdr[21142]: [21142] detected /dev/dvb/adapter4/frontend0
Sep 28 03:41:15 MLD vdr[21142]: [21142] detected /dev/dvb/adapter5/frontend0
Sep 28 03:41:15 MLD vdr[21142]: [21142] probing /dev/dvb/adapter0/frontend0
Sep 28 03:41:15 MLD vdr[21142]: [21142] creating cDvbDevice
Sep 28 03:41:15 MLD vdr[21142]: [21142] new device number 2 (card index 2)
Sep 28 03:41:15 MLD vdr[21142]: [21142] cTimeMs: using monotonic clock (resolution is 1 ns)
Sep 28 03:41:15 MLD vdr[21142]: [21159] device 1 CI adapter thread started (pid=21142, tid=21159, prio=high)
Sep 28 03:41:15 MLD vdr[21142]: [21160] device 2 section handler thread started (pid=21142, tid=21160, prio=low)
Sep 28 03:41:15 MLD vdr[21142]: [21142] DVB API version is 0x050C (VDR was built with 0x050C)
Sep 28 03:41:15 MLD vdr[21142]: [21142] frontend 0/0 provides DVB-T,DVB-T2,DVB-C,DVB-C,DVB-C,DVB-S,DVB-S2 with QPSK,QAM16,QAM32,QAM64,QAM128,QAM256,VSB8,VSB16,TURBO_FEC ("vTuner proxyFE DVB-Multi")
Sep 28 03:41:15 MLD vdr[21142]: [21162] frontend 0/0 tuner thread started (pid=21142, tid=21162, prio=high)
Sep 28 03:41:15 MLD vdr[21142]: [21142] probing /dev/dvb/adapter1/frontend0
Sep 28 03:41:15 MLD vdr[21142]: [21142] creating cDvbDevice
Sep 28 03:41:15 MLD vdr[21142]: [21142] new device number 3 (card index 3)
Sep 28 03:41:15 MLD vdr[21142]: [21142] frontend 1/0 provides DVB-T,DVB-T2,DVB-C,DVB-C,DVB-C,DVB-S,DVB-S2 with QPSK,QAM16,QAM32,QAM64,QAM128,QAM256,VSB8,VSB16,TURBO_FEC ("vTuner proxyFE DVB-Multi")
Sep 28 03:41:15 MLD vdr[21142]: [21167] frontend 1/0 tuner thread started (pid=21142, tid=21167, prio=high)
Sep 28 03:41:15 MLD vdr[21142]: [21163] device 2 CI adapter thread started (pid=21142, tid=21163, prio=high)
Sep 28 03:41:15 MLD vdr[21142]: [21142] probing /dev/dvb/adapter2/frontend0
Sep 28 03:41:15 MLD vdr[21142]: [21142] creating cDvbDevice
Sep 28 03:41:15 MLD vdr[21142]: [21142] new device number 4 (card index 4)
Sep 28 03:41:15 MLD vdr[21142]: [21164] device 3 section handler thread started (pid=21142, tid=21164, prio=low)
Sep 28 03:41:15 MLD vdr[21142]: [21142] frontend 2/0 provides DVB-T,DVB-T2,DVB-C,DVB-C,DVB-C,DVB-S,DVB-S2 with QPSK,QAM16,QAM32,QAM64,QAM128,QAM256,VSB8,VSB16,TURBO_FEC ("vTuner proxyFE DVB-Multi")
Sep 28 03:41:15 MLD vdr[21142]: [21169] device 4 section handler thread started (pid=21142, tid=21169, prio=low)
Sep 28 03:41:15 MLD vdr[21142]: [21172] frontend 2/0 tuner thread started (pid=21142, tid=21172, prio=high)
Sep 28 03:41:15 MLD vdr[21142]: [21142] probing /dev/dvb/adapter3/frontend0
Sep 28 03:41:15 MLD vdr[21142]: [21142] creating cDvbDevice
Sep 28 03:41:15 MLD vdr[21142]: [21142] new device number 5 (card index 5)
Sep 28 03:41:15 MLD vdr[21142]: [21174] device 5 section handler thread started (pid=21142, tid=21174, prio=low)
Sep 28 03:41:15 MLD vdr[21142]: [21142] frontend 3/0 provides DVB-T,DVB-T2,DVB-C,DVB-C,DVB-C,DVB-S,DVB-S2 with QPSK,QAM16,QAM32,QAM64,QAM128,QAM256,VSB8,VSB16,TURBO_FEC ("vTuner proxyFE DVB-Multi")
Sep 28 03:41:15 MLD vdr[21142]: [21177] frontend 3/0 tuner thread started (pid=21142, tid=21177, prio=high)
Sep 28 03:41:15 MLD vdr[21142]: [21142] probing /dev/dvb/adapter4/frontend0
Sep 28 03:41:15 MLD vdr[21142]: [21142] creating cDvbDevice
Sep 28 03:41:15 MLD vdr[21142]: [21142] new device number 6 (card index 6)
Sep 28 03:41:15 MLD vdr[21142]: [21168] device 3 CI adapter thread started (pid=21142, tid=21168, prio=high)
Sep 28 03:41:15 MLD vdr[21142]: [21178] device 5 CI adapter thread started (pid=21142, tid=21178, prio=high)
Sep 28 03:41:15 MLD vdr[21142]: [21142] frontend 4/0 provides DVB-T,DVB-T2,DVB-C,DVB-C,DVB-C,DVB-S,DVB-S2 with QPSK,QAM16,QAM32,QAM64,QAM128,QAM256,VSB8,VSB16,TURBO_FEC ("vTuner proxyFE DVB-Multi")
Sep 28 03:41:15 MLD vdr[21142]: [21182] frontend 4/0 tuner thread started (pid=21142, tid=21182, prio=high)
Sep 28 03:41:15 MLD vdr[21142]: [21142] probing /dev/dvb/adapter5/frontend0
Sep 28 03:41:15 MLD vdr[21142]: [21142] creating cDvbDevice
Sep 28 03:41:15 MLD vdr[21142]: [21142] new device number 7 (card index 7)
Sep 28 03:41:15 MLD vdr[21142]: [21173] device 4 CI adapter thread started (pid=21142, tid=21173, prio=high)
Sep 28 03:41:15 MLD vdr[21142]: [21183] device 6 CI adapter thread started (pid=21142, tid=21183, prio=high)
Sep 28 03:41:15 MLD vdr[21142]: [21142] frontend 5/0 provides DVB-T,DVB-T2,DVB-C,DVB-C,DVB-C,DVB-S,DVB-S2 with QPSK,QAM16,QAM32,QAM64,QAM128,QAM256,VSB8,VSB16,TURBO_FEC ("vTuner proxyFE DVB-Multi")
Sep 28 03:41:15 MLD vdr[21142]: [21142] found 6 DVB devices
Sep 28 03:41:15 MLD vdr[21142]: [21187] frontend 5/0 tuner thread started (pid=21142, tid=21187, prio=high)

OctopusNet 8x DVB-S2
MLD 6.5, Raspberry 5, Argon ONE V3 M.2 Case, SSD 1TB

[1] MLD-6.x / General / Neustart VDR auf RPI5 geht nicht mehr richtig
 



Users Online Users Online

0 Members and 1 Guest are viewing this topic.