1885
Failed to connect to monitor socket for process (LMID = MachineID, LPN = ProcessName, LPI = ProcessInstance). Socket error (Errno) on port number PortNum.
Description
The worker process sentinel cannot connect to the socket that should have been created by the child ProcessName, because of a socket Errno.
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:
| • | The system is extremely heavily loaded. The child ProcessName cannot create its server-side socket before the worker process sentinel attempts to connect to it. |
| • | The child ProcessName fails after it is created, but before the worker process sentinel attempts to connect to it. Consequently, there is no server-side socket for the worker process sentinel to connect to. |
| • | A network infrastructure problem. For example, if multiple network cards are installed on the computer where the is running, and a card is incorrectly configured. This can prevent the child ProcessName from being able to create its server-side socket. |
Appears In
SWDIR\logs\sw_warn
Severity
Either:
| • | 1 (Critical), if the specified ProcessName is critical to the system’s operation and the process sentinels have been unable to automatically restart it, |
or
| • | 2 (Severe), if the specified ProcessName is not critical to the system’s operation but the process sentinels have been unable to automatically restart it, |
or
| • | 3 (Warning), if the process sentinels have automatically restarted the specified ProcessName. |
Action
To resolve the problem:
| 1. | Check to see if the specified ProcessInstance of ProcessName is running (and that there is only one copy of it). If it has been marked as suspended, manually restart it and check that the error does not happen again. |
| 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. |
See Also
“Administering iProcess Engine Server Processes”, in the TIBCO iProcess Engine: Administrator's Guide, for more information about how to monitor and restart processes.