Comment # 2 on bug 918507 from Utto Huber

As Thomas wrote, this really seems to start with a segfault in systemd. This is
our log content:


2015-02-18T08:16:43.892154+01:00 fs1-1 kernel: [404687.140461] systemd[1]:
segfault at a8 ip 000000000047912e sp 00007fffd0db7110 error 4 in
systemd[400000+ed000]
2015-02-18T08:16:44.352680+01:00 fs1-1 systemd[1]: Caught <SEGV>, dumped core
as pid 19512.
2015-02-18T08:16:44.411008+01:00 fs1-1 systemd[1]: Freezing execution.
2015-02-18T08:16:01.955797+01:00 fs1-1 systemd-logind[12034]: message repeated
4 times: [ Failed to store session release timer fd]
2015-02-18T08:18:26.939222+01:00 fs1-1 systemd-logind[12034]: Failed to start
unit user-0.slice: Did not receive a reply. Possible causes include: the remote
application did not send a reply, the message bus security policy blocked the
reply, the reply timeout expired, or the network connection was broken.
2015-02-18T08:18:26.939762+01:00 fs1-1 systemd-logind[12034]: Failed to start
user slice: Did not receive a reply. Possible causes include: the remote
application did not send a reply, the message bus security policy blocked the
reply, the reply timeout expired, or the network connection was broken.
2015-02-18T08:18:26.940061+01:00 fs1-1 /usr/sbin/cron[19515]:
pam_systemd(crond:session): Failed to create session: Did not receive a reply.
Possible causes include: the remote application did not send a reply, the
message bus security policy blocked the reply, the reply timeout expired, or
the network connection was broken.
2015-02-16T23:31:56.333429+01:00 fs1-1 dbus[592]: message repeated 3 times: [
[system] Reloaded configuration]
2015-02-18T08:18:26.940421+01:00 fs1-1 dbus[592]: [system] Failed to activate
service 'org.freedesktop.systemd1': timed out


Does anybody know whether reverting back to systemd 208-23.3 will help? Next
time our servers start misbehaving I'll give it try and give feedback here.

Paul