vdr-addon-lifeguard-ng.service: Failed with result 'timeout'

klausb · Jun 20th 2024

Der vdr-addon-lifeguard-ng.service bricht mit folgenden Fehlermeldungen nach Systemstart ab:

Code

Jun 20 12:43:15 vdr7 systemd[1]: vdr-addon-lifeguard-ng.service: start operation timed out. Terminating.
Jun 20 12:43:15 vdr7 lifeguard[682]: Fatal Python error: init_import_size: Failed to import the site module
Jun 20 12:43:15 vdr7 lifeguard[682]: Python runtime state: initialized
Jun 20 12:43:16 vdr7 lifeguard[682]: Traceback (most recent call last):
Jun 20 12:43:16 vdr7 lifeguard[682]:   File "/usr/lib/python3.8/site.py", line 79, in <module>
Jun 20 12:43:16 vdr7 lifeguard[682]:     import os
Jun 20 12:43:16 vdr7 lifeguard[682]:   File "<frozen importlib._bootstrap>", line 991, in _find_and_load
Jun 20 12:43:16 vdr7 lifeguard[682]:   File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
Jun 20 12:43:16 vdr7 lifeguard[682]:   File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
Jun 20 12:43:16 vdr7 lifeguard[682]:   File "<frozen importlib._bootstrap_external>", line 844, in exec_module
Jun 20 12:43:16 vdr7 lifeguard[682]:   File "<frozen importlib._bootstrap_external>", line 939, in get_code
Jun 20 12:43:16 vdr7 lifeguard[682]:   File "<frozen importlib._bootstrap_external>", line 1038, in get_data
Jun 20 12:43:16 vdr7 lifeguard[682]: KeyboardInterrupt
Jun 20 12:43:16 vdr7 systemd[1]: vdr-addon-lifeguard-ng.service: Main process exited, code=exited, status=1/FAILURE
Jun 20 12:43:16 vdr7 systemd[1]: vdr-addon-lifeguard-ng.service: Failed with result 'timeout'.
Jun 20 12:43:16 vdr7 systemd[1]: Failed to start lifeguard for system services.
Jun

Display More

System:

NAME="Ubuntu" / VERSION="20.04.6 LTS (Focal Fossa)"
Standard ppa's:
- http://ppa.launchpad.net/yavdr/experimental-vdr/ubuntu focal main
- http://ppa.launchpad.net/yavdr/experimental-main/ubuntu focal main
- http://ppa.launchpad.net/yavdr/experimental-kodi/ubuntu focal main
vdr-addon-lifeguard-ng 0.0.5-2yavdr0~focal
VDR version 2.4.8

Habe den service vorerst mal deaktiviert. Wo sollte ich zum Debug suchen?

seahawk1986 · Jun 20th 2024

Da ist irgendetwas mit deiner Python3-Installation nicht in Ordnung, wenn er beim import es os-Moduls scheitert.

Gibt es das Problem auch, wenn du den Python3-Interpreter aufrufst und das von Hand importierst?

Code

python3
>>> import os

Falls es da hängt: klappt es, wenn du Python verbietest externe Module zu nutzen?

Code

python3 -S
>>> import os

Dann könntest du mal schauen, ob es da noch andere stat.py Dateien auf dem System gibt - auf meiner Ubuntu 20.04 Installation tritt das Problem nicht auf und da sieht es so aus:

Code

$ sudo find / -name "stat.py" 2>/dev/null
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/21.08/fcf3dbb56c117835216058acfa99ae280d713029f8d674e1b56e019a20ed082d/files/lib/python3.9/stat.py
/usr/lib/python2.7/stat.py
/usr/lib/python3/dist-packages/ansible/modules/files/stat.py
/usr/lib/python3.8/stat.py

klausb · Jun 20th 2024

Quote from seahawk1986

Gibt es das Problem auch, wenn du den Python3-Interpreter aufrufst und das von Hand importierst?

Kein Problem

Code

root@vdr7:~# python3
Python 3.8.10 (default, Nov 22 2023, 10:22:35)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import os
>>>

