Re: A stop job is running for Entropy Gatherer Daemon? Really?

[Gordon Messmer]

On 5/5/19 6:07 AM, Tom Horsley wrote:

But the service knows that. Why isn't there a way to tell
systemd that in the .service file?



There's no use case for it.  rngd is expected to terminate (more or 
less) immediately after it gets sigterm.  If there were another 
directive to ignore shutdown status (as there is already a timeout 
setting), no one would have put that one in rngd's service file either.


systemd is doing what it was designed to do.  It's operating correctly.  
Why is it more important to you to look for a reason to blame systemd 
than it is to simply correct the error in rngd? Does blaming systemd 
make a better community?

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: A stop job is running for Entropy Gatherer Daemon? Really?

[Sam Varshavchik]

Tom Horsley writes:


On Sat, 4 May 2019 22:12:11 -0600
Joe Zeff wrote:

> Because systemd has no way of knowing what the service is doing or that
> it's safe to kill it without waiting for it to finish.

But the service knows that. Why isn't there a way to tell
systemd that in the .service file?


Yes, there is, the TimeouStopSec setting in [service], see systemd.service  
man page.


But you have to know where it's buried in systemd's documentation. But this  
goes towards the mainstream mindset: chuck a start command into the service  
file, and forget about it. You're done. Systemd Knows Best.





pgpuOVUCnyps7.pgp
Description: PGP signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: A stop job is running for Entropy Gatherer Daemon? Really?

[Tom Horsley]

On Sat, 4 May 2019 22:12:11 -0600
Joe Zeff wrote:

> Because systemd has no way of knowing what the service is doing or that 
> it's safe to kill it without waiting for it to finish.

But the service knows that. Why isn't there a way to tell
systemd that in the .service file?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: A stop job is running for Entropy Gatherer Daemon? Really?

[Tim via users]

Allegedly, on or about 4 May 2019, Tom Horsley sent:
> Though a sane person might ask, "Why is it the right thing to wait
> for a service gathering information which will be utterly discarded
> on the reboot anyway?"

Well, much as I hate to defend systemd, *it* doesn't know that *that*
service is one it can kill with impunity.  Only that service would know
whether it was okay to do so.

-- 
[tim@localhost ~]$ uname -rsvp
Linux 4.16.11-100.fc26.x86_64 #1 SMP Tue May 22 20:02:12 UTC 2018 x86_64

Boilerplate:  All mail to my mailbox is automatically deleted.
There is no point trying to privately email me, I only get to see
the messages posted to the mailing list.

Hooray!  I finally finished typing this email.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: A stop job is running for Entropy Gatherer Daemon? Really?

[Joe Zeff]

On 05/04/2019 08:20 PM, Tom Horsley wrote:

On Sat, 4 May 2019 18:58:32 -0700
Gordon Messmer wrote:


We don't need tortured logic to blame systemd.  It's doing the right
thing.

Though a sane person might ask, "Why is it the right thing to wait
for a service gathering information which will be utterly discarded
on the reboot anyway?"


Because systemd has no way of knowing what the service is doing or that 
it's safe to kill it without waiting for it to finish.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: A stop job is running for Entropy Gatherer Daemon? Really?

[Tom Horsley]

On Sat, 4 May 2019 18:58:32 -0700
Gordon Messmer wrote:

> We don't need tortured logic to blame systemd.  It's doing the right 
> thing.

Though a sane person might ask, "Why is it the right thing to wait
for a service gathering information which will be utterly discarded
on the reboot anyway?"
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: A stop job is running for Entropy Gatherer Daemon? Really?

[Gordon Messmer]

On 5/4/19 4:13 PM, Sam Varshavchik wrote:
In the good-old days, when integrating some new gizmo like rngd, by 
the nature of the beast you'll always check into how it works and make 
a minimal effort to learn its basics. Basic due diligence. From the 
linked bugzilla bug, it seems that rngd was coded to ignore signals.



