I think you have split brain and both nodes are out of sync and likely doing stonith to each other. You may want to shutdown the crm resources on one of the node. And promote one of the node as primary and go through the steps to join the other node as part of the cluster as secondary node. Muhammad On 7/26/12 8:44 AM, "DIMITROV, TANIO" <td250y@xxxxxxx> wrote: >Hello, >I'm testing RHEL 6.2 cluster using CMAN. >It is a two-node cluster, no shared data. The problem is that if there is >a connectivity problem between the nodes, each of them continues working >as stand-alone - which is OK (no shared data, manual fencing). But when >the connection comes back up the nodes kill each other's cman instances : > >Jul 26 13:58:05.000 node1 corosync[15771]: cman killed by node 2 because >we were killed by cman_tool or other application >Jul 26 13:58:05.000 node1 gfs_controld[15900]: cluster is down, exiting >Jul 26 13:58:05.000 node1 gfs_controld[15900]: daemon cpg_dispatch error 2 >Jul 26 13:58:05.000 node1 dlm_controld[15848]: cluster is down, exiting > >Can this be avoided somehow? > >Thanks in advance! > > > >-- >Linux-cluster mailing list >Linux-cluster@xxxxxxxxxx >https://www.redhat.com/mailman/listinfo/linux-cluster -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
