- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- cluster restart problem
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
09-17-2004 04:00 AM
09-17-2004 04:00 AM
I am making tests with my two node cluster . I have a A.11.14 over hp-ux 11.11 . If both nodes are running cluster works ok . If I shutdown the server 2 one node the cluster remain in the node 1 but if I halt the node 1 the cluster remains in an unknow state and I can not restart it again:
Athos:/var/adm/syslog> cmviewcl
cmviewcl : Cannot talk to all the nodes.
Cluster does not appear to be up
CLUSTER STATUS
BHS unknown
NODE STATUS STATE
Athos down unknown
Porthos unknown unknown
UNOWNED_PACKAGES
PACKAGE STATUS STATE AUTO_RUN NODE
pkg-oracle unknown unknown
pkg-bhs unknown unknown
Athos:/var/adm/syslog> cmruncl -v
cmruncl : Validating network configuration...
Gathering configuration information ......... Done
Not probing node Porthos as it is currently unreachable.
cmruncl : Network validation complete
The configuration file on node Porthos will not be checked.
Cannot reach node "Porthos".
Athos:/var/adm/syslog> cmvie3wcl
sh: cmvie3wcl: not found.
Athos:/var/adm/syslog> cmviewcl
cmviewcl : Cannot talk to all the nodes.
Cluster does not appear to be up
CLUSTER STATUS
BHS unknown
NODE STATUS STATE
Athos down unknown
Porthos unknown unknown
UNOWNED_PACKAGES
PACKAGE STATUS STATE AUTO_RUN NODE
pkg-oracle unknown unknown
pkg-bhs unknown unknown
For me is impossible in this state to start the cluster just with one node , why ?????
Is it possible to migrate from SG A.11.14 to A.11.15 ????
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-17-2004 04:16 AM
09-17-2004 04:16 AM
SolutionYou can force the cluster startup using only one node.
cmruncl -f -v -n node1
here node1 is the node on which you want to start the cluster when the other node "say node2" which is part of a 2 node cluster is unavailble for some reason.
Hope this helps.
Regds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-17-2004 04:08 PM
09-17-2004 04:08 PM
Re: cluster restart problem
is the second server is up and you can login from first server.
check the inetd.conf for the hacl-cfg entries on the servers.
regds,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2004 05:42 PM
09-18-2004 05:42 PM
Re: cluster restart problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2004 09:21 PM
09-18-2004 09:21 PM
Re: cluster restart problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2004 10:21 PM
09-19-2004 10:21 PM
Re: cluster restart problem
- what is the purpose of the hacl entries in the inetd.conf file ???? Is the inetd daemon the one who controls the cmcld heartbeat???Which port uses the heartbeat communication??
- how can I test if the heartbeat is running using linklook??? I have alwais used netstat and lsof to test it ..
Thanks again

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-22-2004 02:38 AM
09-22-2004 02:38 AM
Re: cluster restart problem
The hacl entries in inetd.conf are to start the cmclconfd daemons when the commands are run.
The hacl-hb port defined in /etc/services is used for cluster HB communications, i.e. port 5300. You can see if this is being used with a netstat command as you state.
P.S. Be very very careful when using cmruncl -f -n