I don't think the conversation on that bug supports that conclusion.  
This looks like it's simply a bug in rngd that causes an intermittent 
failure to terminate.  (If it intentionally ignored signals, the failure 
would not be intermittent.)


We don't need tortured logic to blame systemd.  It's doing the right 
thing.  There is a bug in rngd, and systemd is exposing that bug so that 
it can be fixed.  That's how software should work. "Errors should never 
pass silently." (Zen of Python #10.  Hello from Pycon!)

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: A stop job is running for Entropy Gatherer Daemon? Really?

[Sam Varshavchik]

Samuel Sieb writes:


On 5/4/19 9:32 AM, Sam Varshavchik wrote:


How can you possibly get stopping a piddly daemon, like rngd, wrong? Who  
knows. It's brain damage.


As usual, it is not a systemd problem, unless you consider that trying to do  
a clean shutdown is brain damage.  The rngd process gets stuck sometimes  
(see the above mentioned bug) and systemd waits nicely for it to stop, but  
finally gives up and force kills it.


In the good-old days, when integrating some new gizmo like rngd, by the  
nature of the beast you'll always check into how it works and make a minimal  
effort to learn its basics. Basic due diligence. From the linked bugzilla  
bug, it seems that rngd was coded to ignore signals. So, having learned that  
factoid, one would code the initscript to sigkill it, with no other options  
available. One would even likely run it, and test it, to be sure it works.  
Or maybe even not wasting time trying to stop it. The system's coming down.  
Who cares.


But now, the mindset is completely different, and that's what I am  
describing as the brain damage. All you need is a service file with an  
ExecStart, to launch the thing. That's it. Nothing else needs to be done.  
Don't worry about it. Systemd Knows Best. It'll take care of stopping it.  
You don't need to do due diligence any more. Just trust the systemd to stop  
it. And that's how you end up with 90 second shutdown delays.






pgp1YoNYOKDMg.pgp
Description: PGP signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: A stop job is running for Entropy Gatherer Daemon? Really?

[Samuel Sieb]

On 5/4/19 9:32 AM, Sam Varshavchik wrote:
I just wait 90 seconds, in those instances, and write it off as yet 
another systemd brain damage.


According to systemd.service man page, TimeoutStopSec sets this timeout. 
So you can add that to rngd.service, I suppose. Or, if you want to bring 
out the big hammer, set DefaultTimeoutStopSec in 
/etc/systemd/system.conf, effectively changing the default timeout for 
everything.


How can you possibly get stopping a piddly daemon, like rngd, wrong? Who 
knows. It's brain damage.


As usual, it is not a systemd problem, unless you consider that trying 
to do a clean shutdown is brain damage.  The rngd process gets stuck 
sometimes (see the above mentioned bug) and systemd waits nicely for it 
to stop, but finally gives up and force kills it.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: A stop job is running for Entropy Gatherer Daemon? Really?

[Tom Horsley]

On Sat, 04 May 2019 12:32:59 -0400
Sam Varshavchik wrote:

> Maybe 1 in every 20 if my reboots gets held up for "stopping user processes".

That happens to me so often that I built an entire
big hammer from scratch just to hit the system with when I
reboot:

https://tomhorsley.com/game/punch.html

I've added more stuff to my pre-reboot script documented
there from time to time. Apparently apache can imagine
it is streaming to my tablet or something and won't shut
down, so I now kill off apache in there before rebooting.
Perhaps I'll need to add a kill -9 of rngd as well...
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: A stop job is running for Entropy Gatherer Daemon? Really?

[Sam Varshavchik]

Tom Horsley writes:


I'm frequently rebooting my new fedora 30 install as
I test things, and on one reboot I got the entire
boot process held up by a stop job for rngd.service.

I'm rebooting for God's sake. Why do you need to stop
the reboot process to wait till you've gathered
enough entropy which will be thrown away immediately
on reboot?

Can a individual service file be configured to exit
immediately on reboot?


There's a default 90 second timeout on stopping a service, before it gets  
forcefully stopped.


