[syslog-ng] Disk buffer file truncation issue

Raghunath Adhyapak funduraghu at gmail.com
Mon Jun 8 22:08:30 UTC 2020

Correcting subject

We did some more troubleshooting on this and we found that all logs in
buffer were indeed sent out and that syslog-ng was facing issues in
truncating the file.
This issue got fixed with restart.
However, we are observing that this issue is happening too often.
Would anyone help me understand why this could be happening?


On Mon, May 11, 2020, 19:34 Fabien Wernli <wernli at in2p3.fr> wrote:

> Hi,
> On Mon, May 11, 2020 at 12:23:27PM +0000, László Várady (lvarady) wrote:
> > > 2. Why couldn't syslog-ng resume operations after partition was freed
> up and destination was available?
> >
> > That might be a bug. Once a destination becomes available (set
> time-reopen() to a lower value to check more frequently), syslog-ng should
> send messages out from the disk buffer.
> > Could you reproduce this issue and share the reproduction steps?
> I remember having a lot of corrupt disk buffers when disk was full.
> In my case, they caused a segfault on startup, maybe that got "fixed" by a
> deletion instead?
> ______________________________________________________________________________
> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Documentation:
> http://www.balabit.com/support/documentation/?product=syslog-ng
> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.balabit.hu/pipermail/syslog-ng/attachments/20200609/1d022ac5/attachment.html>

More information about the syslog-ng mailing list