monitoring services

[Marc Powell]

> -----Original Message-----
> From: Fabiano Martins [mailto:fmapconsulting at aol.com]
> Sent: Friday, May 13, 2005 5:29 PM
> To: Marc Powell
> Subject: RE: [Nagios-users] monitoring services
> 
> OK... Thanks
> 
> I'm gonna try to setup a vpn to monitor DHCP service.
> 
> I would like to know another thing... I have a lot of servers that
runs an
> specific web service in a diferent port than usually (85). I'm trying
to
> monitor that.
> 
> I've already changed the "checkcommand.cfg" as follows:
> 
> # 'check_http' command definition
> define command{
>         command_name    check_http
>         command_line    $USER1$/check_http -I $HOSTADDRESS$ -p 85
>         }
> 
> And I keep receiving the message "CRITICAL - Socket timeout after 10
> seconds"
> 
> Do you have an idea about it?

That's the correct syntax. Did you restart nagios after changing the
command? Are you sure it restarted? If the answer is yes to both, then
it would appear that your monitoring machine simply can't reach that
port or it's taking longer than 10 seconds to respond. Try telnet to
port 85 as the nagios user from your monitoring box as follows --

bash-2.05a$ telnet somehost 85
Trying somehost...
Connected to somehost.
Escape character is '^]'.
GET / HTTP/1.0
[type another return here]
HTTP/1.0 200 OK

<data>
Connection closed by foreign host.

The web server should answer almost immediately and the time after the
GET request to connection close should be no longer than 10 seconds. If
it is longer, you might want to consider extending the timeout.

--
Marc


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_ids93&alloc_id281&op=click
_______________________________________________
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