11 May
2020
11 May
'20
3:04 p.m.
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?