A stop job is running ......
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? -- Robin K Wellington "Harbour City" New Zealand
On Wed, May 12, 2021 at 11:41 AM Robin Klitscher <robin.klitscher@gmail.com> 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.
On 12/05/2021 11.28, Andrei Borzenkov wrote:
On Wed, May 12, 2021 at 11:41 AM Robin Klitscher <robin.klitscher@gmail.com> 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.
As there is little time for analysis, you (robin) could pipe the output from "top" to a terminal, and have the command ready in advance. top -d 5 -n 40 > top.log But it will show the most busy jobs, maybe not someone that is iddle just waiting. Maybe add "-b". Try first, with "-d 1 -n 2" for faster termination. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 12/05/2021 21:28, Andrei Borzenkov wrote:
On Wed, May 12, 2021 at 11:41 AM Robin Klitscher <robin.klitscher@gmail.com> 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.
Thank you for that. I'd thought as much.
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.
You're saying that the problem lies with something other than the process around systemd-logind that showed up in the log? No matter; the situation is obviously more complicated than it seems at first sight. In that it's an annoyance rather than a showstopper, and is partly resolved by reducing the default timeout from 90 sec to 10 sec, it's simpler just to live with it. Thanks again for your interest. -- Robin K Wellington "Harbour City" New Zealand
On 12/05/2021 10.40, 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.
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? Anyone?
You could try something. Log out from your graphical session first, then order the shutdown from the login display. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 12/05/2021 21:33, Carlos E. R. wrote:
On 12/05/2021 10.40, 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.
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? Anyone?
You could try something.
Log out from your graphical session first, then order the shutdown from the login display.
I'd tried that several times. It didn't help. As I've said to Andrei the problem seems harder to fix than it's worth. I'll just live with it. But thanks anyway. -- Robin K Wellington "Harbour City" New Zealand
Am 12.05.21 um 10:40 schrieb Robin Klitscher:
... 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. ...
If that happens to my computer it was always a drive listed in fstab that for some reason was not accessible for the system on logout. Check for USBs. Peter
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
On 12. 05. 21, 10:40, Robin Klitscher wrote:
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.
I am seeing this too on various systems (15.2 and TW). So definitely worth debugging. Care to open a bug? Have you tried? https://freedesktop.org/wiki/Software/systemd/Debugging/#diagnosingshutdownp... Esp. the "Shutdown Completes Eventually" part. thanks, -- js suse labs
On 13. 05. 21, 8:35, Jiri Slaby wrote:
On 12. 05. 21, 10:40, Robin Klitscher wrote:
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.
I am seeing this too on various systems (15.2 and TW). So definitely worth debugging. Care to open a bug?
Have you tried? https://freedesktop.org/wiki/Software/systemd/Debugging/#diagnosingshutdownp...
Esp. the "Shutdown Completes Eventually" part.
Also you can systemctl start debug-shell.service (Early Debug Shell in the document above) and switch to console 9. The shell should stay open also during shutdown. So you can do e.g. ps aux to see what's stuck...
thanks,--
js suse labs
participants (6)
-
Andrei Borzenkov -
Carlos E. R. -
Jiri Slaby -
Peter McD -
Robin Klitscher -
Simon Becherer