-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
I have a question about the way NSCA works. We have a distributed nagios system, where one server does most of the checks and sends them to the master server via NSCA. This works. Some other checks are done by the master server directly, this works too. Now we added some hosts that can't be reached by neither master nor slave server. We had to install a third server, that acts as a slave and sends its results to the master. In case of a failure of the nagios master server, the "old" slave takes its place. Now the results should be sent to the slave instead of the master (which is not available). What happens if the new slave sends the check results to the old slave? Will they be forwarded to to the master? Works it like a pyramid (several levels of check aggregation) or like a star (every distributed server has to reach the master)? Or should the new slave send the results to both old servers? On <http://nagios.sourceforge.net/docs/3_0/distributed.html>, I found "In order to force the distributed server to report all service check results, [...]" "all" would mean that passive check results were transmitted too. Am I right here? Regards, Werner -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9V57kACgkQk33Krq8b42PA5ACcD1gRt4C7kBscO3W81wZVxaoQ GisAn2Y/1KlGpDzAVPxuQVF0+0H0vDDC =fnOa -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Nagios-users mailing list Nagios-users@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
