i assume instead of check_http -a 10.10.10.34 you mean whatever is in nrpe.cfg for check_http command, so i'm showing you whats in there and i'm trying to execute that command and it works fine, but not through nrpe...
# grep check_http ~nagios/etc/nrpe.cfg command[check_http]=/usr/local/nagios/libexec/check_http -I $ARG1$ -e 200 # /usr/local/nagios/libexec/check_http -I 10.10.10.34 -e 200 HTTP OK HTTP/1.1 200 OK - 299 bytes in 0.002 seconds |time=0.002095s;;;0.000000 size=299B;;;0 # On 10/30/07, Hari Sekhon <[EMAIL PROTECTED]> wrote: > alexus wrote: > > does it make sense for anyone? > > > > d# ~nagios/libexec/check_nrpe -H 10.10.10.34 > > NRPE v2.6 > > d# ~nagios/libexec/check_nrpe -H 10.10.10.34 -c check_http -a 10.10.10.34 > > CHECK_NRPE: Socket timeout after 10 seconds. > > d# > > > > > > > This does not make sense to me. Why are you using nrpe against a machine > and then testing the web server on the same local machine? > > If you have a good reason and insist on doing this, then try logging in > the the machine 10.10.10.34 and running the check_http -a 10.10.10.34 > command manually to see if the plugin is returning properly. Nrpe could > timeout waiting for the plugin. Alternatively you can also try to > increase the check_nrpe timeout to 30 secs with -t 30. > > -h > > Hari Sekhon > > > > -- http://alexus.org/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Nagios-users mailing list Nagios-users@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