On Do, 08.02.18 23:50, Kai Krakow (hurikha...@gmail.com) wrote:
> During memory pressure and/or high load, journald may crash. This is
> probably due to design using mmap but it should really not do this.
> On 32-bit systems, we are seeing such crashes constantly although the
> available memory is still gigabytes (it's a 32-bit userland running in a
> 64-bit kernel).
> [82988.670323] systemd: systemd-journald.service: Main process exited,
> code=dumped, status=6/ABRT
> [82988.670684] systemd: systemd-journald.service: Failed with result
This last log lines indicates journald wasn't scheduled for a long
time which caused the watchdog to hit and journald was
aborted. Consider increasing the watchdog timeout if your system is
indeed that loaded and that's is supposed to be an OK thing...
Lennart Poettering, Red Hat
systemd-devel mailing list