Package: systemd Version: 44-11+deb7u4 Severity: important Systemd has an assertion failure and was unsuable after the following. Is systemd supposed to re-execute itself after such a failure?
Create with a config file such as: some-service.service [Unit] Description=Some test service [Service] Type=forking ExecStart=/bin/sleep 1000 User=someuser Group=someuser [Install] WantedBy=multi-user.target Start the service and kill it with kill -9 at the right moment while it is starting. The following backtrace could be obtained from the core file. #0 0x00007fc952fac475 in *__GI_raise (sig=<optimized out>, sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x000000000040bea9 in crash (sig=6) at src/main.c:123 #2 <signal handler called> #3 0x00007fc952fac475 in *__GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #4 0x00007fc952faf6f0 in *__GI_abort () at abort.c:92 #5 0x0000000000453729 in log_assert (text=text@entry=0x473651 "s->type == SERVICE_FORKING", file=file@entry=0x4730bb "src/service.c", line=line@entry=2956, func=func@entry=0x475bf0 "service_sigchld_event", format=format@entry=0x49ba00 "Assertion '%s' failed at %s:%u, function %s(). Aborting.") at src/log.c:637 #6 0x0000000000453ca0 in log_assert_failed (text=text@entry=0x473651 "s->type == SERVICE_FORKING", file=file@entry=0x4730bb "src/service.c", line=line@entry=2956, func=func@entry=0x475bf0 "service_sigchld_event") at src/log.c:642 #7 0x0000000000420f31 in service_sigchld_event (u=0x10788b0, pid=2248, code=2, status=9) at src/service.c:2956 #8 0x000000000040cd02 in manager_dispatch_sigchld (m=m@entry=0xfe7a30) at src/manager.c:2145 #9 0x000000000041374f in manager_process_signal_fd (m=<optimized out>) at src/manager.c:2376 #10 process_event (ev=0x7fff4c9149d0, m=0xfe7a30) at src/manager.c:2401 #11 manager_loop (m=0xfe7a30) at src/manager.c:2535 #12 0x0000000000409fc8 in main (argc=<optimized out>, argv=<optimized out>) at src/main.c:1490 -- System Information: Debian Release: 7.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii dpkg 1.16.12 ii initscripts 2.88dsf-41+deb7u1 ii libacl1 2.2.51-8 ii libaudit0 1:1.7.18-1.1 ii libc6 2.13-38+deb7u1 ii libcap2 1:2.22-1.2 ii libcryptsetup4 2:1.4.3-4 ii libdbus-1-3 1.6.8-1+deb7u1 ii libkmod2 9-3 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.3-7.1 ii libselinux1 2.1.9-5 ii libsystemd-daemon0 44-11+deb7u4 ii libsystemd-id128-0 44-11+deb7u4 ii libsystemd-journal0 44-11+deb7u4 ii libsystemd-login0 44-11+deb7u4 ii libudev0 175-7.2 ii libwrap0 7.6.q-24 ii udev 175-7.2 ii util-linux 2.20.1-5.3 Versions of packages systemd recommends: ii libpam-systemd 44-11+deb7u4 Versions of packages systemd suggests: ii python 2.7.3-4+deb7u1 pn python-cairo <none> pn python-dbus <none> pn systemd-gui <none> -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
