| 1 |
On 23/03/2015 18:37, hw wrote: |
| 2 |
> |
| 3 |
> Hi, |
| 4 |
> |
| 5 |
> syslog-ng keeps reporting: |
| 6 |
> |
| 7 |
> |
| 8 |
> Mar 23 17:34:41 sunflo-mx syslog-ng[27532]: Error suspend timeout has |
| 9 |
> elapsed, attempting to write again; fd='15' |
| 10 |
> Mar 23 17:34:41 sunflo-mx syslog-ng[27532]: Suspending write operation |
| 11 |
> because of an I/O error; fd='15', time_reopen='60' |
| 12 |
> |
| 13 |
> |
| 14 |
> while there's plenty of disk space available. Restarting it didn't |
| 15 |
> help. This is from an LXC container --- could there be some disk limit |
| 16 |
> in effect by default which I don't know about? |
| 17 |
> |
| 18 |
|
| 19 |
|
| 20 |
You are on the wrong track. That error message does not say there is no |
| 21 |
space available. |
| 22 |
|
| 23 |
It says the disk is not available, something very different. Check dmesg. |
| 24 |
|
| 25 |
-- |
| 26 |
Alan McKinnon |
| 27 |
alan.mckinnon@×××××.com |
Archives