Quote from seahawk1986

Dann könntest du mal schauen, ob es da noch andere stat.py Dateien auf dem System gibt

Code

root@vdr7:~# find / -name "stat.py" 2>/dev/null
/usr/lib/python3/dist-packages/ansible/modules/files/stat.py
/usr/lib/python3.8/stat.py
/usr/lib/python2.7/stat.py
/mnt/vdr2/usr/lib/python3.4/stat.py
/mnt/vdr2/usr/lib/python2.7/stat.py

Auch nichts ungewöhnliches. Die /mnt/vdr2/... ist die root des vorherigens yaVDR 0.6 Systems und sollte wohl nicht stören oder?

Was bedeutet denn "frozen"?

seahawk1986 · Jun 21st 2024

Ups, das sollte site.py heißen -

Code

$ sudo find / -name "site.py" 2>/dev/null
[sudo] Passwort für alexander:
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/21.08/fcf3dbb56c117835216058acfa99ae280d713029f8d674e1b56e019a20ed082d/files/lib/python3.9/site.py
/usr/lib/python2.7/site.py
/usr/lib/python3.8/site.py

Quote from klausb

Was bedeutet denn "frozen"?

Soweit ich weiß sind Frozen Modules speziell vorbereitete, eingebettete Python-Module.

klausb · Jun 21st 2024

Also auch nichts doppeltes:

Code

klaus@vdr7:~$ sudo find / -name "site.py" 2>/dev/null
[sudo] Passwort für klaus:
/usr/lib/python3.8/site.py
/usr/lib/python2.7/site.py
/mnt/vdr2/usr/lib/python3.4/site.py
/mnt/vdr2/usr/lib/python2.7/site.py

Habe ja gestern den Service deaktiviert. Aktiviere ihn jetzt und starte noch mal neu.

Code

Jun 21 18:37:34 vdr7 systemd[1]: Starting lifeguard for system services...
Jun 21 18:37:35 vdr7 systemd[1]: Started lifeguard for system services.
Jun 21 18:40:57 vdr7 systemd[1]: Starting lifeguard for system services...
Jun 21 18:41:00 vdr7 systemd[1]: vdr-addon-lifeguard-ng.service: start operation timed out. Terminating.
Jun 21 18:41:00 vdr7 lifeguard[675]: Fatal Python error: init_sys_streams: can't initialize sys standard streams
Jun 21 18:41:00 vdr7 lifeguard[675]: Python runtime state: core initialized
Jun 21 18:41:00 vdr7 lifeguard[675]: Traceback (most recent call last):
Jun 21 18:41:00 vdr7 lifeguard[675]:   File "<frozen importlib._bootstrap>", line 991, in _find_and_load
Jun 21 18:41:01 vdr7 lifeguard[675]:   File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
Jun 21 18:41:01 vdr7 lifeguard[675]:   File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
Jun 21 18:41:01 vdr7 lifeguard[675]:   File "<frozen importlib._bootstrap_external>", line 844, in exec_module
Jun 21 18:41:01 vdr7 lifeguard[675]:   File "<frozen importlib._bootstrap_external>", line 939, in get_code
Jun 21 18:41:01 vdr7 lifeguard[675]:   File "<frozen importlib._bootstrap_external>", line 1038, in get_data
Jun 21 18:41:01 vdr7 lifeguard[675]: KeyboardInterrupt
Jun 21 18:41:01 vdr7 systemd[1]: vdr-addon-lifeguard-ng.service: Main process exited, code=exited, status=1/FAILURE
Jun 21 18:41:01 vdr7 systemd[1]: vdr-addon-lifeguard-ng.service: Failed with result 'timeout'.
Jun 21 18:41:01 vdr7 systemd[1]: Failed to start lifeguard for system services.

Display More

Klappt nicht. ABER: Manuell bei lfd. System:

Code

