Hi Chrissie,
Thanks for your quick response.
But we started the cman manually and then did not start any other
service between.
There is no risk that the network goes down during the test.
We don't use actually 'intelligent switch' and no cisco switches.
We made a new test with the cman config
Yes, I suspect the problem is that the node is 'bouncing' as it joins
the cluster.
Causes of this are usually to do with either a) startup scripts (eg some
Xen ones) taking he interface down and then up after openais has started
or b) "intelligent" switches taking too long to recognise the multica
Hi,
Thanks for your response Marc. It seems that we are the only ones facing
this
problem ... ?
I saw in changelog a fix :
- A dirty node is now prevented from joining the cman cluster.
It could be related to our problem ... because when launching cman
on the second node, the node is labeled as
Hi,
I'm having "exactly" the same problem with some clusters (Version:
cman-2.0.84-2.el5_2.2,..)
Is it so that if you reboot the node that was killed, it will rejoin the
cluster without being killed? And does it only happen if you start the whole
cluster from scratch?
I didn't figure out the
Hi
Release : cman-2.0.95-1.el5
(but same problem with 2.0.98)
I face a problem when launching cman on a two-node cluster :
1. Launching cman on node 1 : OK
2. When launching cman on node 2, the log on node1 gives :
cman killed by node 2 because we rejoined the cluster without a full
restart
