[syslog-ng] Disk buffer file truncation issue
gabor.hl at gmail.com
Tue Jun 9 07:28:37 UTC 2020
Can you describe the issue in detail, please? Could you share the
You say there is an issue with disk-buffer truncating after it's emptied,
and that is resolved when syslog-ng restart?
How do you check if the queue is empty?
Raghunath Adhyapak <funduraghu at gmail.com> ezt írta (időpont: 2020. jún. 9.,
> 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:
>> 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
>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the syslog-ng