Kbase P128080: Clients unable to connect to database server when server attempts to bind to port defined in service
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
02/08/2010 |
|
Status: Verified
SYMPTOM(s):
Clients unable to connect to database server when server attempts to bind to port defined in services file.
Clients cannot connect to the database
No servers are available. Try again later. (1154)
Error <read/writing> socket, ret=<n>, errno=<n>. (778)
** There is no server active for database <database> on -H <hostname> -S <servicename>. (704)
The server or the system has no more resources. Try a larger -n. (748)
Disconnected from server because database name was incorrect. (437)
** Server rejected login. (700)
Promon R&D, 1, 3 shows remote servers with pending user connections
netstat -na do not show port as LISTENING
Database log file shows Remote Servers being spawned but no clients connect to them
In 10.1C and later, message error 12451 is put into the database log by the client that it is unable to connect to the server
A remote client was unable to connect to server <server-number> using port <port-number> - please check the port. (12451)
FACT(s) (Environment):
The default ports for -minport -maxport are not listed in the services file.
Default values of -minport and -maxport parameters are being used as these parameters are not explicitly specified at startup
Does not affect _sqlsrv2 process because it uses a different code set and doesn't block on ports defined in the services file.
Linux
Progress 9.x
OpenEdge 10.x
CAUSE:
Bug# OE00171739
FIX:
The workaround is to implement the -minport -maxport startup parameters to ensure that Remote Servers are spawned in a port range that does not include ports which are already reserved otherwise (e.g. in the services file).