Dear Michael, >please post such urls directly in the body, as it just destroys the subject in modern mail clients. roger that.
>> I'm using Icinga 1.7.1, with two different Ido2db process (one local >> and one remot). >> >> Both of them works correctly independently, but when enabled both >> modules, only the first one is active > >on what purpose? our client has it's own monitoring system, to which we don't have access, but we need to have information about the network, so we must have the same information in our system. Replicating the DB is not an option unfortunately. >> please advice, how to distribute service informations to multiple > >idomod processes! >idomod is the event broker module loaded into the core's memory subscribing to all neb events. ido2db is the daemon receiving the data via ido socket from idomod, running as seperate process. likely you mean that one. to be more exact yes, we must share the events between to separete ido2db processes located on two different machines. >the thing i do not really understand here is - what's the general idea in pushing duplicated data from the core to daemons? wouldn't it be better to replicate the rdbms backend, if that's meant as backup/hotstandby-failover >scenario? described above. don't have access to the international monitoring system, must build our own. the docs states, that I can define multiple event_brokers, however, it seems, that the same module can't be loaded with different configurations. T. ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ icinga-users mailing list icinga-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/icinga-users
