> On 13 Oct 2015, at 13:31, Kai Plückhahn <[email protected]> > wrote: > > Hi, > > i´m testing icinga2. > icinga2-bin-2.3.10-2.1.x86_64 on SLES12. > > I´m having a master cluster zone and some satellite zones. > When i do normal checks everything works fine but if i set the > command_endpoint option to one service > the debuglog explodes. The services works with not really high load but it > really seems that there is not everything ok! > Then i´m having tons of messages like > > [2015-10-13 12:31:13 +0200] debug/Checkable: No origin or local origin for > object 'clientONE!HP Raid', setting clientTWO as check_source. > [2015-10-13 12:31:13 +0200] debug/Checkable: command_endpoint found for > object clientONE!HP Raid', setting clientONE as check_source. > [2015-10-13 12:31:13 +0200] notice/ApiClient: Received 'event::CheckResult' > message from clientONE' > > It´s switch all the time the command_endpoint. First it´s putting in the > satellite or one of the masters and right later the specified one. > And all involved icinga clients produce tons of logs in really frightening > speed. > And the master services are updating all the time the database with the new > status of check_source. > If i comment out the option logging turn back to normal output.
That’s why this is called “debug log” as it contains detailed information for developers and users tracking down issues with a little more context than severity ‘information'. Nothing you should run permanently in production. Kind regards, Michael -- Michael Friedrich, DI (FH) Senior Developer NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg Tel: +49 911 92885-0 | Fax: +49 911 92885-77 GF: Julian Hein, Bernd Erk | AG Nuernberg HRB18461 http://www.netways.de | [email protected] ** OSMC 2015 - November - netways.de/osmc ** ** OSDC 2016 - April – netways.de/osdc ** _______________________________________________ icinga-users mailing list [email protected] https://lists.icinga.org/mailman/listinfo/icinga-users
