clearly there something wrong with the check configuration.
Maybe some duplicated conf.
you could debug the script output (see nagios.cfg file)
On Mon, Aug 30, 2010 at 10:16 PM, newme me wrote:
> One more thing I would like to add here , I have 5 URLs check , 2 thru
> check_http and 3 thru my own
One more thing I would like to add here , I have 5 URLs check , 2 thru
check_http and 3 thru my own curl script and all of them fail at the same
time, initially for 2-3 hrs all are returning the right status.
The error that I am getting from Nagios(check_http) - "nodename nor
servname provided, o
Hi Marc,
Thanks for your reply, I checked on the multiple process of Nagios but there
is only one running.
Any other thing you can think of which might be causing this odd behaviour?
Thanks,
Allan.
On Sun, Aug 29, 2010 at 6:12 PM, newme me wrote:
> Folks,
>
> I switched to "check_http" plugin
On Aug 29, 2010, at 8:12 PM, newme me wrote:
> ./check_http -H xyz.com -p -u /abc -t 3
> OK
>
> Result from Nagios Interface -
> nodename nor servname provided, or not known
> HTTP CRITICAL - Unable to open TCP socket
>
> I am thinking that this has something to do with Nagios as the box
You aren't passing that "<http://xyz.com>" thing to the server, are you?
Sent from my BlackBerry® wireless device
-Original Message-
From: newme me
Date: Sun, 29 Aug 2010 18:12:10
To:
Reply-To: Nagios Users List
Subject: Re: [Nagios-users] Nagio
Folks,
I switched to "check_http" plugin (official nagios plugin) but that also has
same problem.
Initially when I start nagios then the status on the Nagios Web interface is
same as the one returned from commandline.
After some time the status becomes critical but is not as same as the
command
users] Nagios script output issue
--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users
worldwide. Take advantage of sp
On 27 August 2010 06:26, newme me wrote:
> Hi Folks,
>
> Nagios is acting a little weird for me, I have this external script which I
> hooked into Nagios, it merely does a curl/wget on a URL and returns the
> status based on string in the content/output. Initially for 2-3 hrs the
> script returns
Hi Folks,
Nagios is acting a little weird for me, I have this external script which I
hooked into Nagios, it merely does a curl/wget on a URL and returns the
status based on string in the content/output. Initially for 2-3 hrs the
script returns the right status and Nagios reports correctly i.e. OK
