Did anyone want to comment on this post? I expected to hear back from someone. On Wed, 15 Mar 2006, Evan Rempel wrote:
Date: Wed, 15 Mar 2006 22:21:31 -0800 (PST) From: Evan Rempel <erempel@uvic.ca> Reply-To: Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu> To: Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu> Subject: [syslog-ng] syslog-ng 1.6.8 does not reopen logs when out of disk space
I am running syslog-ng 1.6.8 and when my logging space fills up (that's a different story) syslog-ng closes the log file with messages like
io.c: do_write: write() failed (errno 28), No space left on device pkt_buffer::do_flush(): Error flushing data
and starts queueing messages according to the log_fifo_size option. My concern is that when disk space became available again, the logging was not resumed, and I lost all of the messages for the closed log files until the macro expansion changed the file name.
Shouldn't the "time_reopen" apply to files as well? I have it set to 5 seconds.
Is there another option that would allow me to handle this situation?
How would this be handled in the 1.9 (2.0) code path?
Evan Rempel