Am 07.04.2021 um 11:14 schrieb Frédéric Mothe:
-- L'unité (unit) avahi-daemon.service a échoué, avec le résultat failed. avril 07 11:05:01 zarbi CRON[16070]: pam_unix(cron:session): session opened for user root by (uid=0) avril 07 11:05:01 zarbi CRON[16071]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) avril 07 11:05:26 zarbi dbus-daemon[598]: [system] Reloaded configuration avril 07 11:05:26 zarbi dbus-daemon[598]: [system] Activating systemd to hand- off: service name='org.freedesktop.Avahi' unit='dbus- org.freedesktop.Avahi.service' requeste avril 07 11:05:26 zarbi dbus-daemon[598]: [system] Activating systemd to hand- off: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.18 avril 07 11:05:51 zarbi dbus-daemon[598]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) avril 07 11:05:51 zarbi dbus-daemon[598]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out (service_start_timeout=25000ms) avril 07 11:05:51 zarbi dbus-daemon[598]: [system] Failed to activate service 'org.freedesktop.PackageKit': timed out (service_start_timeout=25000ms) avril 07 11:05:51 zarbi CRON[16070]: pam_unix(cron:session): session closed for user root
It appears other services fail to start as well with a timeout, like PackageKit. So it's most likely not an Avahi problem but either a dbus or systemd issue (or interaction issue between the two).
Is systemctl still functional, i.e. can you run start/stop/status for arbitrary services?
Do you have anything in your journal regarding systemd? Michael
