Hi, Any idea what could have gone wrong or if there are other ways to achieve the same ?
Regards, Sriram. ---------- Forwarded message ---------- From: Sriram <[email protected]> Date: Thu, Aug 3, 2017 at 12:31 PM Subject: Notification agent and Notification recipients To: Cluster Labs - All topics related to open-source clustering welcomed < [email protected]> Hi Team, We have a four node cluster (1 active : 3 standby) in our lab for a particular service. If the active node goes down, one of the three standby node becomes active. Now there will be (1 active : 2 standby : 1 offline). Is there any way where this newly elected node sends notification to the remaining 2 standby nodes about its new status ? I was exploring "notification agent" and "notification recipient" features, but that doesn't seem to work. /etc/sysconfig/notify.sh doesn't get invoked even in the newly elected active node. Cluster Properties: cluster-infrastructure: corosync dc-version: 1.1.17-e2e6cdce80 default-action-timeout: 240 have-watchdog: false no-quorum-policy: ignore *notification-agent: /etc/sysconfig/notify.sh* * notification-recipient: /var/log/notify.log* placement-strategy: balanced stonith-enabled: false symmetric-cluster: false I m using the following versions of pacemaker and corosync. /usr/sbin # ./pacemakerd --version Pacemaker 1.1.17 Written by Andrew Beekhof /usr/sbin # ./corosync -v Corosync Cluster Engine, version '2.3.5' Copyright (c) 2006-2009 Red Hat, Inc. Can you please suggest if I m doing anything wrong or if there any other mechanisms to achieve this ? Regards, Sriram.
_______________________________________________ Users mailing list: [email protected] http://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
