Master slave config question
list Tom Diehl
Hi, I have xymon 4.3.7 running in a master slave configuration with the distribute module enabled. Enable/disable messages are being sent to the slave as expected. Is there a way to have acknowledgments also sent to the slave? Regards, -- Tom Diehl user-6203f2c4f8ec@xymon.invalid Spamtrap address user-0545b31a2bcf@xymon.invalid
list Henrik Størner
On Tue, 1 May 2012 08:07:59 -0400 (EDT), Tom Diehl <user-6203f2c4f8ec@xymon.invalid> wrote:
[distribute module] Is there a way to have acknowledgments also sent to the slave?
I wanted it to, but it doesn't do that currently. The reason is that in order to send an "ack" message you need to pin-code. These pin-code are generated indeendently by each Xymon server, so a xymond_distribute module on server A doesn't know what the pin-code is for an alert on server B. (It could fetch the Xymon board to find out). So xymond_distribute cannot generate an ack that will be accepted by the peer server. Poor excuse, I know, and it should be fixed. But now you know why it doesn't do that. Regards, Henrik
list Tom Diehl
Hi Henrik,
▸
On Wed, 2 May 2012, user-ce4a2c883f75@xymon.invalid wrote:
On Tue, 1 May 2012 08:07:59 -0400 (EDT), Tom Diehl <user-6203f2c4f8ec@xymon.invalid> wrote:[distribute module] Is there a way to have acknowledgments also sent to the slave?I wanted it to, but it doesn't do that currently. The reason is that in order to send an "ack" message you need to pin-code. These pin-code are generated indeendently by each Xymon server, so a xymond_distribute module on server A doesn't know what the pin-code is for an alert on server B. (It could fetch the Xymon board to find out). So xymond_distribute cannot generate an ack that will be accepted by the peer server. Poor excuse, I know, and it should be fixed. But now you know why it doesn't do that.
Thanks for the response. At least I know to not waste any more time trying to figure out how to make it work. :-) Regards, -- Tom Diehl user-6203f2c4f8ec@xymon.invalid Spamtrap address user-0545b31a2bcf@xymon.invalid