1830931 Members
2393 Online
110017 Solutions
New Discussion

Cannot start

 
SOLVED
Go to solution
Crystal_1
Frequent Advisor

Cannot start

Hi,

I have found that the cluster daemon cannot be started and the syslog messages are as follows:

cmrunnode : Unable to determine the nodes on the current cluster
cmrunnode : Either no cluster configuration file exists, or the file is corrupt
ed, or /usr/lbin/cmclconfd is unable to run
Unable to connect to the configuration daemon (cmclconfd) on node unixh110: Conn
ection refused
Local node is not currently configured in a cluster
ERROR: Unable to join cluster

Can anyone tell me why?

Tx, Crystal
10 REPLIES 10
John Poff
Honored Contributor

Re: Cannot start

Hello Crystal,

I have a few questions about your problem.

Have you taken a look at your cmclconfig file in /etc/cmcluster? Is it missing or corrupt (zero bytes maybe)? Which version of HP-UX and MG/SG are you running? Can you ping and remsh to the other nodes in the cluster?

JP
Crystal_1
Frequent Advisor

Re: Cannot start

Hi,

I checked the file cmclconfig and it is not readable. Actually, CONF is readable.

I don't know too much about this and I am learning. Can you tell me how to check for your questions with what commands?

Thanks for your help.
John Poff
Honored Contributor

Re: Cannot start

I'll be glad to try and help you.

When you do an 'ls -l' on the cmconfing file, it shouldn't be zero bytes. It is a binary file, so you probably won't be able to read it (more, etc.). Now, in your cluster, each of the nodes has to trust the other nodes. The way that happens is either by using .rhosts files (in root's home directory) that lists the other nodes in the cluster, or by using the cmclnodelist file (which is similar to .rhosts and is greatly preferred by some people). The cmclnodelist file just came about in the recent versions of ServiceGuard, so that's why it helps to know which version you are running. To get the version of MC/SG, do this:

swlist -l product | grep -i serv

This should show your version of MC/SG. You're looking for something like this:

ServiceGuard A.11.13 Service Guard

To get the version of HP-UX you are running, do this:

uname -a

Tell me what those give you and we'll go from there. The other wizards will pick up on this thread soon and you'll have lots of good (and better!) help.

JP
PIYUSH D. PATEL
Honored Contributor

Re: Cannot start

Hi,

You can check your cluster configuration thro the following command:

# cmcheckconf -k -v -c /etc/cmcluster/cmclconf.ascii

Here in the above command pls enter the name of your cluster configuration ascii file.

Was your cluster running properly before or are you trying to build a cluster.

Piyush
PIYUSH D. PATEL
Honored Contributor
Solution

Re: Cannot start

Hi,

If you are trying to set up a MCSG cluster then go thro the online docs on :

http://www.docs.hp.com/hpux/onlinedocs/B3936-90053/B3936-90053.html

Piyush
Sanjay_6
Honored Contributor

Re: Cannot start

Hi Crystal,

Do a ll for /etc/cmcluster. The files cmclconfig and cmclconfig have permission 600 and are owned by root:root.

Also make sure that you are able to do rlogin / remsh between the cluster nodes.

Hope this helps.

Regds
Amruth
Regular Advisor

Re: Cannot start

Hi,

IF i am at your place i will look on /etc/cmcluster/cmclnodelist file and /.rhosts files on both the servers.

Tx,
AR
If i am doing the same way you are doing to me then what is the difference between us.
Tim D Fulford
Honored Contributor

Re: Cannot start

This message means one of two things (in my experience)

/etc/cmcluster/clconfig file is coorupt or (or likely) the equivalences for the user has not been set up.

.rhosts & /etc/cmcluster/cmnodelist are the two main files for equivalences but also check that /etc/hosts, do not use DNS/NIS/anything else for inter-cluster node lookups as if it goes wrong you have a Single Point Of Failure (SPOF) which is why you you clustered it in the first place.

Tim
-
Crystal_1
Frequent Advisor

Re: Cannot start

All,

Thanks for your notes.

I have found that the application eTrust Access Control from Computer Associates blocks the MCSG. The situation is that MCSG cluster daemon couldn't start after eTrust starts up during the reboot. After the system starts up, recycling the eTrust (turn off and turn on) can enable MCSG to start up.

I am thinking there is something wrong with eTrust's startup. I still cannot figure out what causes the problem. I have opened a call to CA and see if they can find out the problem.

Thanks again, Crystal
Crystal_1
Frequent Advisor

Re: Cannot start

Besides,

We are not using .rhosts file, but cmnodelist. The MCSG is A.11.12.

Do you know if there is any patch for this?

Crystal