klaus@vdr7:~$ sudo systemctl start vdr-addon-lifeguard-ng
[sudo] Passwort für klaus:
klaus@vdr7:~$ sudo systemctl status vdr-addon-lifeguard-ng
● vdr-addon-lifeguard-ng.service - lifeguard for system services
     Loaded: loaded (/lib/systemd/system/vdr-addon-lifeguard-ng.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2024-06-21 18:45:29 CEST; 7s ago
   Main PID: 1343 (lifeguard)
      Tasks: 1 (limit: 1948)
     Memory: 9.4M
     CGroup: /system.slice/vdr-addon-lifeguard-ng.service
             └─1343 /usr/bin/python3 /usr/bin/lifeguard

Jun 21 18:45:28 vdr7 systemd[1]: Starting lifeguard for system services...
Jun 21 18:45:29 vdr7 systemd[1]: Started lifeguard for system services.

Display More

seahawk1986 · Jun 21st 2024

Irgendwelche Besonderheiten bei der Aufteilung der ersten Verzeichnisebene auf verschiedene Partitionen? Was sagt mount?

klausb · Jun 21st 2024

Quote from seahawk1986

Was sagt mount?

An sich nichts ungewöhnliches. Hier mal die verschiedenen Sichtweisen:

Code

klaus@vdr7:~$ cat /etc/fstab
# /etc/fstab: static file system information.

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sdd6 during installation
UUID=acd2cca1-3034-4d68-9712-6ea86abde214 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sdd5 during installation
UUID=99c56cff-3764-4d14-bc4f-1eaef4ca06ab none            swap    sw              0       0

# srv
UUID="3009e6ae-cb23-4a53-a1cd-17006f8f3dbb" /srv ext4 errors=remount-ro 0 2

# vdr2 root filesystem
UUID="b1ae37a1-cdfa-4f7f-be0a-5da2148aa386" /mnt/vdr2 ext4 errors=remount-ro 0 3
/var/lib/vdr /home/vdr none bind 0 0

Display More

Code

klaus@vdr7:~$ df -h
Dateisystem    Größe Benutzt Verf. Verw% Eingehängt auf
udev            812M       0  812M    0% /dev
tmpfs           172M    2,7M  170M    2% /run
/dev/sda6       139G    6,4G  126G    5% /
tmpfs           860M       0  860M    0% /dev/shm
tmpfs           5,0M    4,0K  5,0M    1% /run/lock
tmpfs           860M       0  860M    0% /sys/fs/cgroup
/dev/sda1       151G    3,8G  140G    3% /mnt/vdr2
/dev/sdc1       1,8T    134G  1,6T    8% /srv
tmpfs           172M    4,0K  172M    1% /run/user/666
tmpfs           172M    4,0K  172M    1% /run/user/1000

klaus@vdr7:~$ swapon
NAME      TYPE      SIZE USED PRIO
/dev/sda5 partition 1,8G   0B   -2

Display More

Code

klaus@vdr7:~$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,noexec,relatime,size=831348k,nr_inodes=207837,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=175976k,mode=755)
/dev/sda6 on / type ext4 (rw,relatime,errors=remount-ro)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=16071)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
/dev/sda6 on /home/vdr type ext4 (rw,relatime,errors=remount-ro)
/dev/sda1 on /mnt/vdr2 type ext4 (rw,relatime,errors=remount-ro)
/dev/sdc1 on /srv type ext4 (rw,relatime,errors=remount-ro)
-hosts on /net type autofs (rw,relatime,fd=6,pgrp=775,timeout=60,minproto=5,maxproto=5,indirect,pipe_ino=26315)
tmpfs on /run/user/666 type tmpfs (rw,nosuid,nodev,relatime,size=175972k,mode=700,uid=666,gid=666)
/dev/sdb1 on /media/vdr/b4edbc0b-1ef3-4fbe-af09-aeed22d3d6e5 type ext4 (rw,nosuid,nodev,relatime,uhelper=udisks2)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=175972k,mode=700,uid=1000,gid=1000)

Display More

vdr-addon-lifeguard-ng.service: Failed with result 'timeout'

Participate now!

Share

Tags