On Tuesday, March 24, 2015 10:09:50 AM hw wrote: > > Am 24.03.2015 um 08:01 schrieb Alan McKinnon: > > 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. > > > > Mar 24 10:05:01 sunflo-mx syslog-ng[27532]: internal() messages are > looping back, preventing loop by suppressing all internal messages until > the current message is processed; trigger-msg='', > first-suppressed-msg='I/O error occurred while writing; fd=\'15\', > error=\'No space left on device (28)\'' > > > Somewhat misleading maybe ...
I hate it when I run out of space on tty12 :) -- Fernando Rodriguez
