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