Contents
What is systemd-a stop job is running for Session C2 of user?
So as @n.st suggest, I looked at Diagnosing Shutdown Problems again and stored loginctl session-status c2 instead of dmesg, but then there is nothing on the shutdown-log.txt. I replaced loginctl session-status c2 by systemd-cgls and got the following log:
How long is a stop job running for login service?
a stop job is running for login service the initial time is 90 seconds, however, when it close to 90 seconds, it will increase the time. so I have to wait for ever.
When is a stop job running in Ubuntu?
The system would wait 90 seconds every shutdown or restart: A stop job is running for Session c2 of user (1min 30s) Going back to Ubuntu 20.04 default desktop eliminates the problem . Thanks for contributing an answer to Unix & Linux Stack Exchange! Please be sure to answer the question.
How to stop a stop job in systemd?
The solution is to open shell and “shutdown now” then when the machine comes back on then do a “reboot” and the message goes away and future reboots do not hang anymore. I used “sudo shutdown now” and the restart delay is now gone.
What does ” stop job “, as in ” a stop job is running “?
It is (in essence and in theory) a grouping of all of the processes that that user is running as a “login session” somewhere. The job that has been enqueued against it is stop. And it’s probably taking a long time because the systemd people have erroneously conflated session hangup with session shutdown.
What’s the difference between a stop job and session shutdown?
The job that has been enqueued against it is stop. And it’s probably taking a long time because the systemd people have erroneously conflated session hangup with session shutdown. They break the former to get the latter to work, and in response some people alter systemd to break the latter to get the former to work.