Getting very close

Jonathan Bayles jbayles at readytechs.com
Thu Nov 5 21:03:01 CET 2009


Marc,

Thank you for pointing me to the distributed doc and for your explanations. I feel I am very close. Right now if I run:

/usr/local/nagios/libexec/eventhandlers/submit_check_result Athena 'PING' OK 'qwrweewfkljewfglkjwegjlwejglwjeglkjwegkwleg'

>From the distributed server it outputs correctly in the master server. I understand this to mean that the remote server is correct or close enough, and the NSCA pipe is correct.

 However, even with obsess and oscp_command set properly in the nagios.conf file on the distributed server the checks don't seem to be motivated to travel across. Do I need to setup a differen't service class with specific options to motivate the data across the NSCA pipe? What is the process flow of obsess?

-----Original Message-----
From: Marc Powell [mailto:marc at ena.com] 
Sent: Thursday, November 05, 2009 1:59 PM
To: Nagios-Users Mailinglist
Subject: Re: [Nagios-users] Problem with check_http


On Nov 5, 2009, at 9:35 AM, Tata, Joseph wrote:

> My command syntax is:
>
>  ./check_http -H <hostname or IP> -S -u '<name of the javascript  
> page>' -s OK -w 20 -c 30 -t 40
> This works completely fine on my 2.7 server, but always returns  
> "Connection refused HTTP CRITICAL - Unable to open TCP socket" when  
> run from the 3.2 server against the same target.
>
> Any idea what could be going on here?

We really don't have enough information to do anything but guess. An  
educated one would be that there doesn't appear to be a daemon listing  
on port 80 on <hostname or IP>. My speculation is either that the  
command definitions are different between the two versions (or your  
test) or the -H parameter is different between them (i.e. define host 
{ address xxx.xxx.xxx.xxx } is different or the macro you're using in  
the command definitions is different.) You could also have a firewall  
preventing that connection but you don't mention it being present.

At the very least you're trying to connect via SSL (-S) to port 80  
(HTTP), which is extremely unusual. Is that a special server  
configuration you've created?

As you can see, at the minimum posting real, complete definitions are  
necessary to tell you what's going on. Grab them from objects.cache  
and also working/non-working log entries from nagios.log.

--
Marc


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
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

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
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





More information about the Users mailing list