1884
Failed to create monitor socket. Socket error (ErrNo) on port number PortNum.
Description
The child process on port number PortNum has reported a socket Errno. It cannot create a server-side socket because the port number it has been given by the worker process sentinel is still in use.
The worker process sentinel uses a TCP/IP socket connection with each started process to monitor that process. Each process is given a unique port number on which to create a server‑side socket which the worker process sentinel can connect to and monitor. The worker process sentinel simply requests the next free port number from the operating system.
Possible causes of this error are:
| • | Another application creates a socket on the same port number, in between the worker process sentinel requesting the next free port number and the child process creating the server-side socket. This can happen if, for example, an application is configured to always use this port number. |
| • | One of the worker process sentinel’s child processes (for example, a BG process) is using a specified port number and fails. The process is automatically restarted by the worker process sentinel and attempts to create a new socket connection on the same port number as before, but for some reason the operating system has not yet marked that port as unused. |
Appears In
SWDIR\logs\sw_warn
Severity
2 (Severe)
Action
To resolve the problem:
| 1. | Ensure that the specified PortNum is not being used by another application. |
| 2. | See the socket documentation for your particular operating system for more information about the socket ErrNo, what might have caused it, and how to resolve it. |