- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: single node cluster permission denied to itsel...
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
тАО03-01-2006 09:43 AM
тАО03-01-2006 09:43 AM
single node cluster permission denied to itself
Permission denied for the host to talk to itself..?
cmapplyconf gives "Error: Permission denied to "
But then "Completed the cluster creation."
cmruncl then starts off normally, but then "Waiting for cluster to form" followed by "Cluster did not form. Check the syslog file for information."
cmviewcl shows the cluster up and running though.
syslog shows cluster as formed as single node followed by several lines like this:
Mar 2 09:15:45
The IP 10.26.194.16 is the IP of the node itself!
-What's going on here??
thanks,
Peter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-01-2006 09:53 AM
тАО03-01-2006 09:53 AM
Re: single node cluster permission denied to itself
Did you put an entry fo rthis server in cmclnodelist at cluster creation time? including ALL of the ip/hostanmes for the configured NIC's on tgheh ost?
Also take a read through the Security papers on the docs page:
http://docs.hp.com/en/ha choosing Serviceguard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-01-2006 10:56 AM
тАО03-01-2006 10:56 AM
Re: single node cluster permission denied to itself
I suppose I didn't think it was neccesary for a one node cluster.. :-)
So I wiped out ServiceGuard and started over,
putting
And now it doesn't even generate the config file.
"Error: Node
And then
..-At least without the cmclnodelist I could create a cluster and start it.. ;-)
The hostname is in the .rhosts
It is also in /etc/hosts
Only one network interface is configured.
This is all very strange.
What is the mechanism used by ServiceGuard when it creates the cluster?
(We have built a couple of two node clusters before and they weren't this stubborn)
Peter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-01-2006 11:03 AM
тАО03-01-2006 11:03 AM
Re: single node cluster permission denied to itself
cmclconfd
See "Editing Security Files for Serviceguard"
http://www.docs.hp.com/en/6283/SGsecurityfiles.pdf
Rgds...geoff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-01-2006 11:35 AM
тАО03-01-2006 11:35 AM
Re: single node cluster permission denied to itself
Can't see why this would make a difference, because hostnames were resolving fine anyway..
But apperantly it did. :-)
This was not needed on the other clusters we built, but maybe there is some subtle version difference?
Thanks everyone
Peter