- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: SG cmquerycl error
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
11-23-2009 01:58 PM
11-23-2009 01:58 PM
SG cmquerycl error
I'm trying to setup a cluster between two nones. I havve check all the networking and it seem to be correct, however please the the error below.
HPUX 11.31
Blade BL870
SG A.11.18.00
error:
Node hostname is refusing Serviceguard communication.
Please make sure that the proper security access is configured on node
hostname through either file-based access (pre-A.11.16 version) or role-based
access (version A.11.16 or higher) and/or that the host name lookup
on node hostnameresolves the IP address correctly.
cmcheckconf: Failed to gather configuration information
Thanks,
SP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-23-2009 02:00 PM
11-23-2009 02:00 PM
Re: SG cmquerycl error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-23-2009 02:01 PM
11-23-2009 02:01 PM
Re: SG cmquerycl error
hostname1 root
hostname2 root
sp,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-23-2009 02:08 PM
11-23-2009 02:08 PM
Re: SG cmquerycl error
--sp
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-23-2009 02:17 PM
11-23-2009 02:17 PM
Re: SG cmquerycl error
http://docs.hp.com/en/6283/SGsecurityfiles0903.pdf
and
http://docs.hp.com/en/5874/securingserviceguard0903.pdf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2009 09:46 AM
11-24-2009 09:46 AM
Re: SG cmquerycl error
cmdeleteconf: Unable to get cluster configuration information: Permission denied.
sp,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2009 12:19 PM
11-24-2009 12:19 PM
Re: SG cmquerycl error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2009 09:31 PM
11-24-2009 09:31 PM
Re: SG cmquerycl error
>>Unable to get cluster configuration information
"auth" line commented out in /etc/inetd.conf
#auth stream tcp6 wait bin /usr/lbin/identd identd
Serviceguard uses identd to validate Serviceguard commands are being performed by nodes in the cluster. If this line is disabled, Serviceguard commands will fail in various ways; one being the "security token exchange' error.
Aneesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-25-2009 08:13 AM
11-25-2009 08:13 AM
Re: SG cmquerycl error
Command:
cmquerycl -v -C cmclconfig.ascii -n nodename1 -n nodename2
output:
Permission denied to 127.0.0.1
Looking for other clusters ... Done
Node nodename1 is refusing Serviceguard communication.
Please make sure that the proper security access is configured on node
nodename1 through either file-based access (pre-A.11.16 version) or role-based
access (version A.11.16 or higher) and/or that the host name lookup
on node nodename1 resolves the IP address correctly.
Failed to gather configuration information.
Thanks in advance,
sp
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-25-2009 09:50 AM
11-25-2009 09:50 AM
Re: SG cmquerycl error
If you read the documents that Melvyn prescribed, you will know that /etc/hosts must list every fixed IP on each node, and alias them to the simple hostname of the hosting node (yeah - this sounds freaky but it works)
After uncommenting the auth line, or after any modification to /etc/inetd.conf, you must either stop and restart inetd (inetd -k; inetd) or at least have it re-read the inetd.conf file (inetd -c). (Repeat on the other node!)
As for the "Permission denied to 127.0.0.1"
error, insure the cmclnodelist format looks like this:
node1 root
node2 root
(note simple hostnames, and no IPs)
Put a "+" at the bottom for diagnostic purposes. Remove if after resolving the condition.
Verify the permissions an ownership of identd are correct.
At hpux 11.31, you should see these:
-r-xr--r-- 1 bin bin 82192 Nov 6 2007 /usr/lbin/identd
/etc/hosts must have this untouched line:
127.0.0.1 localhost loopback
If 'ps -ef' shows hanging 'cmclconfd -p' processes (they should terminate after 60 seconds of running a SG command, kill them and retry the command.
Servers 'ignited' from a "golden" Ignite/UX backup may get the golden server's /etc/cmcluster/cmclconfig file. If this is a new cluster build and that file exists already, delete it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-25-2009 12:14 PM
11-25-2009 12:14 PM
Re: SG cmquerycl error
Can we verify the physical layer ?
nwmgr --diagnose
Please paste in the results. Also, what does
cmscancl
...report under the lan section.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-25-2009 12:17 PM
11-25-2009 12:17 PM
Re: SG cmquerycl error
1. Change the cmclconfd entry in /etc/inetd.conf to appear as:
hacl-cfg stream tcp nowait root /usr/lbin/cmclconfd \
cmclconfd -c -i
2. Change the cmomd entry in /etc/inetd.conf to appear as:
hacl-probe stream tcp nowait root \
/opt/cmom/lbin/cmomd /opt/cmom/lbin/cmomd -i -f \
/var/opt/cmom/cmomd.log -r /var/opt/cmom
3. Restart inetd: “/etc/init.d/inetd restart”
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-30-2009 07:19 AM
11-30-2009 07:19 AM
Re: SG cmquerycl error
Here is the fix:
1) Move out the /dev/urandom file and check # mv /dev/urandom /tmp If this works then move the urandom file back to /dev and go to next step 2) Check 'rng' module status # kcmodule -v rng If state & state at next boot is as unused, then goto step 3
3) Load the module in kernel
# kcmodule rng=loaded
# kcmodule rng=best
After this try swinstall & swacl commands.
If the above method fails, then try restarting swagentd daemon
Thanks for all the help!
Sp,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2009 07:35 AM
12-08-2009 07:35 AM
Re: SG cmquerycl error
I've also had this problem and I suspect all 4 nodes in my metro cluster went down because of this because my Quorum server was also unreachable...
An indication that there's something wrong in the syslog might be this: cmclconfd[
I've ran kcmodule -v rng and it was scheduled to be loaded next boot but it does not get loaded after I reboot the machine so I'll have to keep this in mind. Or is there a fix for this?
Thanks again for the tip!
Wimmy