On 2011-10-13 17:22, Thomas wrote: > Hi Florian, > > thanks for the advice. I've been able to sort it out (at least I think > it was the reason of malfuction) just a minute before you wrote. > > The problem was, that I had "127.0.1.1 sh2.domain sh2" in /etc/hosts > (which was an entry inserted by debian ?!). And I guess that due to > this, the node itself wasn't able to respond to its own join offer as > stated in log: > >> Oct 13 12:34:03 sh2 crmd: [2292]: info: ghash_print_node: Welcome > >> reply not received from: sh2 6 > > Anyway, once I've edited /etc/hosts and restarted corosync, the node > joined the cluster almost immediately. > > One remark to "corosync-cfgtool -s" - I am not sure what does this check > when I run it. It says that both rings are active with no faults, but > all info stated is only related to the local node. What does it say > regarding the rest of the nodes in cluster?
It states, simply speaking, whether all nodes currently signed in are able to communicate. If you want to know how many nodes Corosync thinks the cluster has, "corosync-objtool | grep members" is usually the quickest way. If you want Pacemaker's view of the membership, use "crm node show" Hope this helps. Cheers, Florian -- Need help with Pacemaker? http://www.hastexo.com/now _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
