Fail to Start Global Heartbeat for OCFS2 Cluster: o2cb: heartbeat region could not be found region UUID
Error:
When starting the OCFS2 cluster service, a "region could not found" error is shown:
# /sbin/o2cb.init online
checking debugfs...
Setting cluster stack "o2cb": OK
Registering O2CB cluster "cluster-name": OK
Setting O2CB cluster timeouts : OK
Starting global heartbeat for cluster "cluster-name": Failed
o2cb: Heartbeat region could not be found XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Stopping global heartbeat on cluster "cluster-name": OK
Solution
1) List the available OCFS2 volumes and select one as the Global Heartbeat
# mounted.ocfs2 -d
Device Stack Cluster F UUID Label
/dev/sdX o2cb cls G XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX lab-1
/dev/sdY o2cb cls G YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY lab-2
2) Edit the file /etc/ocfs2/cluster.conf and change the region to the new UUID (Ex: YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY).
region =YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
3) Restart the cluser service
# /sbin/o2cb.init online
Or
/etc/init.d/o2cb online
4) Check that the service has started properly
# /sbin/o2cb.init status
Or
/etc/init.d/o2cb status
The above has to be performed on all nodes of cluster.
To get cluster information view below file
cat /etc/ocfs2/cluster.conf
Post a Comment
Post a Comment