The iProcess WORKER process sentinel dies after it is started.

iProcess sw_error.log error:
2017/10/02 23:20:18.732729(<unknown>:0:401876:2::::pro:/pmmain.c:82382:6135): 1881-Unable to establish communication with the peer (WORKER) process manager.   Comms error (Unknown error code: 0).
2017/10/02 23:20:18.734307(<unknown>:0:401876:2::::pro:/pmmain.c:82382:6287): 1882-Communication terminated abnormally with peer process manager (WORKER) and could not be re-established after 20 retries.  Assuming process has died and re-starting.  Socket error (Unknown error code: 0).

The TIBCO iProcess WORKER process sentinel dies after it is started.

TIBCO iProcess Engine (Oracle) 11.4.0.2 AIX 64

The debug log shows that the hostname OS the server is:

[T=00001]171002232009.597996:b064: sw_gethostbyname () - hostname abcdef03, h_ent abcdef03

The procmgr debug log indicates that no records were retrieved from the iProcess database for the server name abcdef03

fil_pcfg_node_find - Select found no data

This means that no configuration was found for server abcdef03 and the process terminates as there are no processes to start on the server. The resolution is to configure the server name in iProcess so that the iProcess master node runs on server abcdef03. The server abcdef04 is the current active master node -the following actions are required:

1). Stop iProcess on abcdef04.

2). Update iProcess to run the master on abcdef03.
    swadm move_server 1 abcdef03

3). Start iProcess on abcdef03.

The actions will enable iProcess to start the master node on server abcdef03.