Maybe 1 in every 20 if my reboots gets held up for "stopping user processes".

Apparently, I am asked to believe that selecting "Reboot" from the desktop  
does not always stop every user process, for some reason, even though X is  
completely killed, as well as everything that should be started from it, or  
from the user login.


I just wait 90 seconds, in those instances, and write it off as yet another  
systemd brain damage.


According to systemd.service man page, TimeoutStopSec sets this timeout. So  
you can add that to rngd.service, I suppose. Or, if you want to bring out  
the big hammer, set DefaultTimeoutStopSec in /etc/systemd/system.conf,  
effectively changing the default timeout for everything.


How can you possibly get stopping a piddly daemon, like rngd, wrong? Who  
knows. It's brain damage.





pgpJgvFv3h3HA.pgp
Description: PGP signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: A stop job is running for Entropy Gatherer Daemon? Really?

[Tom Horsley]

I guess this is probably this bug:

https://bugzilla.redhat.com/show_bug.cgi?id=1690364
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

A stop job is running for Entropy Gatherer Daemon? Really?

[Tom Horsley]

I'm frequently rebooting my new fedora 30 install as
I test things, and on one reboot I got the entire
boot process held up by a stop job for rngd.service.

I'm rebooting for God's sake. Why do you need to stop
the reboot process to wait till you've gathered
enough entropy which will be thrown away immediately
on reboot?

Can a individual service file be configured to exit
immediately on reboot?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: can't shutdown (a stop job is running...)

[Tom Horsley]

On Thu, 3 Nov 2016 17:10:12 +0800
Ed Greshko wrote:

> Being that it is a "common issue" are you aware of any bugzilla open on this?

Just search bugzilla for "a stop job is running":

https://bugzilla.redhat.com/show_bug.cgi?id=1337526
https://bugzilla.redhat.com/show_bug.cgi?id=1307260

But they never fix it, they just wait till the release hits
EOL and let bugzilla automatically close it:

https://bugzilla.redhat.com/show_bug.cgi?id=1088619
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: can't shutdown (a stop job is running...)

[Ed Greshko]

