Comment # 32 on bug 878853 from Oliver M�ssinger

Hi,

after installing this update on our vmware virtual hosts we get systemd core
dumps! Following the /var/log/message log:

2015-02-17T02:24:33.445884+01:00 monsrv systemd[1]: Caught <SEGV>, dumped core
as pid 30432.
2015-02-17T02:24:33.446251+01:00 monsrv systemd[1]: Freezing execution.
2015-02-17T02:24:33.444830+01:00 monsrv kernel: [10420206.631824] systemd[1]:
segfault at 7f3ebd73a9d8 ip 00007f3ebd73a9d8 sp 00007fffe40b69a8 error 15 in
libc-2.18.so[7f3ebd73a000+2000]
2015-02-17T02:30:26.963818+01:00 monsrv /usr/sbin/cron[1625]:
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-17T02:30:26.964212+01:00 monsrv dbus[575]: [system] Failed to activate
service 'org.freedesktop.systemd1': timed out
2015-02-17T02:30:26.964556+01:00 monsrv /usr/sbin/cron[1624]:
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-17T02:15:01.502588+01:00 monsrv systemd-logind[12830]: Failed to store
session release timer fd
2015-02-17T02:30:26.964855+01:00 monsrv systemd-logind[12830]: Failed to start
session scope session-32876.scope: Activation of org.freedesktop.systemd1 timed
out org.freedesktop.DBus.Error.TimedOut
2015-02-17T02:30:51.990166+01:00 monsrv systemd-logind[12830]: Failed to start
session scope session-32877.scope: 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. org.freedesktop.DBus.Error.NoReply
2015-02-17T02:40:26.207648+01:00 monsrv systemd-logind[12830]: Failed to start
session scope session-32878.scope: 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. org.freedesktop.DBus.Error.NoReply
2015-02-17T02:40:26.208416+01:00 monsrv /usr/sbin/cron[8030]:
pam_systemd(crond:session): Failed to create session: Input/output error
2015-02-17T02:45:26.560109+01:00 monsrv systemd-logind[12830]: Failed to start
session scope session-32879.scope: 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. org.freedesktop.DBus.Error.NoReply
2015-02-17T02:45:26.560465+01:00 monsrv /usr/sbin/cron[11081]:
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-17T02:45:26.560969+01:00 monsrv /usr/sbin/cron[11080]:
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-17T02:45:51.568899+01:00 monsrv systemd-logind[12830]: Failed to start
session scope session-32880.scope: Activation of org.freedesktop.systemd1 timed
out org.freedesktop.DBus.Error.TimedOut
2015-02-17T03:00:26.823095+01:00 monsrv /usr/sbin/cron[20726]:
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-17T03:00:26.823395+01:00 monsrv /usr/sbin/cron[20727]:
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-17T03:00:26.823707+01:00 monsrv /usr/sbin/cron[20725]:
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.