How to debug stop job running into time-out?

[Lennart Poettering]

Dear systemd folks,
With Debian Sid/unstable (systemd 239) and GDM 3.30.1, sometimes
powering off the system, it takes two minutes and the message
below is shown on the screen.

A stop job is running for User Manager for UID 1000 (1min 3s / 1 min 59s)

What ways are there to debug this issue. The problem is, it’s
not always reproducible.
Is there a key combination for dumping the necessary information?
Like what process(?) cannot be stopped?

Well, it's the service in question which might be hanging. And in this
case that's the "systemd --user" instance of UID 1000. Most likely
this means some user service doesn't want to shut down, which doesn't
let the systemd --user instance shut down, and hence not the systemd
--system instance either...

Lennart

[Mantas Mikulėnas]

On Wed, Oct 24, 2018 at 6:07 PM Paul Menzel <

Dear systemd folks,
With Debian Sid/unstable (systemd 239) and GDM 3.30.1, sometimes
powering off the system, it takes two minutes and the message
below is shown on the screen.

A stop job is running for User Manager for UID 1000 (1min 3s / 1 min 59s)

What ways are there to debug this issue. The problem is, it’s
not always reproducible.
Is there a key combination for dumping the necessary information?
Like what process(?) cannot be stopped?

My method for that is:
1. enable debug-shell.service;
2. repeat reboot/shutdown until reproduced;
3. Alt+F9 and try to type `sudo -u '#1000' XDG_RUNTIME_DIR='/run/user/1000'
systemctl --user list-jobs` through the message