UbuntuThis forum is for the discussion of Ubuntu Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am not sure if this is Ubuntu specific but I see it most often with Ubuntu. I am running Ubuntu Mate 18.04 on a Raspberry Pi 3B+ When I issue a shutdown from the appropriate notification area icon the system will begin to shut down as expected. The Plymouth (?) shutdown screen appears with the little dots moving in the middle. If I press Esc I will see various messages as the system is shutting down. On occasion I see
Code:
A stop job is running for Session c2 for user ken (20/1:30)
The first number steadily increases until a minute and a half has passed from whenever the job started. At this point the shutdown process continues.
My question is... How do I find out what the "stop job" is so that I can investigate and remediate the problem?
This is systemd stopping a process but not sure it's indicative of something broken. I used to get that message when I ran Debian and Gnome: gdm would hang at shutdown and I would just have to wait the 2 minutes or whatever. The only fix I knew of at the time was to change the timeout value but that masks the issue, if there is actually a problem.
You can run journalctl -b to see the system log entries since the last reboot. Might help troubleshoot if there is actually an issue.
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
Rep:
I, too, see this and am running XFCE on Sid. I think it's a systemd thing as it started when that took over.
<waves arms> welcome to The Future by Poetering...
Yeah, I was never able to find a solution, at least on Debian, then I later gave up on Gnome entirely, for different reasons. I don't remember having an issue with xfce on Debian stable (can't remember name) and using lightdm though - seemed to work just fine.
sudo sed -i 's/\#DefaultTimeoutStartSec=90s/DefaultTimeoutStartSec=10s/' /etc/systemd/system.conf
sudo sed -i 's/\#DefaultTimeoutStopSec=90s/DefaultTimeoutStopSec=10s/' /etc/systemd/system.conf
It will be a good idea to make sure which process was causing the delay so that we can fix it/discard it in the future.
steps:
1. use journalctl -b --list-boots to list boots
2. view logs of last boot: journalctl -b --boot xxxxxx to identify the process killed after 90 secs timeout.
^ yes, that about sums up what others have posted here so far.
Quote:
Originally Posted by taylorkh
Code:
A stop job is running for Session c2 for user ken (20/1:30)
The c2 makes me think that maybe you have started a 2nd session on another tty, and not logged out?
If that is the case I think systemd behaves correctly.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.