Re: [systemd-devel] Debug hanging unit stop on shutdown?
Thanks, I'll check it out. Mantas Mikulėnas schrieb am Fr., 28. Juli 2017, 10:52: > On Thu, Jul 27, 2017 at 10:33 PM, Benno Fünfstück < > benno.fuenfstu...@gmail.com> wrote: > >> Hi, >> >> when shutting down my system, I sometimes get a "Stopping ..." from >> systemd, where it waits 90 seconds before it kills the affected session / >> unit / scope / ... . Is there any way to debug this live, without enabling >> persistent journal and hoping that the journal has enough information? >> >> Ideal would be a way to "interrupt" shutdown in this case and be able to >> correct the mistake / fix the error. >> > > Start debug-shell.service (or boot with "systemd.debug-shell"). During > shutdown, switch to tty9 and use `systemctl list-jobs`, then `systemctl > cancel` to flush all pending jobs. > > -- > Mantas Mikulėnas > ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Debug hanging unit stop on shutdown?
On Thu, Jul 27, 2017 at 10:33 PM, Benno Fünfstück < benno.fuenfstu...@gmail.com> wrote: > Hi, > > when shutting down my system, I sometimes get a "Stopping ..." from > systemd, where it waits 90 seconds before it kills the affected session / > unit / scope / ... . Is there any way to debug this live, without enabling > persistent journal and hoping that the journal has enough information? > > Ideal would be a way to "interrupt" shutdown in this case and be able to > correct the mistake / fix the error. > Start debug-shell.service (or boot with "systemd.debug-shell"). During shutdown, switch to tty9 and use `systemctl list-jobs`, then `systemctl cancel` to flush all pending jobs. -- Mantas Mikulėnas ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Debug hanging unit stop on shutdown?
Hi, when shutting down my system, I sometimes get a "Stopping ..." from systemd, where it waits 90 seconds before it kills the affected session / unit / scope / ... . Is there any way to debug this live, without enabling persistent journal and hoping that the journal has enough information? Ideal would be a way to "interrupt" shutdown in this case and be able to correct the mistake / fix the error. Regards, Benno Fünfstück ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel