LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Ubuntu
User Name
Password
Ubuntu This forum is for the discussion of Ubuntu Linux.

Notices


Reply
  Search this Thread
Old 05-03-2019, 01:15 PM   #1
taylorkh
Senior Member
 
Registered: Jul 2006
Location: North Carolina
Distribution: CentOS 6, CentOS 7 (with Mate), Ubuntu 16.04 Mate
Posts: 2,127

Rep: Reputation: 174Reputation: 174
A stop job is running...


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?

TIA,

Ken
 
Old 05-03-2019, 01:34 PM   #2
sevendogsbsd
Senior Member
 
Registered: Sep 2017
Distribution: FreeBSD
Posts: 2,252

Rep: Reputation: 1011Reputation: 1011Reputation: 1011Reputation: 1011Reputation: 1011Reputation: 1011Reputation: 1011Reputation: 1011
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.
 
Old 05-03-2019, 01:40 PM   #3
273
LQ Addict
 
Registered: Dec 2011
Location: UK
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680

Rep: Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373
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...

Last edited by 273; 05-03-2019 at 01:41 PM.
 
Old 05-03-2019, 01:47 PM   #4
sevendogsbsd
Senior Member
 
Registered: Sep 2017
Distribution: FreeBSD
Posts: 2,252

Rep: Reputation: 1011Reputation: 1011Reputation: 1011Reputation: 1011Reputation: 1011Reputation: 1011Reputation: 1011Reputation: 1011
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.
 
Old 05-03-2019, 02:41 PM   #5
taylorkh
Senior Member
 
Registered: Jul 2006
Location: North Carolina
Distribution: CentOS 6, CentOS 7 (with Mate), Ubuntu 16.04 Mate
Posts: 2,127

Original Poster
Rep: Reputation: 174Reputation: 174
Thanks folks,

I guess I really need to do some investigating of the logs. If I start working from the most recent boot and work backwards perhaps.

Ken
 
Old 05-03-2019, 02:51 PM   #6
sevendogsbsd
Senior Member
 
Registered: Sep 2017
Distribution: FreeBSD
Posts: 2,252

Rep: Reputation: 1011Reputation: 1011Reputation: 1011Reputation: 1011Reputation: 1011Reputation: 1011Reputation: 1011Reputation: 1011
There is a way to use journalctl to view the logs in reverse order: newest first, I just can't remember the switch at the moment.
 
Old 05-03-2019, 07:08 PM   #7
verndog
Member
 
Registered: Oct 2007
Posts: 277

Rep: Reputation: 66
I use these two commands for timeouts:
Code:
sudo sed -i 's/\#DefaultTimeoutStartSec=90s/DefaultTimeoutStartSec=10s/' /etc/systemd/system.conf
sudo sed -i 's/\#DefaultTimeoutStopSec=90s/DefaultTimeoutStopSec=10s/' /etc/systemd/system.conf
 
Old 05-03-2019, 08:32 PM   #8
frankbell
LQ Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 19,272
Blog Entries: 28

Rep: Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124
Code:
A stop job is running for Session c2 for user ken (20/1:30)
I got a similar message shutting down a VM of Fedora tonight, and I've seen it other places.

It is not a cause for concern.
 
Old 11-15-2020, 03:19 AM   #9
homyzh
LQ Newbie
 
Registered: Nov 2009
Posts: 1

Rep: Reputation: 0
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.
 
Old 11-16-2020, 01:40 AM   #10
ondoho
LQ Addict
 
Registered: Dec 2013
Posts: 19,872
Blog Entries: 12

Rep: Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053
^ yes, that about sums up what others have posted here so far.
Quote:
Originally Posted by taylorkh View Post
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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
A stop job is running for Plex Luca91 Linux - General 2 08-27-2021 10:31 PM
Debian 9.1 - Very slow network and 'a stop job is running for ifup for en01' darren.williams Linux - Hardware 2 10-09-2017 02:47 AM
linux cron job duplicate job question cpthk Linux - Newbie 4 09-11-2009 08:52 PM
lpr job number -- where does lpr get the job number? conetic Linux - Software 1 02-28-2008 03:38 PM
Can you start a job without getting the job number spit back out? BrianK Linux - General 5 12-13-2007 08:09 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Ubuntu

All times are GMT -5. The time now is 10:21 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration