Am Thu, 08 Feb 2018 18:12:23 -0800 schrieb vcaputo:
> Note the logs you've pasted portray a watchdog timeout which resulted in
> SIGABRT and a subsequent core dump.
>
> This is not really a journald "crash", and you can increase the watchdog
> timeout or disable it entirely to make it more
On Fri, 2018-02-09 at 12:41 +0100, Lennart Poettering wrote:
> 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
On Do, 08.02.18 23:50, Kai Krakow (hurikha...@gmail.com) wrote:
> Hello!
>
> 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
>
