DISK CRITIKAL: No such file or directory

[matt_h2]

# su nagios
$ /usr/local/nagios/libexec/check_disk -w w20% -c c10% PPPPP
DISK OK - free space: PPPPP 23711 MB (99% inode=99%);| PPPPP=206MB;25197;25197;0;25197

[Box293]

So let's construct the same command that Nagios is generating from the check command and service.

$USER1$/check_nrpe -H $HOSTADDRESS$ -p5666 -c check_disk -a $ARG1$ $ARG2$ $ARG3$

What happens when you execute this on your Nagios server:

Code: Select all

/usr/local/nagios/libexec/check_nrpe -H HHHHH -p5666 -c check_disk -a 20% 10% PPPPP

It would be really useful if you could tell us the real text of PPPPP as this may have some special characters.

[matt_h2]

Yes, I don't see what harm showing the mount point being checked would be. Here is the result of your question:

$ /usr/local/nagios/libexec/check_nrpe -H HHHHH -p5666 -c check_disk -a 20% 10% /opt/apache
DISK OK - free space: /opt/apache 23711 MB (99% inode=99%);| /opt/apache=205MB;20157;22677;0;25197

I ran this from the Nagios monitoring server as the 'nagios' user.

This is really weird seeing as all the other mount points being checked report back fine on the Web browser view.

[matt_h2]

OMG!! We've figured it out and it's ridiculous! LOL

We had (by mistake) another object file trying to report on the same partition but pointing to a different server (which didn't have the /opt/apache partition). The Web browser view was confusing it making it look like it was coming from this particular object file.

After correcting the mistake and restarting nagios the error disappeared.

So sorry to have wasted your time but it's great to see people responding on this forum.

[Box293]

Excellent, glad you got to the bottom of it and I learned something new today