TIBCO iProcess sentinel (PROCMGR) report a, 1885-Failed to connect to monitor socket for process, when trying to start the SPO process
Article ID: KB0079716
Updated On:
| Products | Versions |
|---|---|
| TIBCO iProcess Engine (Oracle) | All supported versions |
Description
Starting the iProcess Engine processes results in all the processes starting correctly except the iProcess Objects Server (SPO) process which reports having a SUSPENDED status. A message similar to below is reported in the sw_error.log file,
2018/12/12 12:42:39.717314(PROCMGR:2:31602:1::::pro:/pmstart.c:84973:2217): 1885-Failed to connect to monitor socket for process (LMID = 1, LPN = SPO, LPI = 1). Socket error (Unknown error code: 0) on port number 9759
Environment
Operating System: Unix / Linux
Resolution
The problem may be caused because iProcess Objects Server executable (swentobjsv) does not have the correct permissions.
An "ls -l" directory listing of the $SWDIR/bin directory should show the permissions to be,
-r-xr-x---
Update the permissions to be correct,
chmod 550 swentobjsv
An "ls -l" directory listing of the $SWDIR/bin directory should show the permissions to be,
-r-xr-x---
Update the permissions to be correct,
chmod 550 swentobjsv
Issue/Introduction
Starting the iProcess Engine processes results in the SPO process not starting and having a message reported in the sw_error.log file that is similar to:
2018/12/12 12:42:39.717314(PROCMGR:2:31602:1::::pro:/pmstart.c:84973:2217): 1885-Failed to connect to monitor socket for process (LMID = 1, LPN = SPO, LPI = 1). Socket error (Unknown error code: 0) on port number 9759
Feedback
Yes
No
Powered by
