Am 24.03.2015 um 10:13 schrieb Fernando Rodriguez:
On Tuesday, March 24, 2015 9:01:37 AM Alan McKinnon wrote:
On 23/03/2015 18:37, hw wrote:
Hi,
syslog-ng keeps reporting:
Mar 23 17:34:41 sunflo-mx syslog-ng[27532]: Error suspend timeout has
elapsed, attempting to write again; fd='15'
Mar 23 17:34:41 sunflo-mx syslog-ng[27532]: Suspending write operation
because of an I/O error; fd='15', time_reopen='60'
while there's plenty of disk space available. Restarting it didn't
help. This is from an LXC container --- could there be some disk limit
in effect by default which I don't know about?
You are on the wrong track. That error message does not say there is no
space available.
It says the disk is not available, something very different. Check dmesg.
It just says that a write failed. It could be anything.
I think disabling the logging to the console for the container solves
this; I commented out the entries in /etc/syslog-ng/syslog-ng.conf:
# destination console_all { file("/dev/tty12");
# log { source(src); destination(console_all);
... and restarted syslog-ng, and the error hasn't come back yet.
