[opensuse] systemd segfault
After the latest glibc update, systemd crashed as I was restarting dbus, systemd-logind etc. The only way to resume normal operation was to restart the system. Has anyone else seen this? -- Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-06-29 16:38:57 +0300, auxsvr@gmail.com wrote:
After the latest glibc update, systemd crashed as I was restarting dbus, systemd-logind etc. The only way to resume normal operation was to restart the system. Has anyone else seen this?
Restarting dbus is not a good idea on a systemd enabled machine. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Mon, 29 Jun 2015 17:03:08 +0200 Marcus Rueckert <darix@opensu.se> пишет:
On 2015-06-29 16:38:57 +0300, auxsvr@gmail.com wrote:
After the latest glibc update, systemd crashed as I was restarting dbus, systemd-logind etc. The only way to resume normal operation was to restart the system. Has anyone else seen this?
Restarting dbus is not a good idea on a systemd enabled machine.
systemd is designed be resilient enough. It supports private socket and all components included with systemd should transparently fall back to this socket (the same actually happens during boot until D-Bus daemon is started). Of course, bugs can slip in. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/29/2015 08:55 AM, Andrei Borzenkov wrote:
It supports private socket and all components included with systemd should transparently fall back to this socket
Precisely what does that actually mean? -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Tue, 30 Jun 2015 10:24:19 -0700 John Andersen <jsamyth@gmail.com> пишет:
On 06/29/2015 08:55 AM, Andrei Borzenkov wrote:
It supports private socket and all components included with systemd should transparently fall back to this socket
Precisely what does that actually mean?
systemd always listens on /run/systemd/private socket and systemd tools try to connect to it. So even if D-Bus daemon is not available or stops, systemd should be accessible to its tools and transparently reconnect to D-Bus when it appears again. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday 29 of June 2015 18:55:36 Andrei Borzenkov wrote:
systemd is designed be resilient enough. It supports private socket and all components included with systemd should transparently fall back to this socket (the same actually happens during boot until D-Bus daemon is started). Of course, bugs can slip in.
This is the second or third time systemd crashes this way since it was introduced in opensuse, so there must be a bug lingering somewhere. I have two core dumps, but they don't seem to be of much use, as the backtrace is invalid. -- Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 29 Jun 2015 15:38, auxsvr wrote:
After the latest glibc update, systemd crashed as I was restarting dbus, systemd-logind etc. The only way to resume normal operation was to restart the system. Has anyone else seen this?
In case the message did not make the way to you: AFTER replacing a CORE library like glibc, do a RESTART asap. Any other doing is provocing dataloss. - Yamaban. -- Sadly stupidy does not exterminate itself. No, most of them are even voted into postions of power. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-06-29 17:06, Yamaban wrote:
On Mon, 29 Jun 2015 15:38, auxsvr wrote:
After the latest glibc update, systemd crashed as I was restarting dbus, systemd-logind etc. The only way to resume normal operation was to restart the system. Has anyone else seen this?
In case the message did not make the way to you:
There was no message whatsoever. YaST finished without a message. I did not need to restart. Exit graphical session, daemon-reexec, then go to init 1, then restart four more things. Still running. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWRc4MACgkQja8UbcUWM1zB9wD/RASKbP21Rxa5GVCW50mogyQp lWQWc6wHtFZDSfqkog8A/A3UrBhnGMki9QyxQ0MNgpg3gNTYVECnAwJi7tt396A6 =8Ngi -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-06-29 17:06, Yamaban wrote:
In case the message did not make the way to you:
AFTER replacing a CORE library like glibc, do a RESTART asap.
Any other doing is provocing dataloss.
There was no message whatsoever. YaST finished without a message. I did not need to restart. Exit graphical session, daemon-reexec, then go to init 1, then restart four more things. Still running. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWRdHgACgkQja8UbcUWM1x0AwEAiQQl/qOxC6KA0tbD6cJSVEPw pR29ry1vZdCmeFWCxncBAIZIFMpG5zKvDzw9nO1BPbFW1/XC55K73DBz0336/Xdw =B42g -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Yamaban composed on 2015-06-29 17:06 (UTC+0200):
auxsvr wrote:
After the latest glibc update, systemd crashed as I was restarting dbus, systemd-logind etc. The only way to resume normal operation was to restart the system. Has anyone else seen this?
In case the message did not make the way to you:
AFTER replacing a CORE library like glibc, do a RESTART asap.
Any other doing is provocing dataloss.
This begs a couple of questions: 1-What does "restart" mean? restart PID 1? reboot? kexec? something else? depends on context? 2-What's the point of kernel patching when "core" components are inducing "restarts"? http://kernelnewbies.org/Linux_4.0#head-9aa7c8499b42911a48c02b24f367bf2bc6db... -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Andrei Borzenkov -
auxsvr＠gmail.com -
Carlos E. R. -
Felix Miata -
John Andersen -
Marcus Rueckert -
Yamaban