After a period of 1-3 days, all logging stops, the webadmin indicates 100% cpu usage (top only indicates ~37% to start with but it seems to accumulate over a few days and slow the system). Only solution is to reboot.
I have tried: restarting syslog-ng, ulogd, repairing postgre (gives a bunch of cannot remove read only errors when trying to rm the old stuff), installed from a fresh iso restoring backup config (ran great for 2 days, then same deal).
Stopping syslog-ng gets rid of the 100% cpu use in webadmin.
The system otherwise continues functioning without logging. I have gotten a couple application control daemon restart mail notifications well after logging has failed.
The kernel log spit this 4 times before the last log cuttoff. It's the only thing suspicious.
2015:08:23-23:34:45 sophos kernel: [183447.776236] storvsc: Sense Key : 0x6 [current]
2015:08:23-23:34:45 sophos kernel: [183447.776240] storvsc: ASC=0x3f ASCQ=0x2
2015:08:23-23:34:45 sophos kernel: [183447.776603] sd 2:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters.
This thread was automatically locked due to age.
