No output! errors

[White, Chad (MED)]

Well, this is embarrassing but I think I figured it out.

Due to the nature of our environment I have to use distributed servers 
to monitor all the hosts.  To be clever, I separated the template 
definitions from services into a separate file than the services.  That 
way, I can use the same service.cfg file on every host, and just change 
the templates on each server for whether to perform an active check or 
not from that particular monitoring server.  Seemed like a good idea to 
me.

What seems to be happening is that the "remote" server is still trying 
to actively check things and is then submitting a "No output!" back to 
the "central" server when it fails.  I have tried removing freshness 
checking (that was on on the "remote" server) and I will see if that 
makes it stop..

Figures I would figure it out 5 minutes after sending a desperate plea 
for help. :)

thx,
--Chad

On Wednesday, March 12, 2003, at 02:36  PM, White, Chad (MED) wrote:

> Hi all, I hope someone can help me with this problem that is 
> absolutely driving me crazy.
>
> I have just installed Nagios 1.0 and I am attempting to get it 
> configured.  Everything that I am monitoring right now are Solaris 8 
> SPARC machines.  I've read all the documentation and have everything 
> compiled, installed and running.  At first I was very happy with 
> Nagios compared to Big Brother which is what we are using right now.  
> However I have been fighting with this problem for 2 days now and I am 
> no closer to figuring out the problem.
>
> What happens is that a number of my service checks will act 
> appropriately 50% of the time, and 50% of the time return (No 
> output!).  What does (No output!) mean exactly?  It doesn't seem to be 
> the same as when the plugins time out, which I have seen a few times 
> as well..
>
> Any ideas on what could be causing this?  Any kind of plugin I run 
> gives me this problem eventually, even ones that just check things on 
> the local monitoring services (like check_local_procs).  Due to the 
> sporadic nature, it feels like some kind of a resource limitation but 
> I am only monitoring around 25 services.
>
> Any help would be appreciated at this point!
> thx,
>
> --Chad White
>
>
> Here are some relevant pieces of my config:
> #hq-service template
> define service{
>         name                            hq-service      ;
>         active_checks_enabled           1
>         passive_checks_enabled          1
>         parallelize_check               1
>         obsess_over_service             1
>         check_freshness                 0
>         notifications_enabled           1
>         event_handler_enabled           1
>         flap_detection_enabled          1
>         process_perf_data               1
>         retain_status_information       1
>         retain_nonstatus_information    1
>         check_period                    24x7
>         normal_check_interval           30
>         max_check_attempts              10
>         retry_check_interval            1
>         notification_interval           120
>         notification_period             24x7
>         notification_options            w,u,c,r
>         register                        0
>         }
> # router1 ping service definition
> define service{
>         use                             hq-service
>
>         host_name                       router1
>         service_description             PING
>         is_volatile                     0
>         check_period                    24x7
>         max_check_attempts              3
>         normal_check_interval           5
>         retry_check_interval            1
>         check_command                   check_ping!100.0,20%!500.0,60%
>         }
>
> # 'router1' host definition
> define host{
>         use                     generic-host
>
>         host_name               router1
>         alias                   Router #1
>         address                 x.x.x.x
>         check_command           check-host-alive
>         max_check_attempts      20
>         notification_interval   60
>         notification_period     24x7
>         notification_options    d,u,r
>         }
>
> # 'check_ping' command definition
> define command{
>         command_name    check_ping
>         command_line    $USER1$/check_ping -H $HOSTADDRESS$ -w $ARG1$ 
> -c $ARG2$ -p 5
>         }
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by:Crypto Challenge is now open! Get 
> cracking and register here for some mind boggling fun and the chance 
> of winning an Apple iPod:
> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
> _______________________________________________
> 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


-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
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