- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Cannot start
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2002 10:25 AM
06-21-2002 10:25 AM
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
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2002 10:31 AM
06-21-2002 10:31 AM
Re: Cannot start
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2002 10:39 AM
06-21-2002 10:39 AM
Re: Cannot start
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2002 10:49 AM
06-21-2002 10:49 AM
Re: Cannot start
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2002 10:52 AM
06-21-2002 10:52 AM
Re: Cannot start
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2002 10:58 AM
06-21-2002 10:58 AM
SolutionIf 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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2002 12:02 PM
06-21-2002 12:02 PM
Re: Cannot start
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-23-2002 06:27 AM
06-23-2002 06:27 AM
Re: Cannot start
IF i am at your place i will look on /etc/cmcluster/cmclnodelist file and /.rhosts files on both the servers.
Tx,
AR
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-23-2002 11:24 AM
06-23-2002 11:24 AM
Re: Cannot start
/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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2002 06:47 AM
06-24-2002 06:47 AM
Re: Cannot start
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2002 06:50 AM
06-24-2002 06:50 AM
Re: Cannot start
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