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

Warpme warpme at o2.pl
Wed Feb 22 10:06:06 PST 2012

On 2/20/12 11:35 PM, Olav Vitters wrote:
> On Thu, Feb 09, 2012 at 08:12:55PM +0100, Lennart Poettering wrote:
>> Now, of course, the journal shouldn't crash in the first place. This bug
>> is still something to fix, but so far nobody managed to get me a bt of
>> this. if the journal itself crashes a coredump will be placed in
>> /var/lib/systemd/coredump/. It would be great if somebody could generate
>> a backtrace of that!
> See https://bugs.mageia.org/show_bug.cgi?id=4588 and the duplicate for a
> few different stracktraces. Mageia still has v40 atm, so every crash is
> *very* noticeable.
Thx for hint.
BTW: is there any way to temporarily disable journald and relay on rsyslog ?
I'm on systemd43 with patch related to autorestart process when it's 
BindTo process was restarted 
(https://bugs.freedesktop.org/show_bug.cgi?id=45511). This makes 43 over 
37/39 a really should have release for me.
Unfortunately I have frequent systemd-journald - which unfortunately now 
are not destructive for run of other processes - but sometimes totally 
stops logging from those processes.


More information about the systemd-devel mailing list