Hi,
How can I find out why systemd core dumps and requires system reboot
:-( ?
I just did
# systemctl status sockd-1.5.0
Failed to issue method call: 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.
# systemctl status sockd-1.5.0
Failed to get D-Bus connection: Failed to connect to socket
/run/systemd/private: Connection refused
2015-01-01T17:52:01.625495+00:00 opensuse12 systemd[1]: Accepted connection
on private bus.
2015-01-01T17:52:01.626333+00:00 opensuse12 systemd[1]: Running GC...
2015-01-01T17:52:01.627976+00:00 opensuse12 systemd[1]: Got D-Bus request:
org.freedesktop.DBus.Properties.GetAll() on
/org/freedesktop/systemd1/unit/sockd_2d1_2e5_2e0
2015-01-01T17:52:01.636546+00:00 opensuse12 systemd[1]: Assertion
'endswith(path, ".service")' failed at src/core/service.c:1077, function
service_load_sysv_name(). Aborting.
2015-01-01T17:52:01.686714+00:00 opensuse12 systemd[1]: Caught <ABRT>,
dumped core as pid 2925.
2015-01-01T17:52:01.687538+00:00 opensuse12 systemd[1]: Freezing execution.
I am running Opensuse 12.3
# rpm -q -f /sbin/init
systemd-sysvinit-195-13.45.1.x86_64
# systemd --version
systemd 195
suse
+PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ
Thank you
Markus
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
