Port errors when starting PAS server

Posted by anzki4 on 27-Jun-2018 05:47

I have some weird port issues. I have created PAS server with the following command: "tcman create -p 9110 -P 9111 -s 9112 -j 9113 -N pas-internal-dev {path_to_pas_server_here}"

When I try to start the server, I get the following error from agent log (other logs have no errors):

[18/06/19@15:45:25.149+0300] P-006656 T-011064 1 AS-Aux-0 MSAS Agent Starting Up -- Progress OpenEdge Release 11.7 build 1497.
[18/06/19@15:45:25.149+0300] P-006656 T-011064 1 AS-Aux-0 -- Logging level set to = 2
[18/06/19@15:45:25.149+0300] P-006656 T-011064 1 AS-Aux-0 -- Log entry types activated: ASPlumbing,DB.Connects
[18/06/19@15:45:25.150+0300] P-006656 T-011064 2 AS-Aux-0 AS Starting MSAS Session for pas-internal-dev.
[18/06/19@15:45:25.155+0300] P-006656 T-011064 2 AS-Aux-0 AS MSAS Session Startup. (5473)
[18/06/19@15:45:25.163+0300] P-006656 T-011064 1 AS-Listener -- Log entry types activated: ASPlumbing,DB.Connects
[18/06/19@15:45:25.163+0300] P-006656 T-011064 2 AS-Listener AS Starting MSAS Session for pas-internal-dev.
[18/06/19@15:45:25.164+0300] P-006656 T-011064 2 AS-Listener AS MSAS Session Startup. (5473)
[18/06/19@15:45:25.176+0300] P-006656 T-011064 1 AS-Listener -- Service transport TCP is busy. (5485)
[18/06/19@15:45:25.176+0300] P-006656 T-011064 1 AS-Listener -- TCP is busy, no free ports available between min/max range (-3534 - -3334) (15765)
[18/06/19@15:45:25.176+0300] P-006656 T-011064 2 AS-Listener AS MSAS Session initialisation failure. (5475)
[18/06/19@15:45:25.176+0300] P-006656 T-011064 1 AS-Listener MSAS Unable to initialize service for session!
[18/06/19@15:45:25.176+0300] P-006656 T-011064 1 AS-Listener MSAS Unable to initialize listener thread context!

Neither of those ports (3334, 3534) is not mentioned in any PAS server configuration files or any progress configuration files. From the PAS server configuration (file: {path_to_pas_server}/conf/openedge.properties) the default AppServer.Agent port range is from 62001 to 62202.

If I change those ports to anything other than the default, I get the following error instead (where {PORT_NUMBER_HERE} is the first free port from beginning of the port range):

[18/06/27@11:31:10.637+0300] P-012964 T-007828 1 AS-Aux-0 MSAS Agent Starting Up -- Progress OpenEdge Release 11.7 build 1497.
[18/06/27@11:31:10.637+0300] P-012964 T-007828 1 AS-Aux-0 -- Logging level set to = 2
[18/06/27@11:31:10.637+0300] P-012964 T-007828 1 AS-Aux-0 -- Log entry types activated: ASPlumbing,DB.Connects
[18/06/27@11:31:10.637+0300] P-012964 T-007828 2 AS-Aux-0 AS Starting MSAS Session for pas-internal-dev.
[18/06/27@11:31:10.642+0300] P-012964 T-007828 2 AS-Aux-0 AS MSAS Session Startup. (5473)
[18/06/27@11:31:10.652+0300] P-012964 T-007828 1 AS-Listener -- Log entry types activated: ASPlumbing,DB.Connects
[18/06/27@11:31:10.652+0300] P-012964 T-007828 2 AS-Listener AS Starting MSAS Session for pas-internal-dev.
[18/06/27@11:31:10.652+0300] P-012964 T-007828 2 AS-Listener AS MSAS Session Startup. (5473)
[18/06/27@11:31:10.669+0300] P-012964 T-007828 1 AS-Listener MSAS Spawning New Worker Thread. Number: 4
[18/06/27@11:31:10.674+0300] P-012964 T-013744 1 AS-ResourceMgr -- Log entry types activated: ASPlumbing,DB.Connects
[18/06/27@11:31:10.674+0300] P-012964 T-013744 2 AS-ResourceMgr AS Starting MSAS Session for pas-internal-dev.
[18/06/27@11:31:10.674+0300] P-012964 T-013744 2 AS-ResourceMgr AS MSAS Session Startup. (5473)
[18/06/27@11:31:52.672+0300] P-012964 T-013744 1 AS-ResourceMgr -- Connection failure for host WMLI118037 port {PORT_NUMBER_HERE} transport TCP. (9407)
[18/06/27@11:31:52.672+0300] P-012964 T-013744 1 AS-ResourceMgr MSAS Resource Manager could not establish connection to listener socket.
[18/06/27@11:32:10.669+0300] P-012964 T-007828 1 AS-Listener MSAS Agent Shutting Down. Status: -1000
[18/06/27@11:32:10.669+0300] P-012964 T-011012 1 AS-Aux-0 MSAS Worker Thread exiting. Number: 4, Status: -16
[18/06/27@11:32:10.669+0300] P-012964 T-007828 1 AS-Listener MSAS Spawning New Worker Thread. Number: 5
[18/06/27@11:32:10.669+0300] P-012964 T-012148 1 AS-Aux-0 MSAS Worker Thread exiting. Number: 5, Status: 0
[18/06/27@11:32:10.670+0300] P-012964 T-007828 1 AS-Listener MSAS Agent Shutdown Complete.

All Replies

Posted by gus bjorklund on 27-Jun-2018 13:26

could be other stuff on the system is using those ports, or

the system may be configured to not allow use of ports in a certain range.

see www.ncftp.com/.../ephemeral_ports.html

Posted by Matt Baker on 27-Jun-2018 13:40

Did you run netstat to see what is using the specified port range?

TCP is busy, no free ports available between min/max range (-3534 - -3334) (15765)

This looks a little odd since there are negative numbers in front of those ports.  Maybe the port range is specified incorrectly?

Posted by George Potemkin on 27-Jun-2018 14:07

> TCP is busy, no free ports available between min/max range (-3534 - -3334) (15765)

%s is busy, no free ports available between min/max range (%d - %d) (15765)

where %d is a signed two byte integer

So the real min/max range is 62002- 62202

Posted by Rob Fitzpatrick on 27-Jun-2018 14:12

With numbers that high, it could be ephemeral ports that are in use by outbound connections.

Also, I know the 4GL broker won't assign servers to ports that are defined in the services file, even if they are not currently in use.  Does PASOE do the same?

Posted by anzki4 on 28-Jun-2018 02:40

I have checked with netstat that those ports are not in use. I have checked from /etc/services that there are no ports defined within that range. Those default ports are within ephemeral port range (40900-65535 on my pc), but I have tried it with ports that are outside it.

After some more debugging, when I change the minPort to anything lower than 61788, I get the second error instead.

I have tried it with multiple different minPort values including 3000, 8000, 12000, 40000. With all those ports I get the second error with the {PORT_NUMBER_HERE} being the minPort. I have also tested that I can start http-server on all of those ports.

This thread is closed