<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>We've mostly resolved the issue (combination of flow control and
feeding syslog-ng from the journald file. Disabling flow control
and rate limiting and setting forward to syslog true almost cures
things.</p>
<p>However, there's a serious bug in journald which will cause some
number of logs to disappear without any report of missed
forwarding of logs. I've raised an issue on the github master for
systemd <br>
</p>
<p><a href="https://github.com/systemd/systemd/issues/13078">https://github.com/systemd/systemd/issues/13078:</a></p>
<p>Possible bug in journald-syslog.c #13078</p>
<p>I fear that this oversight in systemd/journald is not the only
occurrence of this bug, just the one we're seeing.<br>
</p>
<div class="moz-cite-prefix">On 7/10/19 10:53 AM, Fabien Wernli
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:20190710085352.GD19364@ccfawe.in2p3.fr">
<pre class="moz-quote-pre" wrap="">Hi,
On Fri, Jul 05, 2019 at 03:00:48PM +0000, Evan Rempel wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">I noticed that between 3.9 and 3.14 this issue was introduced. Buffering to any destination seems to block all destinations of he message.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
This seems pretty bad to me.
Could you open an issue on github for this please?
______________________________________________________________________________
Member info: <a class="moz-txt-link-freetext" href="https://lists.balabit.hu/mailman/listinfo/syslog-ng">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a>
Documentation: <a class="moz-txt-link-freetext" href="http://www.balabit.com/support/documentation/?product=syslog-ng">http://www.balabit.com/support/documentation/?product=syslog-ng</a>
FAQ: <a class="moz-txt-link-freetext" href="http://www.balabit.com/wiki/syslog-ng-faq">http://www.balabit.com/wiki/syslog-ng-faq</a>
</pre>
</blockquote>
</body>
</html>