Unable to determine the nodes on the current cluster

[Taurian]

Please help me out with the following issue.

I am trying to run the cluster on the failover node as the primary node is down.

cmrunpkg command gives the following messages:
---------
# cmrunpkg -v -n ahlprdap dbciPRD
cmrunpkg : Unable to determine the nodes on the current cluster
cmrunpkg : Either no cluster configuration file exists, or the file is corrupted, or cmclconfd is unable to run
Unable to get local cluster configuration.
---------


And cmruncl command gives the following messages:
---------
cmruncl -v -f -n ahlprdap
Warning: Unable to get local cluster configuration.
cmruncl : Unable to determine nodes on the current cluster.
Either no cluster configuration file exists, the file is corrupted,
cmclconfd is unable to run, or user root on node ahlprdap
doesn't have access to view the configuration.
---------


Other posts on this topic have not been able to resolve my issue. Kindly help in this regard. Let me know what information you need. Thanks.

[R.K. # · Accepted solution]

Helloo..

Do you have any ascii and binary file for cluster config under /etc/cmcluster ?
Do you have any file like cmclnodelist under /etc/cmcluster ?
Was the package ever failed over successfully to this (sec) node ?

Looks like you need to try few things before reaching final conclusion.
# cmquerycl -v -C /etc/cmcluster/cmclconf.new_ascii -n node1 -n node2
# cmcheckconf -v -C /etc/cmcluster/cmclconf.ascii

[Victor Fridyev]

Hi,

Try to restart the cluster with /sbin/init.d/cmcluster stop/start.
If everything is OK, check whether the package is configured properly on the secondary node.
I'm afraid that cluster files are not synchronized on the cluster nodes. In this case you'll have to rebuild the cluster.
HTH

[Taurian]

Hi folks,

Thanks for the reply.

The cluster was working fine yesterday on this node. I ran it with the "cmruncl" command. Therefore, the configuration was OK till yesterday.

The customer admin might have restarted the machine without halting the cluster.

Please let me know the possibilities in light of the above information. Thanks.

[johnsonpk]

Hi Taurian,

what about the status of second node ?
can you check following things on both node and compare
1)ps -ef |grep -i cm
2)cmviewcl from both nodes
3)ll /etc/cmcluster/cmclconfig output from both node.

in case cluster configuration is corrupted ,you can try copying cmclconfig from working node

Regard!
Johnson

[ManojK_1]

Hi,

Please verify the folder /etc/cmcluster in cluster nodes that all the required configuration files are available.Missing files will cause the issue.

Another thing, if you want to start the cluster when one of the cluster node is down. you have to issue the following command to start the cluster.

cmruncl -v -n

Otherwise the cmcld daemon check for the availablity of cluster nodes during cluster start and will fail if any of the cluster node unavaialable.

Manoj K

[Taurian]

Hi folks,

Thanks for your replies. We have fixed the issue by restoring the '/etc/cmcluster' folder as all the files were corrupted and reporting wrong check-sums.

[Taurian]

Hi folks,

Thanks for your replies. We have fixed the issue by restoring the '/etc/cmcluster' folder as all the files were corrupted and reporting wrong check-sums.