Nope, lots of disk space:
df -k .
Filesystem 1K-blocks Used Available Use% Mounted on /dev/cciss/c0d0p2 69922596 5430680 60229552 9% /
It almost looks like maybe something had a lock on the file preventing something from reading it?
Would the new "hobbitping" work better? How do I get that?
-Jeff
On 5/5/06, Henrik Stoerner <henrik at hswn.dk> wrote:
On Thu, May 04, 2006 at 05:24:11PM -0500, Jeff Newman wrote:
All,
Every now and then, all of my hosts go red on conn and fail, then come right back up. Below is and excerpt from bb-network.log. As you can see, it's at no set time, no set date, it just plain fails. Any thoughts?
2006-03-06 23:20:29 Execution of '/usr/sbin/fping -Ae' failed with error-code 98 2006-03-06 23:20:29 Cannot open fping output file
The "code 98" is an internal code used by Hobbit when it fails to open two files that we use to pick up the output from fping. These go in ~hobbit/data/tmp/ directory, and are called fping-std{out,err}.PID
Perhaps you're short of diskspace ?
Regards, Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk