Hi, some more information about my problem (see previous email for complete log) (sorry if someone sent to me a response but I've not got any for now perhaps because I'm in digest mode) But if I start qdiskd after cman and in foreground likewise : qdiskd -ddd -f There is no more the problem of infernal loop "Node is undead" , the log on stdout is : [11136] info: Initial score 1/1 [11136] info: Initialization complete [11136] notice: Score sufficient for master operation (1/1; required=1); upgrading [11136] debug: Making bid for master [11136] info: Assuming master role [11136] debug: Node 1 is UP [11136] debug: Node 1 missed an update (2/10) [11136] debug: Node 1 missed an update (3/10) [11136] debug: Node 1 missed an update (4/10) [11136] debug: Node 1 missed an update (5/10) [11136] debug: Node 1 missed an update (6/10) [11136] debug: Node 1 missed an update (7/10) [11136] debug: Node 1 missed an update (8/10) [11136] debug: Node 1 missed an update (9/10) [11136] debug: Node 1 missed an update (10/10) [11136] debug: Node 1 missed an update (11/10) [11136] debug: Node 1 DOWN [11136] notice: Writing eviction notice for node 1 [11136] debug: Telling CMAN to kill the node [11136] notice: Node 1 evicted and the log ends here, and there is no problem "Node x is undead" and when the node1 is rebooted, the launch of CS on node 1 is successful (the node1 enters the cluster without problem as the node2 has not flagged it as "undead" ). I don't know if this test could be meaningful for you to help me to identify the problem . Lon, perhaps have you an idea about this ? Because I'm sure the Node1 is not writing again its timestamp avec the 11 "missing an update" , so the cause of "Node is undead" is not that Node2 got a timestamp of Node1 in quorum after having declared it Off. Thanks for your help Regards Alain |
-- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