On 11/03/16 14:50, Samuel Sieb wrote:
> On 11/01/2016 07:31 AM, Ed Greshko wrote:
>> On 11/01/16 22:26, Ed Greshko wrote:
>>> On 11/01/16 22:21, Ed Greshko wrote:
>>>> On 11/01/16 18:49, Neal Becker wrote:
>>>>> For quite some time now, when I try to reboot (from kde) the shutdown gets
>>>>> stuck saying "a stop job is running for ...".  I just hold the power 
>>>>> button.
>>>>> Any ideas?
>>>> Next time, before you attempt to reboot, issue the "jobs" command in a 
>>>> terminal
>>>> window and
>>>> it should tell you what job is stopped.
>>>>
>>> Humm.  Sadly, the jobs command will only list jobs which have been 
>>> stopped/owned by
>>> the current shell.  :-(
>>>
>> But, you can use "ps -aux" and find the process with a STAT of "T".
>>
> It's not about stopped jobs, it's about systemd trying to stop some 
> process/service. 
> This has unfortunately been a common issue.  Usually it will time out after 
> 1.5 minutes
> or maybe more, but it should eventually time out and finish the shutdown.  Or 
> try
> CTRL-ALT-DEL, that sometimes makes it continue as well.

Thanks.  I must have mis-read and/or mis-understood what was being said

Being that it is a "common issue" are you aware of any bugzilla open on this?  
I've not
seen this sort of issue on any of my systems other than one which happens only 
when there
was an NFS mount over a WiFi connection and that has been fixed about a year 
ago.

-- 
You're Welcome Zachary Quinto
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: can't shutdown (a stop job is running...)

[Samuel Sieb]

On 11/01/2016 07:31 AM, Ed Greshko wrote:

On 11/01/16 22:26, Ed Greshko wrote:

On 11/01/16 22:21, Ed Greshko wrote:

On 11/01/16 18:49, Neal Becker wrote:

For quite some time now, when I try to reboot (from kde) the shutdown gets
stuck saying "a stop job is running for ...".  I just hold the power button.
Any ideas?

Next time, before you attempt to reboot, issue the "jobs" command in a terminal 
window and
it should tell you what job is stopped.


Humm.  Sadly, the jobs command will only list jobs which have been 
stopped/owned by
the current shell.  :-(


But, you can use "ps -aux" and find the process with a STAT of "T".

It's not about stopped jobs, it's about systemd trying to stop some 
process/service.  This has unfortunately been a common issue.  Usually 
it will time out after 1.5 minutes or maybe more, but it should 
eventually time out and finish the shutdown.  Or try CTRL-ALT-DEL, that 
sometimes makes it continue as well.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: can't shutdown (a stop job is running...)

[Go Canes]

FWIW, I have seen the same problem, and use the same solution.  It is late
in the shutdown process, so no other VTs are available to use for
troubleshooting.

On Tue, Nov 1, 2016 at 11:57 AM, Neal Becker <ndbeck...@gmail.com> wrote:

> I don't know how to find out what job it is.  I'm pretty sure at this point
> you can't switch VTs, but next time it happens I'll try
>
> fred roller wrote:
>
> > Is it consistently the same job?  If so, what is the job so we can
> > investigate to program.
> >
> > On Tue, Nov 1, 2016 at 7:21 AM, Neal Becker <ndbeck...@gmail.com> wrote:
> >
> >> Tibor Attila Anca wrote:
> >>
> >> > Do you have any mounted network drives?
> >> >
> >> > Am 01.11.2016 um 11:49 schrieb Neal Becker:
> >> >> For quite some time now, when I try to reboot (from kde) the shutdown
> >> >> gets
> >> >> stuck saying "a stop job is running for ...".  I just hold the power
> >> >> button. Any ideas?
> >> >> ___
> >> >> users mailing list -- users@lists.fedoraproject.org
> >> >> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> >> >>
> >> >
> >>
> >> No, nothing mounted on any network.
> >> ___
> >> users mailing list -- users@lists.fedoraproject.org
> >> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> >>
>
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: can't shutdown (a stop job is running...)

[Neal Becker]

I don't know how to find out what job it is.  I'm pretty sure at this point 
you can't switch VTs, but next time it happens I'll try

fred roller wrote:

> Is it consistently the same job?  If so, what is the job so we can
> investigate to program.
> 
> On Tue, Nov 1, 2016 at 7:21 AM, Neal Becker <ndbeck...@gmail.com> wrote:
> 
>> Tibor Attila Anca wrote:
>>
>> > Do you have any mounted network drives?
>> >
>> > Am 01.11.2016 um 11:49 schrieb Neal Becker:
>> >> For quite some time now, when I try to reboot (from kde) the shutdown
>> >> gets
>> >> stuck saying "a stop job is running for ...".  I just hold the power
>> >> button. Any ideas?
>> >> ___
>> >> users mailing list -- users@lists.fedoraproject.org
>> >> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>> >>
>> >
>>
>> No, nothing mounted on any network.
>> ___
>> users mailing list -- users@lists.fedoraproject.org
>> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>>

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: can't shutdown (a stop job is running...)

[Ed Greshko]

On 11/01/16 22:26, Ed Greshko wrote:
>
> On 11/01/16 22:21, Ed Greshko wrote:
>> On 11/01/16 18:49, Neal Becker wrote:
>>> For quite some time now, when I try to reboot (from kde) the shutdown gets 
>>> stuck saying "a stop job is running for ...".  I just hold the power 
>>> button.  
>>> Any ideas?
>> Next time, before you attempt to reboot, issue the "jobs" command in a 
>> terminal window and
>> it should tell you what job is stopped.
>>
> Humm.  Sadly, the jobs command will only list jobs which have been 
> stopped/owned by
> the current shell.  :-(
>

But, you can use "ps -aux" and find the process with a STAT of "T".

-- 
You're Welcome Zachary Quinto
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: can't shutdown (a stop job is running...)

[Ed Greshko]

On 11/01/16 22:21, Ed Greshko wrote:
>
> On 11/01/16 18:49, Neal Becker wrote:
>> For quite some time now, when I try to reboot (from kde) the shutdown gets 
>> stuck saying "a stop job is running for ...".  I just hold the power button. 
>>  
>> Any ideas?
> Next time, before you attempt to reboot, issue the "jobs" command in a 
> terminal window and
> it should tell you what job is stopped.
>

Humm.  Sadly, the jobs command will only list jobs which have been 
stopped/owned by
the current shell.  :-(

-- 
You're Welcome Zachary Quinto
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: can't shutdown (a stop job is running...)

[Ed Greshko]

On 11/01/16 18:49, Neal Becker wrote:
> For quite some time now, when I try to reboot (from kde) the shutdown gets 
> stuck saying "a stop job is running for ...".  I just hold the power button.  
> Any ideas?

Next time, before you attempt to reboot, issue the "jobs" command in a terminal 
window and
it should tell you what job is stopped.

-- 
You're Welcome Zachary Quinto
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: can't shutdown (a stop job is running...)

[Tom Horsley]

On Tue, 01 Nov 2016 06:49:44 -0400
Neal Becker wrote:

> For quite some time now, when I try to reboot (from kde) the shutdown gets 
> stuck saying "a stop job is running for ...".  I just hold the power button.  
> Any ideas?

The power button is probably more drastic than necessary.
Recent versions of systemd will (finally!) respond to
holding down Ctrl-Alt-Del and stop waiting on the thing
that will never finish and go on to run the rest of
the shutdown (minor things like cleanly unmounting
disks :-).

You could also see if any of the things on this
web page help:

http://tomhorsley.com/game/punch.html

(though even with all that fanaticism, I still
sometimes get stuck on a stop job on reboot).
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: can't shutdown (a stop job is running...)

[Tom Horsley]

On Tue, 1 Nov 2016 11:04:54 +
Gary Stainburn wrote:

> shutdown -h now
> 
> This will force whatever is hanging to finish, and shut down your system 
> cleanly

Highly unlikely. Systemd is still gonna wait because it is in charge
of shutdown (and the odds are really good that by the time you
are waiting on a stop job all the vterms have been shutdown and
you won't be able to switch).
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: can't shutdown (a stop job is running...)

[fred roller]

Is it consistently the same job?  If so, what is the job so we can
investigate to program.

On Tue, Nov 1, 2016 at 7:21 AM, Neal Becker <ndbeck...@gmail.com> wrote:

> Tibor Attila Anca wrote:
>
> > Do you have any mounted network drives?
> >
> > Am 01.11.2016 um 11:49 schrieb Neal Becker:
> >> For quite some time now, when I try to reboot (from kde) the shutdown
> >> gets
> >> stuck saying "a stop job is running for ...".  I just hold the power
> >> button. Any ideas?
> >> ___
> >> users mailing list -- users@lists.fedoraproject.org
> >> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> >>
> >
>
> No, nothing mounted on any network.
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: can't shutdown (a stop job is running...)

[Neal Becker]

Tibor Attila Anca wrote:

> Do you have any mounted network drives?
> 
> Am 01.11.2016 um 11:49 schrieb Neal Becker:
>> For quite some time now, when I try to reboot (from kde) the shutdown
>> gets
>> stuck saying "a stop job is running for ...".  I just hold the power
>> button. Any ideas?
>> ___
>> users mailing list -- users@lists.fedoraproject.org
>> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>> 
> 

No, nothing mounted on any network.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: can't shutdown (a stop job is running...)

[Gary Stainburn]

Whatever your problem, DON'T hold down the power button - eventually you will 
stuff your system.

If all else fails, use ++ to swap to a different virtual 
console and then login and type

shutdown -h now

This will force whatever is hanging to finish, and shut down your system 
cleanly

On Tuesday 01 November 2016 10:49:44 Neal Becker wrote:
> For quite some time now, when I try to reboot (from kde) the shutdown gets
> stuck saying "a stop job is running for ...".  I just hold the power
> button. Any ideas?
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org



-- 
Gary Stainburn
Group I.T. Manager
Ringways Garages
http://www.ringways.co.uk 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: can't shutdown (a stop job is running...)

[Tibor Attila Anca]

Do you have any mounted network drives?

Am 01.11.2016 um 11:49 schrieb Neal Becker:
> For quite some time now, when I try to reboot (from kde) the shutdown gets 
> stuck saying "a stop job is running for ...".  I just hold the power button.  
> Any ideas?
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> 

-- 
Anca Tibor Attila

I use OpenSource. It matters.



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

can't shutdown (a stop job is running...)

[Neal Becker]

For quite some time now, when I try to reboot (from kde) the shutdown gets 
stuck saying "a stop job is running for ...".  I just hold the power button.  
Any ideas?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: a stop job is running....

[Chris Murphy]

On Sun, Sep 18, 2016 at 9:58 AM, François Patte
 wrote:
> Le 17/09/2016 22:53, Jon LaBadie a écrit :
>> On Sat, Sep 17, 2016 at 11:34:54AM -0500, Rex Dieter wrote:
>>> Tom Horsley wrote:
>>>
 Because systemd has a gazillion bugs like this
>>>
>>> In cases like this in general, it's not systemd,
>>> but the individual services that have bugs.
>>>
>> Does anyone else tire of hearing
>> "its not systemd, its ..."
>
> I have no idea about this and systemd in general I have four
> computers running under fedora systemd: a desktop under f21, no problem
> of the like; sometimes I get this message: "a start job is running"
> about some partitions installed on two disks in a raid-1 array, that I
> added to the main system after the install. I suspect that it is an fsck
> check but, systemd gives no info on the boot screen about this and I did
> not check in the huge journal...
>
> two laptops under f23 with no problems abo some running jobs (start or stop)
>
> and one laptop under f24 which has these problems. What can we say?
> there are bugs in fc 24 installation of systemd? These stop problems can
> come from the way journalctl write in the /var partition: both partition
> /var and /usr fail to be unmounted at shutdown (they are separate
> partitions from /), is it because journalctl wants to write the logs
> until the last second and the shutdown process wants to umount these two
> partitions too earlier? I am not able to answer and solve these
> problems... But are they systemd problems or a fedora configuration of
> systemd problem?
>
> Who knows?

The problem is there is some process in the user session that isn't
quitting, and systemd doesn't force quit it for 1m30s at which time it
obliterates the user session and everything running in it. You can use
loginctl to list the contents of the user session, but in my
experience I often can't get to a different tty to check on this.

You can try one of two things:

1. Log out, then restart or shutdown. For whatever reason this works
for me maybe 1/2 the time or more.
2. Edit /etc/systemd/logind.conf such that
KillUserProcesses=yes

i.e. remove the # that's currently there by default. This was slated
to be the default for Fedora 25 but the feature has other
consequences, namely it would kill screen and tmux in your user
session also and so there are some unfinished work arounds to make
those things use different scopes or sessions or whatever they're
called.

Just realize with this option set to use, literally everything running
in your user session will get killed off. There is a way to use
systemd-run blah blah you'll have to read about it, to launch tmux in
a different session that doesn't get killed off. I have no idea how
you reconnect to it, if anything else is different other than just
running it that way because I haven't tried it. I have found some
other things like btrfs balance and scrub, which can take hours or
days, will get killed off also and I'm working with upstream Btrfs
folks on a work around for that also, because the real work is done by
the kernel so the operation isn't killed so much as the user process.
So the user process needs to be killable and then able to reconnect to
check status, pause or cancel correctly.

-- 
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: a stop job is running....

[François Patte]

Le 17/09/2016 22:53, Jon LaBadie a écrit :
> On Sat, Sep 17, 2016 at 11:34:54AM -0500, Rex Dieter wrote:
>> Tom Horsley wrote:
>>
>>> Because systemd has a gazillion bugs like this
>>
>> In cases like this in general, it's not systemd,
>> but the individual services that have bugs.
>>
> Does anyone else tire of hearing
> "its not systemd, its ..."

I have no idea about this and systemd in general I have four
computers running under fedora systemd: a desktop under f21, no problem
of the like; sometimes I get this message: "a start job is running"
about some partitions installed on two disks in a raid-1 array, that I
added to the main system after the install. I suspect that it is an fsck
check but, systemd gives no info on the boot screen about this and I did
not check in the huge journal...

two laptops under f23 with no problems abo some running jobs (start or stop)

and one laptop under f24 which has these problems. What can we say?
there are bugs in fc 24 installation of systemd? These stop problems can
come from the way journalctl write in the /var partition: both partition
/var and /usr fail to be unmounted at shutdown (they are separate
partitions from /), is it because journalctl wants to write the logs
until the last second and the shutdown process wants to umount these two
partitions too earlier? I am not able to answer and solve these
problems... But are they systemd problems or a fedora configuration of
systemd problem?

Who knows?

-- 
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 8394 5849
http://www.math-info.univ-paris5.fr/~patte



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: a stop job is running....

[Jon LaBadie]

On Sat, Sep 17, 2016 at 11:34:54AM -0500, Rex Dieter wrote:
> Tom Horsley wrote:
> 
> > Because systemd has a gazillion bugs like this
> 
> In cases like this in general, it's not systemd,
> but the individual services that have bugs.
> 
Does anyone else tire of hearing
"its not systemd, its ..."

jon
-- 
Jon H. LaBadie  jo...@jgcomp.com
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: a stop job is running....

[Tom Horsley]

On Sat, 17 Sep 2016 11:34:54 -0500
Rex Dieter wrote:

> In this particular case, it's the user session that has processes still 
> running, and not quiting after logout.

There were no "user daemons" till systemd invented them.
Every login creates at least a "systemd --user" process
which never goes away. If systemd is going to invent
user daemons, it should also invent a way to make them exit,
but so far the only way that works for me is to force kill
off all the "systemd --user" process trees on the system
before trying to reboot.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: a stop job is running....

[Rex Dieter]

Tom Horsley wrote:

> On Thu, 15 Sep 2016 23:40:19 +0200
> François Patte wrote:
> 
>> Why theses messages?
> 
> Because systemd has a gazillion bugs like this

In cases like this in general, it's not systemd, but the individual services 
that have bugs.

In this particular case, it's the user session that has processes still 
running, and not quiting after logout.  systemd is waiting for them to 
gracefully exit before timeout (120 seconds?) and focefully killing them.

-- Rex
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: a stop job is running....

[Doug H.]

On Thu, 2016-09-15 at 23:40 +0200, François Patte wrote:
> And it takes ages to shutdown
> 
> Why theses messages?
> 
> today I started rc.local compatibility then I stopped it and at
> shutdown, I get the message: "a stop job is running for this
> service" which has been stopped one hour before morever I was
> threatenned with a "no limit" menace!
> 
> Thanks for helping

May just be coincidence, or maybe...

A couple of days ago you were advised to enable "akmods-
shutdown.service". I stopped using that one since I noticed a "stop
job" slowdown with it.

For myself I just keep:

>systemctl -a | grep akmods
 
akmods.service 
   loadedactive   exitedBuilds and install new
kmods from akmod packages

-- 
Doug H.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: a stop job is running....

[P. G.]

Tom Horsley wrote:

> Read about it here: http://tomhorsley.com/game/punch.html

LOL

Actually, I'm pretty happy with systemd h/t To think of the 
hours I used to spend finding out about daemons I never used 
and what they were for, setting them all up to either run or 
not run, etc... Sure, I suppose I learned a lot about the 
system, but I like that systemd just does it all for me and I 
don't need to waste my time on pointless tasks that a modern 
OS should be able to deal with on its own.

My old computers were afflicted with pesky stop job problem, 
too. I'm not sure if it is on my new one? I didn't realize 
that it was only on reboots and not shutdowns: perhaps that's 
why I haven't seen it lately? Or could it be fixed :-O

I dealt with it by making an espresso and then it was timed 
out. They go for 1'30". But, yes, it is frustrating when 
working on something and having to wait for the timeout.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: a stop job is running....

[Sylvia Sánchez]

In my case, when it shows up, it never last more than a couple of
minutes.  But yeah, it's been ages with this problem.


Cheers,
Sylvia
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: a stop job is running....

[Saint Michael]

I filed this bug in Fedora years ago. Unhappy to see it still is not fixed

On Thu, Sep 15, 2016 at 7:42 PM, Terry Polzin  wrote:

> I've noticed an issue trying to shutdown when there are NFS and CIFS mounts
>
> On Thu, Sep 15, 2016 at 5:50 PM, Tom Horsley 
> wrote:
>
>> On Thu, 15 Sep 2016 23:40:19 +0200
>> François Patte wrote:
>>
>> > Why theses messages?
>>
>> Because systemd has a gazillion bugs like this and they
>> are having so much fun introducing yet more bugs that
>> they aren't remotely interested in making what they have
>> actually work correctly.
>>
>> I have noticed that sometimes you can get it to stop
>> waiting by holding down Ctrl-Alt-Del. If it repeats
>> long enough, systemd eventually gets the idea you'd
>> like it to stop.
>> --
>> users mailing list
>> users@lists.fedoraproject.org
>> To unsubscribe or change subscription options:
>> https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
>> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
>> Have a question? Ask away: http://ask.fedoraproject.org
>>
>
>
> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>
>
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: a stop job is running....

[Tom Horsley]

On Thu, 15 Sep 2016 19:42:00 -0400
Terry Polzin wrote:

> I've noticed an issue trying to shutdown when there are NFS and CIFS mounts

I've developed my own reboot alias that kills off all the
things I've been able to track down as sources of hangs
before asking systemd to reboot. It works pretty well,
but the problems always start when something new makes
reboot hang and you have to track it down.

Read about it here: http://tomhorsley.com/game/punch.html
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: a stop job is running....

[Terry Polzin]

I've noticed an issue trying to shutdown when there are NFS and CIFS mounts

On Thu, Sep 15, 2016 at 5:50 PM, Tom Horsley  wrote:

> On Thu, 15 Sep 2016 23:40:19 +0200
> François Patte wrote:
>
> > Why theses messages?
>
> Because systemd has a gazillion bugs like this and they
> are having so much fun introducing yet more bugs that
> they aren't remotely interested in making what they have
> actually work correctly.
>
> I have noticed that sometimes you can get it to stop
> waiting by holding down Ctrl-Alt-Del. If it repeats
> long enough, systemd eventually gets the idea you'd
> like it to stop.
> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: a stop job is running....

[Tom Horsley]

On Thu, 15 Sep 2016 23:40:19 +0200
François Patte wrote:

> Why theses messages?

Because systemd has a gazillion bugs like this and they
are having so much fun introducing yet more bugs that
they aren't remotely interested in making what they have
actually work correctly.

I have noticed that sometimes you can get it to stop
waiting by holding down Ctrl-Alt-Del. If it repeats
long enough, systemd eventually gets the idea you'd
like it to stop.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

a stop job is running....

[François Patte]

And it takes ages to shutdown

Why theses messages?

today I started rc.local compatibility then I stopped it and at
shutdown, I get the message: "a stop job is running for this
service" which has been stopped one hour before morever I was
threatenned with a "no limit" menace!

Thanks for helping

-- 
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 8394 5849
http://www.math-info.univ-paris5.fr/~patte



signature.asc
Description: OpenPGP digital signature
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org