After Power outage, SG failover node is NOT coming up

[Basheer_2]

Good Morning
HPUX 11.11
SG 11.16
2 node cluster

After power outage
pri came up but failover node is NOT coming up.
cmviewcl -l package
Error: Permission denied to 127.0.0.1
cmviewcl : Cannot view the cluster configuration. Either this node is not confi
gured in a cluster, or else there is some obstacle to viewing the configuration.
Check the syslog file for more information. For a list of possible causes, see
the ServiceGuard manual for cmviewcl.

Appreciate your help.

[Geoff Wild]

Is AUTOSTART_CMCLD set to 1 in /etc/rc.config.d/cmcluster?

can you do a cmrunnode?

Anything relevant in syslog?

Rgds...Geoff

[Basheer_2]

Thanks
Yes, it is set to 1
tried manually to bring up

# cmrunnode
cmrunnode : Unable to determine the nodes on the current cluster
cmrunnode : Either no cluster configuration file exists, or the file is corrupted, or cmclconfd is unable to run

[A. Clay Stephenson]

Well the first thing to check is whether the file /etc/cmcluster/cmclconfig exists. If so, then do a cksum of this file on a good node and compare it to the bad node. The files should be identical; if not, the file is corrupt.

[Enrico P.]

Hi,
could be your binary configuration file is corrupted.
Try to stop the cluster, move the binary file it in .old in both the node and run the cmcheckconf and cmapplyconf command to re-create an distribuite it.

Enrico

[Basheer_2]

Thanks
tried copy of cmclconfig, no luck

for now I can NOT stop and do cmapplyconf

[Mike Chisholm]

Since you are getting the "Permission denied" error I would check your /var/adm/inetd.sec file and make sure it is the same on both server wrt to the hacl-cfg entries. I assume cmviewcl works on the node that is still in the single node cluster, correct? You may try turning on inetd logging via the "inetd -l" command(it toggles the state each time you run it) and look in syslog for additional errors when you run the cmviewcl command.

Also take a look at the http://docs.hp.com/en/6283/SGsecurityfiles.pdf document and verify that the lan cards are setup with appropriate aliases.

[Basheer_2]

Thanks Mike

/var/adm/inetd.sec on pri has many entries
on failover node (the one not working) has only 1 entry.

[Kent Ostby]

So did Mike's advice get the node back up?

Sometimes when two nodes are power cycled in an outage, they come up close to the same time but not at the same time and that can cause problems with the autostart.

I'd suggest a 20 minute break to let them time out and then take a look at it. It's quite possible that they are having a different issue, but its something to keep in mind.

Also, try running your command from the other server.

Run "uptime" on both to make sure they are up in a high enough level.

Try doing "rlogin" (if you use .rhosts).

[Basheer_2]

Thanks

NO still same problem
PRI started
then after 2 hours, other one started