HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Problem in starting the alternate machine in a...
Operating System - HP-UX
1834020
Members
2782
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
12-14-2003 04:41 PM
12-14-2003 04:41 PM
Hi masters,
I have found one problem while trying to run cmrunnode from alternate client in a two node cluster.
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
Gave up attempting to receive a connection from Beta3
Failed to lookup /cluster in configuration database.
Fail to load data from configuration database
The package is up and running and the status of alternate link is shown halted in cmviewcl.
The cmviewcl is getting hanged while issued from Alternate Machine
Pls help in solving this
regds
sgk
I have found one problem while trying to run cmrunnode from alternate client in a two node cluster.
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
Gave up attempting to receive a connection from Beta3
Failed to lookup /cluster in configuration database.
Fail to load data from configuration database
The package is up and running and the status of alternate link is shown halted in cmviewcl.
The cmviewcl is getting hanged while issued from Alternate Machine
Pls help in solving this
regds
sgk
Engineer
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2003 05:13 PM
12-14-2003 05:13 PM
Solution
What it looks like is that the /etc/cmcluster/cmclconfig on the other node is corrupt. You can try to get the configuration and then re-apply the configuration on the other node. Do this.
1. run cmgetconf and get the present cluster configuration.
#cmgetconf -v -c outputfile
2. If it doesn't have the alternate node, edit the file and put that node too in the outputfile
3. Then cmcheckconf -v -C outputfile
4. cmapplyconf -v -C outputfile
This will add the node to the cluster and rebuild the cluster configuration on the alternate node
1. run cmgetconf and get the present cluster configuration.
#cmgetconf -v -c
2. If it doesn't have the alternate node, edit the file and put that node too in the outputfile
3. Then cmcheckconf -v -C outputfile
4. cmapplyconf -v -C outputfile
This will add the node to the cluster and rebuild the cluster configuration on the alternate node
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-15-2003 04:26 AM
12-15-2003 04:26 AM
Re: Problem in starting the alternate machine in a cluster
Do you have the correct entries in your host equivalency file?
check root's .rhosts, or more likely /etc/cmcluster/cmclnodelist
The file must contain entries for ALL nodes in hte cluster.
check root's .rhosts, or more likely /etc/cmcluster/cmclnodelist
The file must contain entries for ALL nodes in hte cluster.
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP