Problems with passing on service check information

[Steven Schwartz]

I am trying to follow the instructions to use a centralized server in
the Nagios documentation, with one major change - instead of reporting
all errors to a central server and having it do the notifications, I
want the individual servers to do their own notification, and also send
copies of service check results to a central, read-only server, at the
moment called bigboard.

 

<looks at problem, suddenly realizes that he may know what the fix is>

 

Does anyone know what happens if you try and use send_nsca to
communicate to a machine running two separate nagios instances?

 

Steven Schwartz

 

 

CONFIDENTIALITY NOTICE: Proprietary/Confidential Information belonging
to Gracenote, Inc. may be contained in this message. If you are not a
recipient indicated or intended in this message (or responsible for
delivery of this message to such person), or you think for any reason
that this message may have been addressed to you in error, you may not
use or copy or deliver this message (and all attachments) to anyone
else. In such case, you should destroy this message (and all attached
documents) and are asked to notify the sender by reply email.

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20070221/bb44fc8b/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
-------------- 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