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 tolerant of thrashing.
What I presume happened is the system was thr
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
available memory is still gigabytes (it's a 32-bit userland running in a
64-bit ker
Hello systemd-devel.
Short summary from the old thread:
On 06.09.15 16:14, Lennart Poettering [1]:
> Ultimately our goal is that you build your tree of slices, and then
> freely attach users, services, containers, VMs to these slices at the
> places you want them. You can already do that nicely f
