> > I don't have answers, but questions: > Assuming node1 was DC when stopped: Will ist CIB still record it as DC after > being stopped? > Obviously node1 cannot know about any changes node2 did. And node1 when > started will find that node2 is unexpectedly down, so it will fence it to be > sure. node2 when started will thing ist DC also. That might trigger some > comunication with node1 to find out who's right. AFAIK node1 should win, > because it has the longer uptime. >
node1 is DC in this case. But this is not the cause for this unexpected node 2 cluster services shutdown. As I said, it happens sometimes. Having the same scenario, it seems to happen 25% of the times Thanks _______________________________________________ Users mailing list: Users@clusterlabs.org 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