On Sun, Oct 08, 2017 at 11:22:00AM +0200, Michael Hirmke wrote: > Hi, > > today systemd crashed on my main server: > > Okt 08 10:06:28 perth systemd[1]: Code should not be reached 'Uh, main > process died at wrong time.' at src/core/service. > c:2701, function service_sigchld_event(). Aborting. > Okt 08 10:06:28 perth systemd[1]: Caught <ABRT>, dumped core as pid > 31706. > Okt 08 10:06:28 perth systemd[1]: Freezing execution. > Okt 08 10:06:28 perth systemd-coredump[31707]: Process 31706 (systemd) > of user 0 dumped core. > > This is a machine running openSuSE Leap 42.3, i.e. > systemd-228-35.1.x86_64. > > What information can I provide in what way to help resolving this > problem? > Or is this already fixed in a later version of systemd?
Upstream is at v235. So the answer is "yes probably", but this issue should be reported to suse leap maintainers. Zbyszek _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel