You are not logged in.

#1 2015-09-05 09:43:18

wes
Member
Registered: 2011-03-05
Posts: 67

[solved-ish: fixed upstream] systemd 225-1: ungraceful shutdown

Before making noise with bug reports, can anyone confirm that with
systemd-sysvcompat 225, when you run shutdown you will see error messages like

Failed to set wall message, ignoring: Message did not receive a reply (timeout by message bus)
Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Message did not receive a reply (timeout by message bus)

??

The system will reboot, but this is kind of annoying when using ssh, as you
will be instantly disconnected and there's no chance to cancel.

Also, if I instead use "systemctl reboot" over an ssh session, I get this:

g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

followed by instant disconnect.

Thanks in advance.

*EDIT:* update title as this is now patched upstream.

Last edited by wes (2015-09-06 00:02:59)

Offline

#2 2015-09-05 09:48:24

wes
Member
Registered: 2011-03-05
Posts: 67

Re: [solved-ish: fixed upstream] systemd 225-1: ungraceful shutdown

Turns out this thread is already noise :\  Others have reported the bug
already:

https://github.com/systemd/systemd/issues/1120

Offline

#3 2015-09-05 16:53:03

nstgc
Member
Registered: 2014-03-17
Posts: 381

Re: [solved-ish: fixed upstream] systemd 225-1: ungraceful shutdown

Just to confirm, this bug does not affect those of us that aren't specifying a specific time to reboot/halt, correct?

Offline

#4 2015-09-05 20:43:24

wes
Member
Registered: 2011-03-05
Posts: 67

Re: [solved-ish: fixed upstream] systemd 225-1: ungraceful shutdown

nstgc wrote:

...this bug does not affect those of us that aren't specifying a specific time to reboot/halt, correct?

If you do want to shut the machine down immediately, it will still have that
effect.  I've not witnessed any other major consequences, but I've not had
much time... One thing I did notice was that (at least over ssh) some of my
current session's history didn't seem to make it to ~/.bash_history.  Not a
big deal, but perhaps not nothing.

Offline

#5 2015-09-05 23:36:56

nstgc
Member
Registered: 2014-03-17
Posts: 381

Re: [solved-ish: fixed upstream] systemd 225-1: ungraceful shutdown

Thank you.

Offline

#6 2015-09-13 05:12:30

jamespharvey20
Member
Registered: 2015-06-09
Posts: 129

Re: [solved-ish: fixed upstream] systemd 225-1: ungraceful shutdown

wes wrote:
nstgc wrote:

...this bug does not affect those of us that aren't specifying a specific time to reboot/halt, correct?

If you do want to shut the machine down immediately, it will still have that
effect.  I've not witnessed any other major consequences, but I've not had
much time... One thing I did notice was that (at least over ssh) some of my
current session's history didn't seem to make it to ~/.bash_history.  Not a
big deal, but perhaps not nothing.

To avoid the .bash_history issue, use the AUR's systemd-kill-fix package.  It reverts a single upstream commit, that changed a boolean from false to true.  Other than that boolean value, it's pure upstream systemd.

Having the commit eliminates a race condition during shutdown that otherwise could lead to a 90 second or so wait during shutdown.  But, it means many programs are given a SIGKILL (kill -9) upon reboot/shutdown so they can't shutdown gracefully.  This has caused data loss, thankfully the most common is .bash_history.  But, there have been many other situations of more severe data loss.

Most distributions (including Debian, Ubuntu, Fedora, and RedHat) have reverted the commit.  The head upstream developer (poettering) refuses to revert the commit.  No one else seems to have expressed agreement with the decision, but it is his project.  (We can all be thankful he's made systemd, no sarcasm intended here by me.)

My understanding is it is planned that systemd will continue operating the way it does, risking data loss, until kernel 4.3 is out.

You can see much frustration here and here on systemd GitHub, and many tickets on distribution-specific forums about the issue, some of which are linked to on those GitHub pages.

Offline

#7 2015-09-17 02:52:04

wes
Member
Registered: 2011-03-05
Posts: 67

Re: [solved-ish: fixed upstream] systemd 225-1: ungraceful shutdown

@james: thanks!  Did not know about that.  I will likely make use of the package.

Offline

Board footer

Powered by FluxBB