Re: A way to debug machine shutdown

[Lennart Poettering <lennart@xxxxxxxxxxxxxx>]

On Mi, 13.05.20 08:34, darkpenguin (darkpenguin@xxxxxxxxxx) wrote:

> I had trouble trying to paste a 70M text file to fpaste.org; here is the
> gzipped log of the shutdown process instead ('zcat journal.gz | less'
> works where other ways don't).
>
> >> Instead of 90 seconds of "Waiting for session-1.scope ... ", which gives
> >> us next to zero information about the real source of the problem, why
> >> not also mention exactly which process is the problem? Or even
> >> better, a
> >
> > Again, as  mentioned above, we already do that. That's what I wrote
> > above.
>
> What I meant was not exactly this - rather, show the scope status next
> to the "Waiting for Session 1 of user..." message, so that we don't have
> to enable debug, reproduce the problem one more time and then search
> through a 70M log file.
>
> By the way, I could probably do a "systemctl status session-1.scope"
> from the debug shell, but there is no way to have the debug shell during
> shutdown, is there?..

Hmm, I started having a look at the output, but there's just too much
noise going on, something is reloading PID 1 configuration repeatedly
during shutdown. Please figure out what does that and fix that. It's
not how this should work...

Lennart

--
Lennart Poettering, Berlin
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel