Re: [ClusterLabs] wireshark cannot recognize corosync packets

2017-03-17 Thread Jan Friesse
I have checked all the config files are the same, except bindnetaddr. So I'm sending only logs. I'm not sure if config files matches log files. Because config file contains nodes 200.201.162.(52|53|54), but log files contains ip 200.201.162.(52|53|55). Can you confirm node with ip

Re: [ClusterLabs] DRBD promotion based on ping

2017-03-17 Thread Victor
Hello, This is the status (when not failed): Last updated: Fri Mar 17 16:17:44 2017Last change: Fri Mar 17 14:21:24 2017 by root via cibadmin on db-main Stack: corosync Current DC: db-main (version 1.1.14-70404b0) - partition with quorum 2 nodes and 8 resources configured Online: [

Re: [ClusterLabs] DRBD promotion based on ping

2017-03-17 Thread Klaus Wenninger
On 03/17/2017 01:17 PM, Victor wrote: > Hello, > > I have implemented the following pacemaker configuration, and I have a > problem which I don't understand (and all my net searches were in > vain, probably not looking for the correct keywords). If the ping > fails on the Master node, it moves

[ClusterLabs] DRBD promotion based on ping

2017-03-17 Thread Victor
Hello, I have implemented the following pacemaker configuration, and I have a problem which I don't understand (and all my net searches were in vain, probably not looking for the correct keywords). If the ping fails on the Master node, it moves into Slave, but the other node also remains a slave