On Fr, 11.02.22 13:50, Mariusz Tkaczyk (mariusz.tkaczyk@xxxxxxxxxxxxxxx) wrote: > > Otherwise there might simply be another program that explicitly tells > > systemd to shut this stuff down, i.e. some script or so. Turn on debug > > logging (systemd-analyze log-level debug) before shutting down, the > > logs should tell you a thing or two about why the service is stopped. > > > > That is ridiculous when I enabled debug logging by command provided, it > is not killed: A heisenbug. Usually some race then. i.e. the extra debug logging probably slows down relevant processes long enough so that others can catch up that previously couldn't. Lennart -- Lennart Poettering, Berlin