You are not logged in.

#1 2018-06-02 13:04:03

julesm
Member
Registered: 2014-07-29
Posts: 70

[Solved] Trying to debug stop job at shutdown/reboot

I have a "stop job" that arises *sometimes* when I try to reboot/shutdown. The message I get is: "a stop job is running for User Manager for UID 1001". The timeout is 2min.

My questions are:

1) Where do I start to look for what's causing this? I don't see any obvious errors in the journal...but I'm sure there's somewhere that references the delay when shutting down/rebooting...

2) How do I change the timeout? I tried setting DefaultTimeoutStopSec from 90s to 10s in /etc/systemd/system.conf. But that didn't do anything - plus the timeout isn't 90s but 2min...

A steer as to how to approach debugging this would be very, very much appreciated!

Cheers,
Jules

Last edited by julesm (2018-06-04 07:19:07)

Offline

#2 2018-06-03 13:17:50

berbae
Member
From: France
Registered: 2007-02-12
Posts: 1,304

Re: [Solved] Trying to debug stop job at shutdown/reboot

For the first point, try to look at remaining user processes after the user logout, in a virtual console under root.

For the second point, you need to change the parameter in /etc/systemd/user.conf because it's the User Manager which doesn't stop due to processes which stay running after user logout.

And give informations about the environment from which you shutdown/reboot, and how you do this.

Offline

#3 2018-06-03 13:45:10

sevendogs
Member
From: Texas
Registered: 2016-01-24
Posts: 220

Re: [Solved] Trying to debug stop job at shutdown/reboot

You can also view the systemd journal in reverse order so shutdown events are at the top:

journalctl -rb -1

"Give a man a truth and he will think for a day. Teach a man to reason and he will think for a lifetime"

Offline

#4 2018-06-04 07:18:53

julesm
Member
Registered: 2014-07-29
Posts: 70

Re: [Solved] Trying to debug stop job at shutdown/reboot

Many thanks for this. Exactly what I needed - a place to start debugging and to understand where that 2min time was getting set.

But wouldn't you know - as soon as I've got this information, the stop job hasn't occurred again. At least I'm armed with what I need for the next it (or another stop job) raises its head.

Since I got what I needed here, I'm going to mark this as solved and will create a new thread if and when with more specifics should it become an issue again.

Again, many thanks!

Offline

#5 2018-06-05 00:09:14

sevendogs
Member
From: Texas
Registered: 2016-01-24
Posts: 220

Re: [Solved] Trying to debug stop job at shutdown/reboot

Debugging is a good idea, as opposed to setting the timeout to a shorter period. Setting the timeout lower just hides the issue and doesn't fix anything. Debian did this to me and I was never able to fix it, but to Debian's credit, it was GDM causing the behavior and not Debian core.


"Give a man a truth and he will think for a day. Teach a man to reason and he will think for a lifetime"

Offline

Board footer

Powered by FluxBB