Operating System - HP-UX
1832308 Members
2382 Online
110041 Solutions
New Discussion

Error: Unable to get a socket for server1

 
SOLVED
Go to solution
Manuales
Super Advisor

Error: Unable to get a socket for server1


I'd like to know why appear the error about socket ... i mean, how can i know what is the socket ? and how can i start it?

server1:/etc/cmcluster->cmcheckconf -C sap.ascii

Begin cluster verification...
Error: Fail to bind with socket due to errno 227
Error: Unable to get a socket for server1: Can't assign requested address
Error: Unable to connect to the configuration daemon (cmclconfd) on node server1: Connection timed out
cmcheckconf : Unable to obtain configuration information: No such device or address.
3 REPLIES 3
Peter Godron
Honored Contributor
Solution

Re: Error: Unable to get a socket for server1

Hi,
what are the results of:
cmquerycl ?
Has anything been changed on the set-up?
Wouter Jagers
Honored Contributor

Re: Error: Unable to get a socket for server1

In several other threads, you & your colleagues are facing some other issues.

We've seen questions like 'What is a cluster', 'What is a configuration file' and some more.

I think it would be helpful if you could tell us about your environment a little:

- Are you working on an existing (running/not-running) cluster ?
- Are you currently setting up some clustered systems ?
- Are you working on existing, non-clustered systems ?

Some answers to these questions will help us help you better ;-)

Cheers
an engineer's aim in a discussion is not to persuade, but to clarify.
Jaime Bolanos Rojas.
Honored Contributor

Re: Error: Unable to get a socket for server1

Manuales,

Make sure that the IP addresses in the /etc/hosts file are pointing to the correct locations.

Suerte con el cluster,

Jaime.
Work hard when the need comes out.