Clients unable to connect to database server when server attempts to bind to ports defined in services file.

« Go Back

Information

Title	Clients unable to connect to database server when server attempts to bind to ports defined in services file.

URL Name	Clients-unable-to-connect-to-database-server-when-server-attempts-to-bind-to-ports-defined-in-services-file

Article Number	000128002

Environment	Product: OpenEdge Version: 10.x, 11.x, 12.x OS: All supported platforms

Question/Problem Description

Clients are unable to or cannot connect to database.
Client takes several attempts to be able to connect to database.
Broker is unable to spawn server when server attempts to bind to port defined in services file.
Database log file shows Remote Servers being spawned but no clients can connect to them.
Default values of -minport and -maxport parameters are being used as these parameters are not explicitly specified in database startup parameters.
OpenEdge 10.1C and later, message error 12451 is written to the database log by the client that it is unable to connect to the server when it is started for that client-server connection.

Steps to Reproduce

Clarifying Information

netstat -na does not show the port as LISTENING

PROMON > R&D > 1 > 3. Servers shows remote servers with Pending user connections.

Error Message	Errors received by the client include: Can not connect to database server errno = 0 (1432) Error <read/writing> socket, ret=<n>, errno=<n>. (778) There is no server active for database <database> on -H <hostname> -S <servicename>. (704) No servers are available. Try again later. (1154) 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) Errors that can be found in the database log file A remote client was unable to connect to server <server-number> using port <port-number> - please check the port. (12451) Server cannot find a free port for a TCP socket. (1159) BROKER: Could not spawn a server. (1890)

Error Message

Errors received by the client include:

Can not connect to database server errno = 0 (1432)
Error <read/writing> socket, ret=<n>, errno=<n>. (778)
** There is no server active for database <database> on -H <hostname> -S <servicename>. (704)
No servers are available. Try again later. (1154)
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)

Errors that can be found in the database log file

A remote client was unable to connect to server <server-number> using port <port-number> - please check the port. (12451)
Server cannot find a free port for a TCP socket. (1159)
BROKER: Could not spawn a server. (1890)

Defect Number	Defect PSC00203374 / OE00171739

Enhancement Number

Cause

Remote 4GL/ABL servers are spawned in the -minport -maxport range, without first checking if the port is reserved in the /etc/services.

Resolution

Upgrade to OpenEdge 10.2B08, 11.2 or later.

For Database Remote ABL Server (_mprosrv), ensure that Remote Servers are spawned in a port range that are not included on ports already listed for Services in the /etc/services file, by configuring the -minport and -maxport database startup parameter range for remote servers on the login broker. For further information refer to Article:

minport maxport reservation in etc/services

Workaround

Notes

Keyword Phrase

Last Modified Date	11/20/2020 7:26 AM