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 <[email protected]> wrote: > 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, or not known HTTP CRITICAL - Unable to open TCP socket" > is somewhat as if the dns server becomes inaccessible but when I run the > commands from the command line, the status is fine. Is there something > within Nagios that I need to set/configure? > Please help! > Thanks, > Allan. > On Mon, Aug 30, 2010 at 10:47 AM, newme me <[email protected]> wrote: >> >> 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 <[email protected]> wrote: >>> >>> 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 >>> commandline. Command line returns the correct status of OK instead of what >>> the Nagios web interface shows as "CRITICAL" >>> >>> Result from commandline(& browser) - >>> ./check_http -H xyz.com -p 2222 -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 is >>> behaving just fine based on the commandline result(and verified on the URL >>> through the browser). >>> >>> Please help! >>> >>> Thanks, >>> Allan. >>> >>> On Thu, Aug 26, 2010 at 10:26 PM, newme me <[email protected]> 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 the right status and Nagios reports correctly i.e. OK, WARN, >>>> ERROR based on the exit from the script. After 2-3 hrs output which was >>>> (and >>>> should be) OK or WARN starts returning CRITICAL and the output line says >>>> "Application is" and not even "Application is ERROR" or "Application is >>>> FATAL". >>>> >>>> There is nothing in the logs to suggest what could be the problem. Have >>>> you experienced this before and let me know the corrective action. I am >>>> running Nagios on Mac OSX. >>>> >>>> Here is the script for the curious - >>>> >>>> #!/bin/bash >>>> >>>> read URL < "$1" >>>> >>>> STATUS=`curl -s $URL |grep summary|awk -F\" '{print $2}'` >>>> echo "Application is $STATUS" >>>> echo "curl $URL" >>>> >>>> case $STATUS in >>>> OK) >>>> exit 0 >>>> ;; >>>> WARN) >>>> exit 1 >>>> ;; >>>> ERROR) >>>> exit 2 >>>> ;; >>>> FATAL) >>>> exit 2 >>>> ;; >>>> *) >>>> exit 2 >>>> ;; >>>> esac >>>> >>>> Thanks, >>>> >>>> Allan. >> > > > ------------------------------------------------------------------------------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > _______________________________________________ > Nagios-users mailing list > [email protected] > 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 > -- Diego Roccia diego.roccia (at) gmail (dot) com ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Nagios-users mailing list [email protected] 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
