| 1 |
On Tuesday, March 24, 2015 10:09:50 AM hw wrote: |
| 2 |
> |
| 3 |
> Am 24.03.2015 um 08:01 schrieb Alan McKinnon: |
| 4 |
> > On 23/03/2015 18:37, hw wrote: |
| 5 |
> >> |
| 6 |
> >> Hi, |
| 7 |
> >> |
| 8 |
> >> syslog-ng keeps reporting: |
| 9 |
> >> |
| 10 |
> >> |
| 11 |
> >> Mar 23 17:34:41 sunflo-mx syslog-ng[27532]: Error suspend timeout has |
| 12 |
> >> elapsed, attempting to write again; fd='15' |
| 13 |
> >> Mar 23 17:34:41 sunflo-mx syslog-ng[27532]: Suspending write operation |
| 14 |
> >> because of an I/O error; fd='15', time_reopen='60' |
| 15 |
> >> |
| 16 |
> >> |
| 17 |
> >> while there's plenty of disk space available. Restarting it didn't |
| 18 |
> >> help. This is from an LXC container --- could there be some disk limit |
| 19 |
> >> in effect by default which I don't know about? |
| 20 |
> >> |
| 21 |
> > |
| 22 |
> > |
| 23 |
> > You are on the wrong track. That error message does not say there is no |
| 24 |
> > space available. |
| 25 |
> > |
| 26 |
> > It says the disk is not available, something very different. Check dmesg. |
| 27 |
> > |
| 28 |
> |
| 29 |
> Mar 24 10:05:01 sunflo-mx syslog-ng[27532]: internal() messages are |
| 30 |
> looping back, preventing loop by suppressing all internal messages until |
| 31 |
> the current message is processed; trigger-msg='', |
| 32 |
> first-suppressed-msg='I/O error occurred while writing; fd=\'15\', |
| 33 |
> error=\'No space left on device (28)\'' |
| 34 |
> |
| 35 |
> |
| 36 |
> Somewhat misleading maybe ... |
| 37 |
|
| 38 |
I hate it when I run out of space on tty12 :) |
| 39 |
|
| 40 |
|
| 41 |
-- |
| 42 |
Fernando Rodriguez |
Archives