check_dirsize and "CHECK_NRPE: Socket timeout"

[Yogesh Hasabnis]

Hi All,

I am using nrpe and check_dirsize plugin to monitor the home directory sizes
of quite a few users. I receive the error "CHECK_NRPE: Socket timeout after
10 seconds" during the checking of quite a few directories. This error isn't
observed at each check or for each directory. It is observed very randomly
(say every 3rd check of a directory on an average). The error is observed
for the larger directories most of the times.  So assuming that the
check_dirsize plugin is taking longer to complete the check, I have set the
"command_timeout" value to 240 from the original default of 60 in the
nrpe.cfg of the remote host. Also changed the service_check_timeout value to
240 in the nagios.cfg on the nagios host. But I still get the error messages
quite a few times (not always). What could be the resolution for this error?

Secondly, is there any way to always schedule these checks at a specific
time. I would like to schedule them after work hours, because I suspect that
the access to the host on which these directories are located, becomes slow
when these checks are running.

Thanks in advance.

Yogesh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20070205/99e99f4d/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null