NSClient NRPE Socket Timeout

[samye]

Hello,

I have googled and searched and cannot find an answer to the socket timeout error. I have Nagios 3.2.2 installed. I am using the current version of NSClient++ installed on a Win2003 server. I have approximately 20 service checks with about 10 CheckDriveSize service checks on the server using NSClient nrpe. All checks except one CheckDriveSize check work. The check that is not working is intermittent where every once in awhile it gets a socket timeout and it is on drive Y. None of the other drives have this issue.

We have increased the socket_timeout parm to 30 in the nsclient.ini file. If I executed from the CL, the check always works. In the cgi, the check gets the timeout error intermittently. Increasing the socket_timeout parm did not change anything.

Please help.

Regards,
Carol

Here is the service check definition:
define service {
host_name host
use contact
service_description NRPE DISK: Check Y drive
check_command nt_check_nrpe!CheckDriveSize!ShowAll=long MinWarnFree=9% MinCritFree=4% Drive=y:\\
}

[mguthrie]

Can you post the actual command-line test that you're running that is working (minus any private data)?

Also, there is also a service timeout setting in the nagios.cfg file, you could try increase that as well, but I'm wondering if the timeout needs to be increased in the command definition on the Nagios side.

[samye]

The check from the command line is:
sudo check_nrpe -H host dns name -p 5666 CheckDriveSize -a ShowAll MaxWarn=90 MaxCrit=95 Drive=y:\\

All other drive (c, d, etc.) checks on this server work fine and there are several other servers that check a y drive.

I don't think its a timeout error. I think it's something else but I don't know where to look.

[mguthrie]

Drive=y:\\

Do you have these backslashes in the other check commands? Does the check work if you wrap everything after the -a flag in single quotes?

[samye]

Hi,

I do have the "//" slashes in the other commands but I took them out at the Command Line and the check still works. I'm not sure what you mean about the -a parm. The check works from the Command Line with all of the information passed after the -a.