On Mi, 05 aug 20, 18:02:12, Urs Thuermann wrote: > Andrei POPESCU <andreimpopescu@gmail.com> writes: > > > The package 'needrestart' hooks into APT and offers to restart any > > affected services. > > Thx, I didn't know needrestart until today, but learned about in in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770135 and > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823987. > > But regardless of using needrestart or finding grepping them from the > output of lsof, it seems systemd has problems with it or dbus being > restarted. > > The bug is obviously nearly 6 years old but hasn't been fixed yet. #770135 is closed as unreproducible with recent (at the time) systemd, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770135#138 and follow-ups. It's of course possible to reopen the bug if it still exists, though stretch is oldstable now and in LTS mode. Ideally you should try to reproduce it in unstable, or at least buster (maybe a fix would qualify for a stable update). > I have spent much time today restarting dbus, ssh, and/or several > systemd services in different order. Also systemctl daemon-reexec. > Nothing seems to help and it seems systemd bugs again force me to > reboot. But I am currently 700 km away from my server for the next > 1.5 weeks and noone else has access to it. So I'd prefer not to risk > it. On a server it might be possible to simply not use systemd-logind. E.g. (at least on buster) libpam-systemd is only recommended by systemd and openssh-server. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
Attachment:
signature.asc
Description: PGP signature