HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- "Error: Node app6 is refusing Serviceguard communi...
Operating System - Linux
1827810
Members
1926
Online
109969
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
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-25-2007 08:45 PM
02-25-2007 08:45 PM
"Error: Node app6 is refusing Serviceguard communication." from cmcheckconf
We are using the server app6 as our master for configuring the cluster, and are copying a configuration we have working in a separate cluster.
These are all running Red Hat Linux RHEL3
We have verified that cmclnodelist contains "app6 root"
We have also verified that "ping app6" works from app6 itself.
What should we be looking at?
These are all running Red Hat Linux RHEL3
We have verified that cmclnodelist contains "app6 root"
We have also verified that "ping app6" works from app6 itself.
What should we be looking at?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2007 10:42 PM
02-25-2007 10:42 PM
Re: "Error: Node app6 is refusing Serviceguard communication." from cmcheckconf
I would say your (x)inetd.conf & services files.. do they have the necessary ServiceGuard entries ?
Also, as described in http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=906175 , a running identd would also be important.
Cheers,
Wout
Also, as described in http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=906175 , a running identd would also be important.
Cheers,
Wout
an engineer's aim in a discussion is not to persuade, but to clarify.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-26-2007 03:33 PM
02-26-2007 03:33 PM
Re: "Error: Node app6 is refusing Serviceguard communication." from cmcheckconf
This may be in teh link that Wouter sent but just in case:
If you get an error message when doing a cmquerycl, cmapplyconf, or cmcheckconf indicating the Serviceguard cannot communicate with a node.
1. Usually this means that the firewall is set up incorrectly. Try turning off the firewall
2. Also, identd may not have started. "identd" is the service associated with pidentd (see #2). Make sure this is set to start automatically.
3. Check that the file cmclnodelist has been created and is set up correctly.
4. After you make all of the changes, reboot both nodes.
To debug cmnodelist - use the "+" as described int eh manual.
If you get an error message when doing a cmquerycl, cmapplyconf, or cmcheckconf indicating the Serviceguard cannot communicate with a node.
1. Usually this means that the firewall is set up incorrectly. Try turning off the firewall
2. Also, identd may not have started. "identd" is the service associated with pidentd (see #2). Make sure this is set to start automatically.
3. Check that the file cmclnodelist has been created and is set up correctly.
4. After you make all of the changes, reboot both nodes.
To debug cmnodelist - use the "+" as described int eh manual.
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
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP