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