fping failure

Here is some more info (df -i, ls in the tmp dir)

# cd /usr/local/hobbit/server/tmp
# ls
alert.chk           fping-stderr.17687  fping-stdout.17182  fping-stdout.18045
alert.chk.sub       fping-stderr.18009  fping-stdout.17471  fping-stdout.28736
fping..status       fping-stderr.18026  fping-stdout.17520  fping-stdout.31722
fping-stderr.17182  fping-stderr.18045  fping-stdout.17576  fping-stdout.4937
fping-stderr.17471  fping-stderr.28736  fping-stdout.17687  hobbitd.chk
fping-stderr.17520  fping-stderr.31722  fping-stdout.18009
fping-stderr.17576  fping-stderr.4937   fping-stdout.18026
# df -k .
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/cciss/c0d0p2     69922596   5436192  60224040   9% /
# df -i .
Filesystem            Inodes   IUsed   IFree IUse% Mounted on
/dev/cciss/c0d0p2    8897472  178544 8718928    3% /

-Jeff


On 5/5/06, Henrik Stoerner <user-ce4a2c883f75@xymon.invalid> wrote:

On Fri, May 05, 2006 at 09:32:15AM -0500, Jeff Newman wrote:

Nope, lots of disk space:

# df -k .
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/cciss/c0d0p2     69922596   5430680  60229552   9% /

How about inodes ? "df -i"

It almost looks like maybe something had a lock on the file
preventing something from reading it?

No, something prevented us from creating it.

Would the new "hobbitping" work better? How do I get that?

This is before fping/hobbitping gets to run, so I don't think it will
make any difference. Still, if you want to try it out just grab the
latest snapshot and build it. Then you can copy the bbnet/hobbitping
binary to your Hobbit server/bin/ directory - make sure it is suid-root.
And change your FPING setting to point at "$BBHOME/bin/hobbitping"


Henrik