There was indeed a filesystem corruption - however, fsck only found
problems with the files munin had touched.
There was no other indication that anything else had done anything
wrong, misbehaved or otherwise was out of whack and I monitor this
machine fairly closely.
I agree that the filesystem corruption thing is probably the cause here
but I'm still puzzled by the fact that munin was the only process that
broke anything else. This machine also runs backuppc and does a nightly
backup of ~70Gb worth of data.
Munin did not run as root btw.
I really don't have any other good ideas here - obviously I hope I
can't/won't recreate the problem.
- OM
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
