Discussion:
systemd core dump
(too old to reply)
Michael Hirmke
2017-10-08 09:22:00 UTC
Permalink
Raw Message
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?

TIA.

Bye.
Michael.
--
Michael Hirmke
Zbigniew Jędrzejewski-Szmek
2017-10-08 11:44:57 UTC
Permalink
Raw Message
Post by Michael Hirmke
Hi,
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
Michael Hirmke
2017-10-08 11:51:00 UTC
Permalink
Raw Message
Hi Zbigniew,
Post by Zbigniew Jędrzejewski-Szmek
Post by Michael Hirmke
Hi,
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.
I already opened a bug report on openSuSE's bugzilla.
Post by Zbigniew Jędrzejewski-Szmek
Zbyszek
Thx for your answer.

Bye.
Michael.
--
Michael Hirmke
Loading...