[systemd-devel] systemd39: journald segfault brings down some user services

warpme warpme at o2.pl
Fri Feb 3 02:53:56 PST 2012


I have question related to latest systemd39 & newly introduced journald.
I'm on ArchLinux (kernel 3.0.18). Recently - after upgrade from systemd37->39 I'm observing decreased system stability. 
It manifests as random services outages. 
So far during last days I had 2 such cases. 
In both of them careful log analysis points to hypothesis that event sequence was following:

1.segfault in systemd-journald
2.it looks like one from user process received restart event because of p1
3.other user processes which have "BindTo" to above process are stopped (as expected).
4.process from p2 is successfuly restarted (as expected).
5.process from p3 stays in "failed" state (despite Restart=always" and "BindTo" to proc from p2). I have to manually start it again.

My questions is following: it is possible that in systemd39 segfault in systemd-journal triggers restarting user service ?
Kernel log analysis didn't show any malfunction of process in p2. Kernel log simply says:

Feb  3 08:04:41 kernel: [  331.154128] systemd-journal[258]: segfault at 7f5e741030a0 ip 000000000040dc4c sp 00007fff71cbc490 error 4 in systemd-journald[400000+1f000]
Feb  3 08:04:41 [1972]:  Process 258 (systemd-journal) dumped core.
Feb  3 08:04:41 systemd[1]:  systemd-journald.service: main process exited, code=dumped, status=11
Feb  3 08:04:48 systemd[1]:  service1.service: main process exited, code=exited, status=141
Feb  3 08:04:48 systemd[1]:  service1.service holdoff time over, scheduling restart.
Feb  3 08:04:48 systemd[1]:  Unit service1.service entered failed state.

so it looks like service1 was restarted by external event. I can't find any correlated event beside journald segfault.


More information about the systemd-devel mailing list