- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: Node xxxx is refusing Serviceguard communicat...
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
Discussions
Discussions
Forums
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
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
тАО02-28-2008 09:38 AM
тАО02-28-2008 09:38 AM
Node xxxx is refusing Serviceguard communication
another refusing error. here are my details.
RHEL 5
SG A.11.18.01-0.rhel5
xinetd intalled
identd installed
cmquerycl -v -L /dev/dm-0 -n sgj-bd1 -n sgj-bd2 -C mysqlcl.conf
Looking for other clusters... done
Node sgj-bd2 is refusing Serviceguard communication
Please make sure....(etc etc)
my /etc/hosts (on both nodes)
127.0.0.1 localhost.localdomain localhost
192.168.248.5 sgj-bd1.dom1.com sgj-bd1
192.168.248.7 sgj-bd2.dom1.com sgj-bd2
10.10.10.10 sgj-bd1.hbone sgj-bd1
10.10.10.11 sgj-bd2.hbone sgj-bd2
Telnet to localhost 5302 is ok on both sides.
no firewall of any kind enabled.
/var/log/messages (on sgj-bd1)
xinetd[4206]: START: hcl-cfgupd pid=4211 from:127.0.0.1
xinetd[4206]: EXIT: hacl-cfgupd status=0 pid=4211 duration=15(sec)
/var/log/messages (on sgj-bd2)
xinetd[4267]: START: hacl-cfgupd pid=4271 from=192.168.248.5
xinetd[4267]: EXIT: hacl-cfgupd status=0 pid=4271 duration=15(sec)
So it seems the first node is reaching the second, but is refused.
I have tried restarting the servers, xinetd,identd and still no clue.
I am installing two SG clusters and I had a similar error in the apache cluster. It was fixed by simply restarting identd on one node. However on this cluster i am tired of rebooting/restaring.
Any additional comments on this one?
Thanks in advance,
Erick Perez
Panama.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-28-2008 02:45 PM
тАО02-28-2008 02:45 PM
Re: Node xxxx is refusing Serviceguard communication
Not to be a pain but its RTFM time. This is caused by security not being set up correctly on the problem node. Probably not a firewall, maybe a cmnodelist or hostname/dns resolution issue.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-28-2008 04:17 PM
тАО02-28-2008 04:17 PM
Re: Node xxxx is refusing Serviceguard communication
both cmclnodelist are exactly the same on both nodes.
no firewall was or is enabled on the nodes.
ping on each interface is ok.
what other security should I check?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-29-2008 01:13 AM
тАО02-29-2008 01:13 AM
Re: Node xxxx is refusing Serviceguard communication
Therefore I suggest you install the latest 11.18 patch SGLX_00222 (or SGLX_00223, SGLX_00224 depending on your architecture) since this fixes a defect where aliases were not recognised:
32. Defect: QXCR1000747462
If the primary names the IP addresses on a cluster node
resolve to do not match the hostname of the node then
Serviceguard commands fail. i.e. it is not possible to
configure the hostname as an alias as described in
the "Configuring IP Address Resolution" section of the
manual.
That is certainly the next step I'd try.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-29-2008 05:27 AM
тАО02-29-2008 05:27 AM
Re: Node xxxx is refusing Serviceguard communication
I cannot seem to find it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-01-2008 06:01 PM
тАО03-01-2008 06:01 PM
Re: Node xxxx is refusing Serviceguard communication
******before******
my /etc/hosts (on both nodes)
127.0.0.1 localhost.localdomain localhost
192.168.248.5 sgj-bd1.dom1.com sgj-bd1
192.168.248.7 sgj-bd2.dom1.com sgj-bd2
10.10.10.10 sgj-bd1.hbone sgj-bd1
10.10.10.11 sgj-bd2.hbone sgj-bd2
******AFTER and working******
my /etc/hosts (on both nodes)
127.0.0.1 localhost.localdomain localhost
10.10.10.10 sgj-bd1.hbone sgj-bd1
10.10.10.11 sgj-bd2.hbone sgj-bd2
192.168.248.5 sgj-bd1.dom1.com sgj-bd1
192.168.248.7 sgj-bd2.dom1.com sgj-bd2
Please note that the only thing I did was to move the 192. hosts from the top of the file to the bottom. First I was thinking it was a DNS issue, but the DNS servers resolve perfectly.
Also, it was mentioned there are patches to SG. Where? I cannot find a downloadable area for such patches (linux).
Thanks in advance for your comments.
Erick.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-03-2008 12:42 AM
тАО03-03-2008 12:42 AM
Re: Node xxxx is refusing Serviceguard communication
emha.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-03-2008 02:09 AM
тАО03-03-2008 02:09 AM
Re: Node xxxx is refusing Serviceguard communication
You can find the patches by clicking on the patch database link at http://www11.itrc.hp.com/service/patch/mainPage.do from the ITRC home page and entering the patch names in search field at the top which is entitled "find a specific patch". You should then find the patches.
The link for SGLX_00222 is http://www12.itrc.hp.com/service/patch/patchDetail.do?admit=109447627+1204538815436+28353475&patchid=SGLX_00222&sel=%7Blinux%3Aredhat%3A5ap%2C%7D&BC=main%7Csearch%7C (assuming this works from your account).
I think the most likely reason for your changing allowing things to work is that timeings are affected although without seeing your exact configuration it is hard to say. It is certainly unusual to see a system be a member of multiple domains like this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-03-2008 03:44 AM
тАО03-03-2008 03:44 AM
Re: Node xxxx is refusing Serviceguard communication
is the RHEL5 update 1?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-03-2008 07:04 AM
тАО03-03-2008 07:04 AM
Re: Node xxxx is refusing Serviceguard communication
John: to help the forums, what kind of complete information do i need to write here so it can be of help to others?
So far, what I can tell is this:
FIRST HOST
hostname: sgj-bd1
OS: RHEL 5 (stock, not updated yet)
SG A.11.18 RHEL 5
xinetd intalled, running
identd installed, running
Ethernet interfaces:
lo/127.0.0.1 localhost.localdomain localhost
bond0/192.168.248.5 sgj-bd1.dom1.com sgj-bd1
eth2 / 10.10.10.10 sgj-bd1.hbone sgj-bd1
Netmask: 255.255.255.0
gateway: 192.168.248.1
dns: 192.168.248.2 / 192.168.248.3
dom1.com is a valid internal domain (replaced for security reasons)
eth2 and eth3 are hearbeats only, crossover, not routed.
eth0 and eth1 are the bonding interfaces.
As far as the second host, is exactly the same execept for the hostname and ipaddress.
hostname: sgj-bd2
OS: RHEL 5 (stock, not updated yet)
SG A.11.18 RHEL 5
xinetd intalled, running
identd installed, running
Ethernet interfaces:
lo/127.0.0.1 localhost.localdomain localhost
bond0/192.168.248.7 sgj-bd2.dom1.com sgj-bd2
eth2/10.10.10.11 sgj-bd2.hbone sgj-bd2
content of cmclnodelist on both nodes
sgj-bd1 root
sgj-bd2 root
Thanks to all for your kind help.