HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- cmquerycl fails with error
Operating System - HP-UX
1833883
Members
1853
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
02-18-2008 07:21 AM
02-18-2008 07:21 AM
Hi Folks,
I'm trying to build a new two node cluster, and I'm issuing cmquerycl as the first step:
node1#cmquerycl -v -C /etc/cmcluster/clusternew.config -n node1 -n node2
Begin checking the nodes...
Looking for other clusters ... Done
Gathering configuration information .......... Done
Error: Unable to determine device configuration: failed to send device query to node node1
Error: Unable to determine device configuration: failed to send device query to node node2
Error: Unable to determine lvm configuration: failed to send lvm query to node node1
Error: Unable to determine lvm configuration: failed to send lvm query to node node2
Warning: Not probing node node1 as it is currently unreachable.
This may cause network partitions to be reported.
Warning: Not probing node node2 as it is currently unreachable.
This may cause network partitions to be reported.
Failed to gather configuration information.
The relevant entries are present in cmclnodelist as well as .rhosts (even though that does not matter)
The relevant entries are present in /etc/inetd.conf file and system is listening on ports designated for configuration and probe.
The product I have is:
B3935DA A.11.15.00 MC / ServiceGuard
The nodes are able to ping to each other with out trouble.
What am I missing? What should I do to get rid of that error?
Will assign points to deserving answers. Thanks!
Anoop
I'm trying to build a new two node cluster, and I'm issuing cmquerycl as the first step:
node1#cmquerycl -v -C /etc/cmcluster/clusternew.config -n node1 -n node2
Begin checking the nodes...
Looking for other clusters ... Done
Gathering configuration information .......... Done
Error: Unable to determine device configuration: failed to send device query to node node1
Error: Unable to determine device configuration: failed to send device query to node node2
Error: Unable to determine lvm configuration: failed to send lvm query to node node1
Error: Unable to determine lvm configuration: failed to send lvm query to node node2
Warning: Not probing node node1 as it is currently unreachable.
This may cause network partitions to be reported.
Warning: Not probing node node2 as it is currently unreachable.
This may cause network partitions to be reported.
Failed to gather configuration information.
The relevant entries are present in cmclnodelist as well as .rhosts (even though that does not matter)
The relevant entries are present in /etc/inetd.conf file and system is listening on ports designated for configuration and probe.
The product I have is:
B3935DA A.11.15.00 MC / ServiceGuard
The nodes are able to ping to each other with out trouble.
What am I missing? What should I do to get rid of that error?
Will assign points to deserving answers. Thanks!
Anoop
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2008 09:09 AM
02-18-2008 09:09 AM
Solution
The message "failed to send device query to node" has been seen in conjunction with configuration oversights based on the document "Editing Security Files for Serviceguard, March 2005" which is located at this site: http://docs.hp.com/en/6283/SGsecurityfiles.pdf
The files to focus on are /etc/hosts and /etc/nsswitch.conf on EVERY node in the cluster.
Insure that all fixed IPs on each node are listed in /etc/hosts
Insure that all fixed IPs are also aliased to the simply hostname of the server. <-- This last configuration requirement is -THE- most common cause of "permission denied" and errors such as the one that you are seeing.
The files to focus on are /etc/hosts and /etc/nsswitch.conf on EVERY node in the cluster.
Insure that all fixed IPs on each node are listed in /etc/hosts
Insure that all fixed IPs are also aliased to the simply hostname of the server. <-- This last configuration requirement is -THE- most common cause of "permission denied" and errors such as the one that you are seeing.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2008 10:56 AM
02-18-2008 10:56 AM
Re: cmquerycl fails with error
# more /etc/inetd.conf | grep auth
auth stream tcp6 wait root /usr/lbin/identd identd
#
Use "-k" option with cmquerycl to avoid disk probing.
auth stream tcp6 wait root /usr/lbin/identd identd
#
Use "-k" option with cmquerycl to avoid disk probing.
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