Resolution: The daemon doesn't pick up the IP address correctly due to a different
output format of the command "ifconfig -a" which looks like below:
[tibco@trex-centos-01 ~]$ ifconfig -a
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.42.1 netmask 255.255.0.0 broadcast 0.0.0.0
ether 56:84:7a:fe:97:99 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
The engine fails to get the IP address of the server correctly and returns 0.0.0.0 which in-turn prevents the engine daemon from starting up.
The
workaround is to set the environment variable DS_USE_SNAT_IP_ADDRESS to
the Engine’s IP on the engine start-up script. This should pick up the
correct adapter relative to the IP.
I have copied the release notes for the variable below:
DS_USE_SNAT_IP_ADDRESS
This is an Engine Daemon setting.
To
use
this, set the environment variable DS_USE_SNAT_IP_ADDRESS on a Daemon
to the IP address that you want it to report to the Manager and all
Drivers as its address. Additionally, you MUST set 'Self Ping' on the
fileserver to FALSE in the Engine Configuration.
Alternatively,This can also be set in the .bash_profile of the tibco user account.