Hi,
Our lab has two resource: (1) PAF (master/slave) (2) VIP (bind to the master PAF node). The configuration is in the attachment. Each node has two network card: One(enp0s8) is for the pacemaker heartbeat in internal network, the other(enp0s3) is for the master VIP in the external network. We are testing the following case: if the master VIP network card is down, the master postgres and VIP could switch to another node. 1. At first, node2 is master, I run "ifdown enp0s3" in node2, then node1 become the master, that is ok. [cid:image001.png@01D3DCB4.E6FC6140] [cid:image002.png@01D3DCB5.4DF4DA80] 2. Then I run "ifup enp0s3" in node2, wait for 60 seconds, then run "ifdown enp0s3" in node1, but the node1 still be master. Why does switchover doesn't happened? How to recover to make system work? [cid:image003.png@01D3DCB5.AC487F60] The log is in the attachment. Node1 reports the following waring: Apr 25 04:49:27 node1 crmd[24678]: notice: State transition S_IDLE -> S_POLICY_ENGINE Apr 25 04:49:27 node1 pengine[24677]: warning: Processing failed op start for master-vip on sds2: unknown error (1) Apr 25 04:49:27 node1 pengine[24677]: warning: Processing failed op start for master-vip on sds1: unknown error (1) Apr 25 04:49:27 node1 pengine[24677]: warning: Forcing master-vip away from sds1 after 1000000 failures (max=1000000) Apr 25 04:49:27 node1 pengine[24677]: warning: Forcing master-vip away from sds2 after 1000000 failures (max=1000000) Apr 25 04:49:27 node1 pengine[24677]: notice: Calculated transition 14, saving inputs in /var/lib/pacemaker/pengine/pe-input-59.bz2 Apr 25 04:49:27 node1 crmd[24678]: notice: Transition 14 (Complete=0, Pending=0, Fired=0, Skipped=0, Incomplete=0, Source=/var/lib/pacemaker/pengine/pe-input-59.bz2): Complete
info.rar
Description: info.rar
_______________________________________________ Users mailing list: Users@clusterlabs.org https://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
