Not able to run cmruncl to start cluster

[Sushil Singh_1]

Hi all,
When ever I run cmruncl, I ge the following output
# cmruncl
cmruncl : Waiting for cluster to form.......................
cmruncl : Cluster did not form. Check the syslog file for information.

When I check the syslog, I see the following things.
Mar 27 15:53:15 greategg cmcld: Attempting to form a new cluster
Mar 27 15:53:16 greategg cmtaped[3840]: cmtaped: There are no ATS devices on this cluster.
Mar 27 15:54:15 greategg cmcld: Cluster formation failed
Mar 27 15:54:15 greategg cmcld: Reason: Ran out of time for manually starting the cluster
Mar 27 15:54:15 greategg cmcld: This node (greategg) has ceased cluster activities.
Mar 27 15:54:15 greategg cmcld: Daemon exiting
Mar 27 15:54:15 greategg cmtaped[3840]: Lost connection to the cluster daemon.
Mar 27 15:54:15 greategg cmtaped[3840]: cmtaped terminating. (ATS 1.14)


Just wondering if someone can help out here.

Thanks
Sushil Singh

[Sridhar Bhaskarla]

Sushil,

Make sure your heartbeat connections are up and you are able to ping from one server to the other.

-Sri

[Sanjay_6]

Hi Sushil,

Look at the node timeout variable in your cluster configuration. If possible increase the node timeout value, reapply the cluster binaries and then restart the cluster. Also do a nslookup from each cluster node and make sure the other cluster nodes names and ip addresses can be resolved. The problems looks like it is related to network traffic.

Hope this helps.

Regds

[Sushil Singh_1]

Hi Sri,
I am able to ping using the heartbeat IP. But still not able to bring it up.

# ping 200.200.200.18
PING 200.200.200.18: 64 byte packets
64 bytes from 200.200.200.18: icmp_seq=0. time=0. ms
64 bytes from 200.200.200.18: icmp_seq=1. time=0. ms


Thanks
Sushil

[Sanjay_6]

Hi Sushil,

another thing to look for is to see if you have the same version of cmcld on all the nodes if you are trying to start multiple nodes in the cluster.

Here is a link on how to change the node timeout if that is a problem,

http://us-support3.external.hp.com/cki/bin/doc.pl/sid=1694f98314cf5d9116/screen=ckiDisplayDocument?docId=200000046942489

Hope this helps.

Regds

[Jeff Schussele]

Hi,

Sounds to me like you've got Advanced Tape Services setup for MC/SG & you've got a config problem.
Run #stchecckconf

See the following link:

http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B3936-90032/B3936-90032_top.html&con=/hpux/onlinedocs/B3936-90032/00/00/10-con.html&toc=/hpux/onlinedocs/B3936-90032/00/00/10-toc.html&searchterms=ATS&queryid=20020327-133146

HTH,
Jeff

[Dave La Mar]

If you have made changes, be sure to perform the build, compile, and distribute.

Sorry, this is my fourth try at trying to respond. If the others ever show up, my apologies.

Best of luck.
dl

[Helen French]

Hi Sushil,

One work around:

Do you have the patch PHSS_26180 installed ? This is what the patch description says:

The kernel tuneable for stape reserve/release functionality, st_ats_enabled, currently defaults to enabled on 11.0 and 11.i HP-UX systems. In the near future, this tuneable will be defaulted to disabled. Currently, ATS does not check the state of this tuneable before proceeding with shared tape operations.

Resolution:

Added check in shared tape daemon cmtaped that causes it to treat node has having no ATS tape devices if kernel tuneable st_ats_enabled is disabled on node. Also added check in ATS configuration commands to block SG shared tape configuration if one or more nodes in cluster has kernel tuneable disabled.

HTH,
Shiju

[Sushil Singh_1]

Hi all,
I don't have any ATS (Advance Tape Service) and I am not so sure wht cmtaped is looking for it. I cannot apply patch because that required SG 11.13 which would be in conflict with costumers. Is there any way i can disable the cmtaped ?

Thanks
Sushil Singh

[Jeff Schussele]

Sushil,

This is a kernel tunable parameter that needs to be set to 0 (zero).
This can be set thru SAM I believe.

See the following link:

http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/TKP-90202/TKP-90202_top.html&con=/hpux/onlinedocs/TKP-90202/00/01/154-con.html&toc=/hpux/onlinedocs/TKP-90202/00/01/154-toc.html&searchterms=st_ats_enabled&queryid=20020327-140903

Rgds,
Jeff

[Sridhar Bhaskarla]

Sushil,

I wouldn't worry about ATS devices.

Try to re-apply the configuration. It is not going to harm anything.

1. cmdeleteconf
2. cmcheckconf
3. cmapplyconf

and try starting the cluster.

-Sri

[Barry Feinberg]

Sushil,

I had the same error message a few days ago. I found 2 problems. first make sure files /usr/sbin/snmpd and /usr/sbin/snmpdm have at least _r_xr__r__ permissions. Older version of serviceguard need snmp running. second problem was a bug in serviceguard where a bogus ping was coming from another node in the cluster. Try booting the other nodes one at a time.

[MANOJ SRIVASTAVA]

Hi Sushil

Just in case check for the setting of the Network Port , you can do some ftp of big files to check whether the through put is fine, sometimes it happens that bcoz of mismatch u can still communicate but there will be problems in proper communications.

Also check netstat -i for errors collisions.


Manoj Srivastava