[systemd-devel] some services always being killed when stress tests running

[Lennart Poettering]

On Tue, 22.03.16 10:02, Han Pingtian (hanpt at linux.vnet.ibm.com) wrote:

> But only after about 30 minutes, a lot of systemd services failed
> and restarted like this:
> 
> ... ... 
> [26885.910036] systemd[1]: systemd-journald.service: Failed with result 'signal'.
> [26885.910218] systemd[1]: systemd-udevd.service: Main process
> exited, code=killed, status=9/KILL

This indicates that something killed the processes in question with
SIGKILL. Quite possibly this was the OOM killer, which was triggered
by your stress test? Check the kernel logs if you see anything about
that...

Lennart

-- 
Lennart Poettering, Red Hat