Re: Node2 kills node1 when it is booting ...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jakub Suchy wrote:
Hello,
this is a common problem which arised in past months in RHCS.

The usual solution is to let the nodes solve the problem naturally -
after the node is killed, it is usually fenced and rejoins back in OK
state after a reboot. You only have a problem if you are using manual
fencing...Don't...

See /etc/init.d/cman also, there is a new variable introduced in RHEL5.3
(and 5.2 errata), called FENCE_DELAY (or similar), try setting it to a
bit higher value. It tells how many seconds to wait for the nodes to
join the same fence domain before killing them.

Jakub

Thanks jakub, but if I change FENCED_MEMBER_DELAY param to, for example, 3600 seconds, when fenced daemon starts up ?? automatically or after 3600 seconds??



carlopmart wrote:
Hi all,

I need to setup another rhcs today with two nodes. But every times that I start second node, node1 returns this error:

cman killed by node 2 because we rejoined the cluster without a full restart

.. and cman stops on node1. Why?? I didn't find any solution under http://sources.redhat.com/cluster/wiki/FAQ/

 My nodes are rhel5.3



--
CL Martinez
carlopmart {at} gmail {d0t} com

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux