Nagios reporting no output when there is output

[Anthony Montibello]

Hi,

this may be related to freshness checking.


check what your freshness check command is,
then test it to see what its output is.
IF you have the Hosts reporting every 1/2 hr
and nagios freshness testing every 1 hr,
that means if one check is accedenly droped before nagios processes it
 ( this can happen for different reasons)
your odds of failing a freshness test drastically increase.
this would be noticed if the Hosts check is recieved within a few minutes
afte the alert
I like to setup freshness checking for 3-5x the check interval
so for testing every 1/2 hr, I would freshness check every 2-3 hrs not every
1 hr.


TOny

On Fri, May 15, 2009 at 4:04 PM, Marc Powell <marc at ena.com> wrote:

>
> On May 15, 2009, at 2:29 PM, Jean-Michel Philippon-Nadeau wrote:
>
> > Thanks for your reply Tom.
> > I really appreciate that you take a few minutes of your time to help
> > me
> > on this one.
> >
> > Tom Wlodek wrote:
> >> You may also check whether you run it by hand as the right user.
> >> Common
> >> mistake is to execute plugins or scripts as one user 9say, root) and
> >> then nagios executes them as another one (say "nagios"). It works for
> >> user root but not for user nagios.
> >
> > The Nagios server does not actively check the disk status of every
> > monitored server. Each server has a script in it's crontab that checks
> > the disks and sends the status via NCSA to the main Nagios server.
> >
> > Correct me if I'm wrong, but I do not think the user running the
> > script
> > on the monitored host can interfere with how the Nagios server will
> > parse the answer. Am I right?
>
> Nagios/NSCA don't parse the answer at all, other than to say '(no
> output)' when the passive results or plugin execution have no text
> output. This is most often caused by an error being returned by the
> plugin.
>
> Something is happening, either with the execution of the check_disk
> plugin, the passing of those results to send_nsca or send_nsca's
> transmission of those results to nagios. I expect it's one of the
> first two but you can easily work this issue backwards. Put NSCA into
> debug mode on the nagios server. Observe the check results coming in.
> If they are not correct, add debugging output to your script that's
> executing the plugin and passing the results to send_nsca, have it log
> to a file, to identify where the breakdown is occurring. That should
> guide you on how to fix it.
>
> You could also capture any error output generated by the plugin to
> adding '2>&1' to the end of the check_disk line.
>
> --
> Marc
>
>
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables
> unlimited royalty-free distribution of the report engine
> for externally facing server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20090516/a2b3dc25/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables 
unlimited royalty-free distribution of the report engine 
for externally facing server and web deployment. 
http://p.sf.net/sfu/businessobjects
-------------- next part --------------
_______________________________________________
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