Here are also some Additional some additional information for a failover with setting the node standby.
Apr 12 12:40:28 s1 pacemaker-controld[1611990]: notice: State transition S_IDLE -> S_POLICY_ENGINE Apr 12 12:40:28 s1 pacemaker-schedulerd[1611989]: notice: On loss of quorum: Ignore Apr 12 12:40:28 s1 pacemaker-schedulerd[1611989]: notice: Actions: Stop sto-ipmi-s0 ( s1 ) due to node availability Apr 12 12:40:28 s1 pacemaker-schedulerd[1611989]: notice: Actions: Stop pri-zfs-drbd_storage:0 ( s1 ) due to node availability Apr 12 12:40:28 s1 pacemaker-schedulerd[1611989]: notice: Actions: Stop pri-drbd-pluto:0 ( Promoted s1 ) due to node availability Apr 12 12:40:28 s1 pacemaker-schedulerd[1611989]: notice: Actions: Stop pri-drbd-poserver:0 ( Promoted s1 ) due to node availability Apr 12 12:40:28 s1 pacemaker-schedulerd[1611989]: notice: Actions: Stop pri-drbd-webserver:0 ( Promoted s1 ) due to node availability Apr 12 12:40:28 s1 pacemaker-schedulerd[1611989]: notice: Actions: Stop pri-drbd-dhcp:0 ( Promoted s1 ) due to node availability Apr 12 12:40:28 s1 pacemaker-schedulerd[1611989]: notice: Actions: Stop pri-drbd-wawi:0 ( Promoted s1 ) due to node availability Apr 12 12:40:28 s1 pacemaker-schedulerd[1611989]: notice: Actions: Stop pri-drbd-wawius:0 ( Promoted s1 ) due to node availability Apr 12 12:40:28 s1 pacemaker-schedulerd[1611989]: notice: Actions: Stop pri-drbd-saturn:0 ( Promoted s1 ) due to node availability Apr 12 12:40:28 s1 pacemaker-schedulerd[1611989]: notice: Actions: Stop pri-drbd-openvpn:0 ( Promoted s1 ) due to node availability Apr 12 12:40:28 s1 pacemaker-schedulerd[1611989]: notice: Actions: Stop pri-drbd-asterisk:0 ( Promoted s1 ) due to node availability Apr 12 12:40:28 s1 pacemaker-schedulerd[1611989]: notice: Actions: Stop pri-drbd-alarmanlage:0 ( Promoted s1 ) due to node availability Apr 12 12:40:28 s1 pacemaker-schedulerd[1611989]: notice: Actions: Stop pri-drbd-jabber:0 ( Promoted s1 ) due to node availability Apr 12 12:40:28 s1 pacemaker-schedulerd[1611989]: notice: Actions: Stop pri-drbd-TESTOPTIXXX:0 ( Promoted s1 ) due to node availability Apr 12 12:40:28 s1 pacemaker-schedulerd[1611989]: notice: Actions: Move pri-vm-jabber ( s1 -> s0 ) due to unrunnable mas-drbd-jabber demote Apr 12 12:40:28 s1 pacemaker-schedulerd[1611989]: notice: Actions: Move pri-vm-alarmanlage ( s1 -> s0 ) due to unrunnable mas-drbd-alarmanlage demote Apr 12 12:40:28 s1 pacemaker-schedulerd[1611989]: notice: Calculated transition 5, saving inputs in /var/lib/pacemaker/pengine/pe-input-2478.bz2 Apr 12 12:40:28 s1 pacemaker-controld[1611990]: notice: Initiating stop operation sto-ipmi-s0_stop_0 locally on s1 Apr 12 12:40:28 s1 pacemaker-controld[1611990]: notice: Requesting local execution of stop operation for sto-ipmi-s0 on s1 Apr 12 12:40:28 s1 pacemaker-controld[1611990]: notice: Initiating stop operation pri-vm-jabber_stop_0 locally on s1 Apr 12 12:40:28 s1 pacemaker-controld[1611990]: notice: Requesting local execution of stop operation for pri-vm-jabber on s1 Apr 12 12:40:28 s1 pacemaker-controld[1611990]: notice: Initiating stop operation pri-vm-alarmanlage_stop_0 locally on s1 Apr 12 12:40:28 s1 pacemaker-controld[1611990]: notice: Requesting local execution of stop operation for pri-vm-alarmanlage on s1 Apr 12 12:40:28 s1 pacemaker-controld[1611990]: notice: Result of stop operation for sto-ipmi-s0 on s1: ok Any help on this topic are very welcome because lack to find any solution for this behaviour. Kind regards Philip.
_______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
