Another observation about this bug, which might be helpful.
If the signal is sent to systemd-journald via
/bin/systemctl kill --kill-who=main --signal=SIGUSR1
then messages like the following show up in the kernel messages from `dmesg
[Sat Oct 15 21:02:35 2016] systemd-journald: Received request to
flush runtime journal from PID 1
but they don't show up in the output of 'journalctl -r'.
In /etc/systemd/journald.conf, it says:
so I would have thought the same messages would go to both places.
I don't know if I'm misunderstanding something here..
On Sat, Oct 15, 2016 at 9:07 PM, Daniel Povey <dpo...@gmail.com> wrote:
> BTW, I attach the output from `systemd-analyze dump`, as dump.txt.
> It would be great if the debian people could help us look into this.
> Lennart has a policy that his team will only look into bug reports in the
> latest two versions of systemd, and obviously we are well behind that.
> On Sat, Oct 15, 2016 at 8:53 PM, Daniel Povey <dpo...@gmail.com> wrote:
>> I just want to report that we are suffering from this bug, and it is
>> quite frequent.
>> This is with version 215-17+deb8u5 .
>> root@a12:~# systemctl status systemd-journald
>> *** systemd-journald.service - Journal Service
>> Loaded: loaded (/lib/systemd/system/systemd-journald.service; static)
>> Active: *failed* (Result: start-limit) since Sat 2016-10-15 12:01:57
>> EDT; 8h ago
>> Docs: man:systemd-journald.service(8)
>> Process: 51561 ExecStart=/lib/systemd/systemd-journald *(code=killed,
>> Main PID: 51561 (code=killed, signal=USR1)