Consultor Eletrônico



Kbase P132208: Remote clients cannot connect to database due to error 748 - database startup parameters are misconf
Autor   Progress Software Corporation - Progress
Acesso   Público
Publicação   7/29/2010
Status: Verified

SYMPTOM(s):

Cannot connect remote users to database due to error 748

The server or the system has no more resources. Please contact Progress Technical Support. (748)

No servers are available. Try again later. (1154)

Promon against the database at the time of the 748 errors show 5 servers that have 0 users connected.

The 5 servers have 1 or more Pending Connections even though no users are logged into these server processes.

Remote connections performed on the same machine as the database with the -H and -S parameter fail periodically with 437 error.

Disconnected from server because database name was incorrect. (437)

** Server rejected login. (700)

437 and 700 error occur when remote client attempts to connect to one of the servers that have pending connections without any users attached to them.

Database log file contains errors from when the database was being started.

Server cannot find a free port for a TCP socket. (1159)

4GL server process terminated. (8837)

-minport and -maxport parameters are not being used to specify range for ports for each of the brokers.

Using promon to terminate these remote servers does not resolve the issue.

FACT(s) (Environment):

Sun Solaris SPARC
RedHat Enterprise Linux 4.0
Progress 9.1E04 Service Pack
OpenEdge Database Category: Configuration
Can connect local users to the database.
Firewall not being used.
Multiple brokers being started for the database.
Brokers do not have a specified ServerType.
Database name was entered correctly when the 437 error occurred.

CAUSE:

Database startup parameters for -n, -Ma, -Mn, -Mpb are misconfigured and the -minport and -maxport parameters are not being used to specify range for ports for each of the brokers.

FIX:

1. Configure multiple brokers using solution P7843, "How to configure a secondary SQL-92 Broker for Progress 9.1D and above" to ensure that calculations for client / server ratio is specified correctly.
2. Use -minport and -maxport parameters for each of the login brokers to specify different port ranges for each broker. This will remove race conditions associated with getting a port when multiple brokers are started using the same port range.
3. Use the -PendConnTime startup parameter to ensure that Pending Connections are cleared after a set time interval.