RPI3 / VDR dreht Schleifen [Problem verschwunden]

  • Seit dem letzten Upgrade (Raspbian) dreht mein VDR Schleifen. Ich weiss nichtmal, wo ich anfangen soll, nach dem Problem zu suchen.


    Code
    Mar 31 21:50:02 adler systemd[1]: vdr.service: Main process exited, code=killed, status=11/SEGV
    Mar 31 21:50:02 adler systemd[1]: vdr.service: Failed with result 'signal'.
    Mar 31 21:50:02 adler systemd[1]: vdr.service: Service RestartSec=100ms expired, scheduling restart.
    Mar 31 21:50:02 adler systemd[1]: vdr.service: Scheduled restart job, restart counter is at 600.
    Mar 31 21:50:02 adler systemd[1]: Stopped Video Disk Recorder.
    Mar 31 21:50:02 adler systemd[1]: Starting Video Disk Recorder...
    Mar 31 21:50:02 adler vdr: [23976] VDR version 2.4.0 started


    Code
    Start-Date: 2021-03-30  20:54:18
    Commandline: apt-get dist-upgrade
    Requested-By: pi (1000)
    Install: libjson-glib-1.0-0:armhf (1.4.4-2, automatic), libsoup-gnome2.4-1:armhf (2.64.2-2, automatic), libcroco3:armhf (0.6.12-3, automatic), libpangoft2-1.0-0:armhf (1.42.4-8~deb10u1, automatic), glib-networking-services:armhf (2.58.0-2+deb10u2, automatic), libvte-2.91-0:armhf (0.54.2-2, automatic), libwayland-egl1:armhf (1.16.0-1, automatic), gir1.2-gtk-3.0:armhf (3.24.5-1+rpt2, automatic), gir1.2-gdkpixbuf-2.0:armhf (2.38.1+dfsg-1, automatic), libgdk-pixbuf2.0-0:armhf (2.38.1+dfsg-1, automatic), libproxy1v5:armhf (0.4.15-5+deb10u1, automatic), libcairo-gobject2:armhf (1.16.0-4+rpt1, automatic), glib-networking:armhf (2.58.0-2+deb10u2, automatic), libgtk-3-common:armhf (3.24.5-1+rpt2, automatic), libgtk-3-0:armhf (3.24.5-1+rpt2, automatic), librsvg2-common:armhf (2.44.10-2.1+rpi1, automatic), gir1.2-atk-1.0:armhf (2.30.0-2, automatic), at-spi2-core:armhf (2.30.0-7, automatic), libxcursor1:armhf (1:1.1.15-2, automatic), libthai-data:armhf (0.1.28-2, automatic), gir1.2-pango-1.0:armhf (1.42.4-8~deb10u1, automatic), libepoxy0:armhf (1.5.3-0.1, automatic), gsettings-desktop-schemas:armhf (3.28.1-1, automatic), gir1.2-freedesktop:armhf (1.58.3-2, automatic), glib-networking-common:armhf (2.58.0-2+deb10u2, automatic), libsoup2.4-1:armhf (2.64.2-2, automatic), libwayland-client0:armhf (1.16.0-1, automatic), libpangoxft-1.0-0:armhf (1.42.4-8~deb10u1, automatic), fontconfig:armhf (2.13.1-2, automatic), libatk1.0-0:armhf (2.30.0-2, automatic), libxcomposite1:armhf (1:0.4.4-2, automatic), adwaita-icon-theme:armhf (3.30.1-1, automatic), libgtk-3-bin:armhf (3.24.5-1+rpt2, automatic), libpangocairo-1.0-0:armhf (1.42.4-8~deb10u1, automatic), gir1.2-vte-2.91:armhf (0.54.2-2, automatic), libatspi2.0-0:armhf (2.30.0-7, automatic), librsvg2-2:armhf (2.44.10-2.1+rpi1, automatic), libxinerama1:armhf (2:1.1.4-2, automatic), libxft2:armhf (2.3.2-2, automatic), libjson-glib-1.0-common:armhf (1.4.4-2, automatic), libxrandr2:armhf (2:1.5.1-1, automatic), libgdk-pixbuf2.0-bin:armhf (2.38.1+dfsg-1, automatic), hicolor-icon-theme:armhf (0.17-2, automatic), libxfixes3:armhf (1:5.0.3-1, automatic), libthai0:armhf (0.1.28-2, automatic), libgdk-pixbuf2.0-common:armhf (2.38.1+dfsg-1, automatic), libgraphite2-3:armhf (1.3.13-7, automatic), libxdamage1:armhf (1:1.1.4-3+b3, automatic), librest-0.7-0:armhf (0.8.1-1, automatic), libatk-bridge2.0-0:armhf (2.30.0-5, automatic), libvte-2.91-common:armhf (0.54.2-2, automatic), gtk-update-icon-cache:armhf (3.24.5-1+rpt2, automatic), libatk1.0-data:armhf (2.30.0-2, automatic), libharfbuzz0b:armhf (2.3.1-1, automatic), libpango-1.0-0:armhf (1.42.4-8~deb10u1, automatic), libxkbcommon0:armhf (0.8.2-1, automatic), libdatrie1:armhf (0.2.12-2, automatic), libwayland-cursor0:armhf (1.16.0-1, automatic)
    Upgrade: libpython3.7-minimal:armhf (3.7.3-2+deb10u2, 3.7.3-2+deb10u3), lirc:armhf (0.10.1-6.2~deb10u1+rpt1, 0.10.1-6.3~deb10u1), openssl:armhf (1.1.1d-0+deb10u5+rpt2, 1.1.1d-0+deb10u6+rpt1), libportaudio2:armhf (19.6.0-1, 19.6.0-1+deb10u1), libavahi-glib1:armhf (0.7-4+b1, 0.7-4+deb10u1), rpi-eeprom:armhf (11.12-1, 12.0-1), libbsd0:armhf (0.9.1-2, 0.9.1-2+deb10u1), libavahi-common-data:armhf (0.7-4+b1, 0.7-4+deb10u1), libavahi-common3:armhf (0.7-4+b1, 0.7-4+deb10u1), libpython3.7:armhf (3.7.3-2+deb10u2, 3.7.3-2+deb10u3), python3.7:armhf (3.7.3-2+deb10u2, 3.7.3-2+deb10u3), libpython3.7-stdlib:armhf (3.7.3-2+deb10u2, 3.7.3-2+deb10u3), python3.7-minimal:armhf (3.7.3-2+deb10u2, 3.7.3-2+deb10u3), groff-base:armhf (1.22.4-3, 1.22.4-3+deb10u1), avahi-daemon:armhf (0.7-4+b1, 0.7-4+deb10u1), libavahi-core7:armhf (0.7-4+b1, 0.7-4+deb10u1), iputils-ping:armhf (3:20180629-2+deb10u1, 3:20180629-2+deb10u2), libssl1.1:armhf (1.1.1d-0+deb10u5+rpt2, 1.1.1d-0+deb10u6+rpt1), libavahi-client3:armhf (0.7-4+b1, 0.7-4+deb10u1), liblirc0:armhf (0.10.1-6.2~deb10u1+rpt1, 0.10.1-6.3~deb10u1), liblirc-client0:armhf (0.10.1-6.2~deb10u1+rpt1, 0.10.1-6.3~deb10u1)
    End-Date: 2021-03-30  20:56:35
  • Ich weiss nichtmal, wo ich anfangen soll, nach dem Problem zu suchen.

    Aus welcher Quelle stammen denn die VDR-Pakete (Debian-Repos, selbst gebaut, Mischung aus beidem) und welche Plugins nutzt du?

    yaVDR-Dokumentation (Ceterum censeo enchiridia esse lectitanda.)

  • Code
    etc/apt/sources.list
    deb http://raspbian.raspberrypi.org/raspbian/ buster main contrib non-free rpi

    Merkwürdig, nachdem das Problem einige Tage lang bestand, läuft das Ding heute ganz normal.

    Könnte aus sein, dass es gar nichts mit dem Update zu tun hat, sondern dass sich das Lebensende der SD-Karte ankündigt?

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!