On Wed, May 12, 2021 at 11:41 AM Robin Klitscher wrote:

If this has been asked before, I’ve missed it and apologise. It’s certainly been asked elsewhere, though with no clear answer.

Because there is no universal clear answer.

Frequently, but not always, when closing (or rebooting) Leap 15.2, the shutdown stalls for 90 seconds with a message “A stop job is running for Session 2 of user <xxxx>”, together with a register counting down from 1 minute 30 seconds. When the countdown reaches zero the shutdown completes. There’s no other diagnostic information.

...

Assuming the problem does lie somehow with systemd-logind on shutdown, is there something else I can do to fix it?

Find out what process did not stop when the user session stops. Logout, login as a different user (preferably on console to make less noise) and check what processes from your user remain.

Same problem since "years" here, but with tumbleweed. never investigated it. if you find a soluten, would make me happy ;-)) mit freundlichen gruessen simon bechereR Am 12.05.21 um 10:40 schrieb Robin Klitscher:

If this has been asked before, I’ve missed it and apologise. It’s certainly been asked elsewhere, though with no clear answer.

Frequently, but not always, when closing (or rebooting) Leap 15.2, the shutdown stalls for 90 seconds with a message “A stop job is running for Session 2 of user <xxxx>”, together with a register counting down from 1 minute 30 seconds. When the countdown reaches zero the shutdown completes. There’s no other diagnostic information.

I can’t invoke a terminal at that point to establish what’s what. But I have captured what could be useful info with systemctl -b -<x> across boots/shutdowns.

Case 1. Excerpt from journal, “clean” shutdown, no significant delay:

May 09 13:58:02 Corgi systemd[1]: Started Session 2 of user robin.

May 09 15:08:45 Corgi systemd[1]: Stopping Session 2 of user robin.

May 09 15:08:45 Corgi systemd-logind[1108]: Session 2 logged out. Waiting for processes to exit.

May 09 15:08:48 Corgi systemd[1]: Stopped Session 2 of user robin.

Case 2. Excerpt from journal, shutdown with "stop job running" and 90-sec delay:

May 09 15:09:52 Corgi systemd[1]: Started Session 2 of user robin.

May 09 15:15:51 Corgi systemd[1]: Stopping Session 2 of user robin.

May 09 15:15:51 Corgi systemd-logind[1064]: Session 2 logged out. Waiting for processes to exit.

May 09 15:17:21 Corgi systemd[1]: Stopped Session 2 of user robin.

The timestamps of the last two lines in Case 1 show an inconsequential 3 second delay. Those for Case 2 show the full 90 second wait, seeming also to finger systemd-logind as the culprit.

The most common suggestion in other forums is to reduce the default for DefaultTimeoutStopSec in /etc/systemd/system.conf from 90 seconds to 10. This works, but it only addresses the symptom, not the cause.

Assuming the problem does lie somehow with systemd-logind on shutdown, is there something else I can do to fix it? Anyone?

-- B e c h e r e r GmbH Sondermaschinenbau Mauermatten Strasse 22 79183 Waldkirch Germany Tel.: (+49) (0)7681 3134 Fax: (+49) (0)7681 4378 Mail: info@becherer.de Web: www.becherer.de USt-ID-Nr.: DE 814912198 Registergericht: Freiburg HRB 701860 Geschäftsführer: Dipl.-Ing. (FH), EWE Simon H. Becherer Gerichtsstand / Sitz: Waldkirch Es gelten ausschließlich unsere allgemeinen Liefer- und Zahlungsbedingungen / Einkaufsbedingungen: www.becherer.de/AGB