<div dir="ltr">Another observation about this bug, which might be helpful.<div><br></div><div>If the signal is sent to systemd-journald via</div><div>/bin/systemctl kill --kill-who=main --signal=SIGUSR1 systemd-journald.service<br></div><div>then messages like the following show up in the kernel messages from `dmesg -T`, like:</div><div><br></div><div>[Sat Oct 15 21:02:35 2016] systemd-journald[26517]: Received request to flush runtime journal from PID 1<br></div><div><br></div><div>but they don't show up in the output of 'journalctl -r'. </div><div>In /etc/systemd/journald.conf, it says:</div><div><br></div><div><div>#MaxLevelStore=debug<br></div><div>#MaxLevelSyslog=debug</div></div><div><br></div><div>so I would have thought the same messages would go to both places. </div><div>I don't know if I'm misunderstanding something here..</div><div><br></div><div>Dan</div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Oct 15, 2016 at 9:07 PM, Daniel Povey <span dir="ltr"><<a href="mailto:dpovey@gmail.com" target="_blank">dpovey@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">BTW, I attach the output from `systemd-analyze dump`, as dump.txt.<div>It would be great if the debian people could help us look into this.</div><div>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.</div><div><br></div><div>Dan</div><div><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Oct 15, 2016 at 8:53 PM, Daniel Povey <span dir="ltr"><<a href="mailto:dpovey@gmail.com" target="_blank">dpovey@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div>I just want to report that we are suffering from this bug, and it is quite frequent.</div><div>This is with version 215-17+deb8u5 .</div><div><br></div><div><p style="margin:0px;font-size:12px;line-height:normal;font-family:menlo;background-color:rgb(241,241,241)">root@a12:~# systemctl status systemd-journald</p>
<p style="margin:0px;font-size:12px;line-height:normal;font-family:menlo;background-color:rgb(241,241,241)"><span style="color:rgb(188,48,28)"><b>*</b></span> systemd-journald.service - Journal Service</p>
<p style="margin:0px;font-size:12px;line-height:normal;font-family:menlo;background-color:rgb(241,241,241)"> Loaded: loaded (/lib/systemd/system/systemd-j<wbr>ournald.service; static)</p>
<p style="margin:0px;font-size:12px;line-height:normal;font-family:menlo;background-color:rgb(241,241,241)"> Active: <span style="color:rgb(188,48,28)"><b>failed</b></span> (Result: start-limit) since Sat 2016-10-15 12:01:57 EDT; 8h ago</p>
<p style="margin:0px;font-size:12px;line-height:normal;font-family:menlo;background-color:rgb(241,241,241)"> Docs: man:systemd-journald.service(8<wbr>)</p>
<p style="margin:0px;font-size:12px;line-height:normal;font-family:menlo;background-color:rgb(241,241,241)"> man:journald.conf(5)</p>
<p style="margin:0px;font-size:12px;line-height:normal;font-family:menlo;background-color:rgb(241,241,241)"> Process: 51561 ExecStart=/lib/systemd/systemd<wbr>-journald <span style="color:rgb(188,48,28)"><b>(code=killed, signal=USR1)</b></span></p>
<p style="margin:0px;font-size:12px;line-height:normal;font-family:menlo;background-color:rgb(241,241,241)"> Main PID: 51561 (code=killed, signal=USR1)</p></div><div><br></div><div><br></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>