Remote Events / multinode sessions not working

Document ID : KB000085540
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
These kind of errors appear on the universe.log

######################################################
ERROR|X|IO |pid=7692.7404| owls_api_exchanger_create | Error 200 connecting to node <ttl6db01> port 10600
ERROR|X|IO |pid=2564.3000| k_handshakeAuthent | authentication to []/[ttl6db01.int-prod.trainline.com] failed, status [3]
ERROR|X|IO |pid=2564.3000| owls_api_exchanger_create | Error 300 connecting to node <ttl6db01> port 10600
ERROR|X|IO |pid=2564.3000| o_module_exc_cycle_emissi | Cannot send exchanger message to remote node ttl6db01
######################################################

These errors may also appear:

on windows node:
######################################################
|ERROR|X|IO |pid=6176.8872| fopen | Error opening file [D:\app\dollar_universe\data\exp\network\0000001.receive] mode (rb): No such file or directory
######################################################

on linux remote node:
######################################################
ERROR|X|IO |pid=95966.139829996988736| fopen | Error opening file [/u01/app/dollaruniverse/TRAINP_ttl6db01/data/exp/fla/0036727.input] mode (rb): No such file or directory
######################################################

Patch level detected:Dollar Universe 6.0.00
Product Version: Dollar.Universe 6.0.0

Description :The multinode sessions stop working when having to switch to a remote node.
The uprocs having a dependency condition on a remote Event, remain in status Event Wait.
Environment:
OS: All
Cause:
Cause type:
Configuration
Root Cause: The remote node had several ip adresses and the one used to declare the node on the UVMS (ttl6db01.int-prod.trainline.com) pointed to an ip adress which was not allowed on the firewall for the local node to communicate with.
Resolution:
In order to fix the issue, add a line on the hosts file of the local node pointing to the IP address of the remote node that is opened on the firewall.
A better solution would be asking the Network team to create a different alias on the DNS pointing to that ip address and the modify the declaration of the remote node via the command:
unims -update -host NEWHOSTNAME

A restart of the node is necessary to take into account the change.

Fix Status: No Fix
 
Additional Information:
Workaround :
N/A