Passive service checks not being accepted by primary?

[Cliff Riggs]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thank you Paul,

I did disable the active checks for the services that were being 
checked remotely. I see the benefit of freshness checks, but I didn't 
want to enable those until I was confident that the passive checks 
themselves where being received properly.

I'm embarrassed to say it, but I figured out the problem - thanks to 
the comments on this board in response to my post and from scouring the 
archives. I mentioned that I used FreeBSD and I'm normally quite 
diligent about changing the Linux paths to match what FreeBSD uses. I 
neglected to do so in one portion of the example submit_check_results 
script in the Nagios Distributed Monitoring discussion page. I used the 
example "/bin/printf" when I should have been using the 
"/usr/bin/printf" for FreeBSD. This meant that garbage was being sent 
by the send_nsca script. I also neglected my own Nagios troubleshooting 
procedure of running the commands from the libexec/nagios directory 
when I was in trouble, which would have pointed out the problem right 
away.

Thank you to those who responded. I appreciate it!

Cliff
- --
- --------------------------------------------
Clifford Riggs
CCIE #9314, CISSP
- --------------------------------------------
Proteris Group LLC
Information Security Consultants
Trust. Expertise. Results.
- --------------------------------------------
www.proteris.com
- --------------------------------------------

On Mar 29, 2004, at 7:17 PM, Paul L. Allen wrote:

> Cliff Riggs writes:
>> log_passive_service_checks=1
>> accept_passive_service_checks=1
>
> If it is not possible to perform active checks, you need to disable
> those for the relevant services.  Otherwise if the passive check gets
> stale the active check will be performed and will probably fail with
> a plugin timeout.
> It works that way so you can have distributed monitoring.  You can 
> perform
> the checks directly from the central server but you use distributed 
> checks
> to reduce the load on it.  In this case, if one of the remote servers 
> goes
> down the central server can take over.  Obviously in this case you need
> enough spare capacity on the central server to cope if one (perhaps
> more, if you have a lot of remote servers) of the remote servers goes
> down.
> Having active checks enabled when they cannot actually be performed
> will lead to misleading error messages.  You'll still know there is
> a problem, but you'll be misled as to what the problem really is.
>> I did create a "check_dummy" command definition and apply it to my 
>> primary host 'check_command' as Demetri suggested, but I did not yet 
>> enable freshness checking as defined in the documentation. My 
>> understanding of the documentation was that this was an add-on to 
>> make sure you are regularly receiving updates from the remote server 
>> and not essential to accepting passive service checks.
>
> Freshness checking is not essential but it is desirable.  Without 
> freshness
> checking the remote server could die and you wouldn't know there is a
> problem for a long time, depending exactly on how checks of various
> services are scheduled (and especially if the remote server submits
> passive checks for itself).  With freshness checking you know if a 
> service
> check result is overdue.  It's not perfect, because you have to allow
> enough slop in the freshness check interval to cover worst-case 
> shceduling,
> which is not entirely deterministic.
> -- 
> Paul Allen
> Softflare Support
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)

iD8DBQFAaN/IJ3mHWY7troQRAvxjAJ4sO//ARS9aCncWoJNdZLtB0kHFWACeMmhP
09lxP+nTt2GmYzUCsLts+ro=
=IhDG
-----END PGP SIGNATURE-----



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
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