RSEG1242 Daemon failed to launch server on <host> using port <port>.
Connection refused.
"Connection refused" is a TCP/IP message saying that nobody is listening on the port you are
trying to connect to. Here are the possible reasons no one is listening:
RSE daemon is not active. Check the host. (For example, in SDSF.)
RSE daemon is not using the port specified by the client. Check console message
FEK002I (in the syslog or RSE daemon job output).
A firewall or other network issue is blocking the client from accessing the RSE daemon port.
(Port 0 in the RSEG1242 message normally indicates the RSE daemon.) Try telnet from the
client machine to the RSE daemon port. (The connection will hang for 30 seconds if successful, but a
firewall should display a message.)
telnet <host> <port>
The client can access the RSE daemon, but not the RSE server, due to firewall issues. (This
situation is typically indicated by a non-zero port number in the RSEG1242 message.) Use
_RSE_PORTRANGE in rsed.envvars to limit the ports being used, and
open them in your firewall.
Figure 1. RSEG1242 with connection refused
RSEG1242 Daemon failed to launch server on <host> using port <port> server
failure: <message>
The details show the error message shown in rseserver.log (only if the RSE
daemon or server was reached). Host logs are probably needed to see what is going on and resolve the
issue. See the rseserver.log section for more information.
Figure 2. RSEG1242 with server failure
RSEG1242 Daemon failed to launch server on <host> using port <port>
userid: <message>
The details show the error message shown in rseserver.log (only if RSE daemon or
server was reached). Host logs are probably needed to see what is going on and resolve the issue.
See rseserver.log section for more information.
