cmruncl error: Cluster is busy

[Chauhan Amit]

Hello Experts,

Getting Following Error while creating Single-Node Cluster.

cmruncl throws following error:

Waiting for cluster to form ....Cluster is busy right now, please try your request again later.


Syslog:

Mar 22 02:55:25 vmia3 cmcld[3765]: Reason: Ran out of time for manually starting
the cluster
Mar 22 02:55:22 vmia3 cmcld[3765]: Attempting to form a new cluster
Mar 22 02:55:25 vmia3 above message repeats 16 times
Mar 22 02:55:25 vmia3 cmsrvassistd[3768]: Unable to send 64 bytes (Software caus
ed connection abort).
Mar 22 02:55:22 vmia3 cmcld[3765]: Beginning standard election
Mar 22 02:55:25 vmia3 above message repeats 16 times
Mar 22 02:55:25 vmia3 cmsrvassistd[3768]: Unable to notify Serviceguard main dae
mon (cmcld): Software caused connection abort
Mar 22 02:55:25 vmia3 cmsrvassistd[3768]: The cluster daemon aborted our connect.

SG Version - A.11.17 on 11.23

Has anybody seen these errors before.Any help will be much appreciated.

-Amit

[RAC_1]

cmviewcl
does it report anything. did cmquerycl report any errors?

[Chauhan Amit]

RAC

cmquerycl and cmapplyconf doesn't throw any errors.

cmviewcl shows Single node Cluster as Down.

-Amit

[Sameer_Nirmal]

Hi Amit,

It looks like the problem with SG required ports are not available. The message shows the "cmsrvassistd" daemon is not able to communicate with "cmcld". Check the ports used by SG in /etc/services specially hacl* ports. They should not be blocked.
http://docs.hp.com/en/B3935-90091/B3935-90091.pdf

Check if the ports are open at server and in "LISTEN" state using
# netstat -anf inet

[dhananjay_1]

Hello Amit ,

tried to start up a single-node cluster like

# cmruncl -f -n nodeA

This gave a more detailed error message .

delete the /var/adm/cmcluster/.cm_start_time file and touch it.

# rm /var/adm/cmcluster/.cm_start_time

# touch /var/adm/cmcluster/.cm_start_time

reboot the node.

Hope this will solve this issue.

Dhananjay

[Chauhan Amit]

Re-Installing SG and the Required Patches did the trick. Closing the Thread. Thanks for your suggestions.