[DUSTBIN] Timeout at shutdown/poweroff/reboot

[DebbyIan]

I was wondering if anyone knows about the timeout that occurs when shutting down the system? It happens after X has exited. I'm not entirely sure I could be wrong, but is it related to a LA/Network tmeout?

Does anyone know what this timeout is because it is around 30 seconds and very irritating when powering off etc..?

[Head_on_a_Stick]

Check the journal...

[bw123]

I was wondering if anyone knows about the timeout that occurs when shutting down the system? It happens after X has exited. I'm not entirely sure I could be wrong, but is it related to a LA/Network tmeout?

Does anyone know what this timeout is because it is around 30 seconds and very irritating when powering off etc..?

I agree, it is extremely irritating. I don't know what LA means, but yeah it's probably "a stop job is running..." for networkmanager. I don't get this stuff when using fluxbox and wpa_cli for wifi. I have noticed if I bring the wifi down before shutting down it doesn't happen, but some other stop job can pop up for something else.

It's especially aggravating when you are experimenting and get a zombie or a hung task. There is a way to lower the timeout but I haven't bothered I just try not to reboot, going on five days now, pretty good huh?

[DebbyIan]

LAN = Local Area Network

Sometimes I get a deauthenticating from network message but I'm not using network manager either. What is the timeout you had in mind?

[Head_on_a_Stick]

OK, I'll try again...

Code: Select all

# mkdir -p /var/log/journal
# reboot
# journalctl -b -1
# rm -r /var/log/journal

Set the timeout in /etc/systemd/system.conf

*puts away feeding spoon*

[DebbyIan]

Don't post useless info! Go home.

[GarryRicketson]

Did you try what was suggested, ? Maybe post the output, of :

Code: Select all

journalctl -b -1

You should see information that you need to do this:

Head_on_a_Stick » Set the timeout in /etc/systemd/system.conf

If you don't understand the solution, or it did not work , instead of getting
mad and complaining:

Don't post useless info! Go home.

It would have been better to say,
"OK, thanks, but please don't put the feeding spoon away, it did not work"
(or I don't understand and need more help) (if it did not work, at least give some information, as to what errors there were or what happened).
I probably shouldn't even do this for you, but your remark and request has
probably just eliminated any chance of you getting more help for one of the
most experienced and helpful members, also Head On A Stick, is part of the
forum staff,...so any way your on your own now, here is the stove, and over there is the refrigerator, if you look around the pots and pans are there also,..
so no more spoon feeding, figure it out your self if you are hungry.
What is the timeout thing when Debian shutsdown
And
On Debian, how to Set the timeout in /etc/systemd/system.conf

P.S Maybe practice what you preach :

Post by DebbyIan » 2017-12-07 17:01
Don't post useless info! Go home.

And please don't tell me my post is not use full, nor to go home, I am at home.
Everything I post is use full, the problem is some people do not know how to use it nor the search engines either, etc.
Hint , a apology can go a long ways.

[ticojohn]

In my limited experience, and even more limited knowledge base, I have examined the logs (journalctl) after having similar timeout issues. It appears to me, and again I am but an egg, that there is some kind of "race" condition where some process is getting released from dbus while some other process is still expecting to use the released process. Again, that is just a conjecture on my part.

So, what did I do about? First I set the timeout to 10 seconds which was of course helpful but did nothing to eliminate the problem. Then I changed from using gdm to lightdm as the display manager. Many fewer instances of the timeout issue. Then, on a whim, I updated the kernel to a more recent version (this is on Jessie, I was using kernel 3.16 and updated to 4.9), and have not seen any of the timeout issues since.

I know that none of this is a cure but might give some smart person a clue as to what might be going on.

[None1975]

I know that none of this is a cure but might give some smart person a clue as to what might be going on.

Display managers is a evil. Use startx.

[ticojohn]

Display managers is a evil. Use startx.

I think it is a bit of a stretch to call them evil. Quirky perhaps, but evil would imply some intelligent malevolence. Of course the designers of the display managers might be evil, but I seriously doubt it.

[Bulkley]

Use startx.

I use sx.

[GarryRicketson]

I just use the keyboard and the terminal, The desktop tray makes a nice perch though
Waiting 30 seconds for it to shut down is no big deal.

Display managers is a evil. Use startx

Ok, yes that worked, it started just fine,... but when I typed
'stopx', it did not stop, what do I do now ?, I don't mind waiting 30 seconds,
but I been here waiting 2 days now, Garry is out of town, How do I shut this
thing down ?

P.S. I am getting hungry, can anybody spoon feed me ?

[ticojohn]

P.S. I am getting hungry, can anybody spoon feed me ?

See, parrots are pretty smart after all!

[None1975]

but when I typed
'stopx', it did not stop, what do I do now ?, I don't mind waiting 30 seconds,

Code: Select all

pkill X

is your firiend Also, many wm (if you use any) provides mechanism to cleanly exit without killing your X server...

[None1975]

I use sx.

It is shell script?