Red Hat Bugzilla – Bug 230972
Qdisk daemon unable to be started on all members in Xen cluster setup
Last modified: 2018-10-19 15:51:34 EDT
Description of problem:
Starting qdisk service fails on all Xen domU cluster members (2-node cluster).
cluster.conf configuration as follows:
<quorumd device="/dev/sdb" interval="1" label="quorum" min_score="3" tko
<heuristic interval="2" program="ping b -c1 -t1" score="1"/>
Version-Release number of selected component (if applicable):
Configure qurourm device via system-config-cluster. Create quorum disk seen by
all members via mkqdisk command. Attempt to start qdiskd daemon fails.
Steps to Reproduce:
1. Create cluster with quorum device via system-config-cluster
2. Add in apprppriate heuristics
3. Start cman services - successful
4. Start qdiskd service -fails with errror
"Could not determine local node ID; cannot start"
Qdiskd fails to start so quorum device cannot be used as part of cluster.
Qdiskd starts successfully and quorum device part of cluster, seen via clustat
command. Optional status file also updated as specified in cluster.conf.
*** Bug 230971 has been marked as a duplicate of this bug. ***
This is fixed in 4.5/5.1, or should be. It may warrant an errata against 5.0.
Can the updated packages be made available so I may test? I'm assuming it's an
update to the cman package?
I have some cman & cman-kernel packages with just qdisk-required updates for
42.0.3 & 42.0.8 RHEL4 errata kernels here:
Oh - I missed that this is RHEL5. I'll build something shortly.
Created attachment 149344 [details]
update patch for RHEL5.0 qdisk -> RHEL5 stable development
Hi! I got the same Problem with RHEL5. Will there be an errata or how can i get
a supported fix?
same problem on FC6
Fixing Product Name. Cluster Suite was merged into Red Hat Enterpise Linux for
5.0. In addition dlm, fence and ccs were merged into the cman package, so
bugzilla should reflect package name where those utilities are located.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Any news if there will be an official errata for this problem?
This is fixed in 5.1 beta - give it a spin?
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.