DUAS: Communication issues between UVMS/UVC and Nodes through the network
Article ID: 87117
Updated On:
Products
CA Automic Dollar Universe
Issue/Introduction
The Unijob or Dollar Universe nodes are not accessible from the Univiewer console.
It is for example impossible to display the Node settings, perform a Node Synchronization, display the Objects or the Job Runs on all the impacted nodes.
The registration process may also fail.
Examples of error Messages :
From UVC log file:
#####
Agent IO Connection problem - ServerException - connect: error creating socket to node_name/port_number
#####
From unijob universe.log file:
#####
u_connect | u_gethostbyname_mf(uvms_node_name) returns error: Unknown host (gethostbyname(uvms_node_name) returns null pointer)
#####
From UVMS uvserver.log file:
#####
ERROR| consolidation-1-worker-xxx| com.orsyp.monitoring.consolidation.stdimpl.owls.OwlsConsolidationStdImpl | ConnectionException:
com.orsyp.std.IoConnectionException: Connection Authenticate problem com.orsyp.UniverseException: ServerException - connect: error creating socket to distant.hostname.domain/port_number
UniverseException: The server is unreachable. Reason: NIO CDJ Connection problem - ServerException - connect: error creating socket [company_name/node_name/X]
#####
It is for example impossible to display the Node settings, perform a Node Synchronization, display the Objects or the Job Runs on all the impacted nodes.
The registration process may also fail.
Examples of error Messages :
From UVC log file:
#####
Agent IO Connection problem - ServerException - connect: error creating socket to node_name/port_number
#####
From unijob universe.log file:
#####
u_connect | u_gethostbyname_mf(uvms_node_name) returns error: Unknown host (gethostbyname(uvms_node_name) returns null pointer)
#####
From UVMS uvserver.log file:
#####
ERROR| consolidation-1-worker-xxx| com.orsyp.monitoring.consolidation.stdimpl.owls.OwlsConsolidationStdImpl | ConnectionException:
com.orsyp.std.IoConnectionException: Connection Authenticate problem com.orsyp.UniverseException: ServerException - connect: error creating socket to distant.hostname.domain/port_number
UniverseException: The server is unreachable. Reason: NIO CDJ Connection problem - ServerException - connect: error creating socket [company_name/node_name/X]
#####
Cause
Network traffic not opened between the different components on their associated ports.
To make a connection between the different nodes, we use the TCP IP protocol, so basically, a set of ports and IP addresses must be opened on each Node / UVMS and other components.
To make a connection between the different nodes, we use the TCP IP protocol, so basically, a set of ports and IP addresses must be opened on each Node / UVMS and other components.
Resolution
We recommend to check the network configuration using the ping and telnet commands:
Check the ping result between the UVC host and the host where duas is installed
Check the ping result between the UVMS host and the host where duas is installed
Check the ping result distant_hostname
If the ping results are not ok, please check the network configuration for each impacted hosts
=> The address ip resolution, DNS or host file, must work correctly.
Check the telnet result between the UVMS host and the DUAS host: telnet duas_hostname 10600 (default IO port change if another port is used)
Check the telnet result between the UVC host and the DUAS host: telnet duas_hostname 10600 (default IO port change if another port is used)
Check the telnet result between the Tomcat hosting UVWC and the duas/unijob host: telnet duas_hostname 10600 (default IO port change if another port is used)
Check the telnet result between the DUAS host and the UVMS host: telnet uvms_hostname 4184 (default port change if another port is used)
If the telnet is not ok the firewall rules must be checked and modified in order to open the concerned ports on the impacted hosts.
In a few words, to have a normal network behaviour, the ping and telnet commands must give positive results for the concerned hostname(and/or IP address) and the concerned port number.
Check the ping result between the UVC host and the host where duas is installed
Check the ping result between the UVMS host and the host where duas is installed
Check the ping result distant_hostname
If the ping results are not ok, please check the network configuration for each impacted hosts
=> The address ip resolution, DNS or host file, must work correctly.
Check the telnet result between the UVMS host and the DUAS host: telnet duas_hostname 10600 (default IO port change if another port is used)
Check the telnet result between the UVC host and the DUAS host: telnet duas_hostname 10600 (default IO port change if another port is used)
Check the telnet result between the Tomcat hosting UVWC and the duas/unijob host: telnet duas_hostname 10600 (default IO port change if another port is used)
Check the telnet result between the DUAS host and the UVMS host: telnet uvms_hostname 4184 (default port change if another port is used)
If the telnet is not ok the firewall rules must be checked and modified in order to open the concerned ports on the impacted hosts.
In a few words, to have a normal network behaviour, the ping and telnet commands must give positive results for the concerned hostname(and/or IP address) and the concerned port number.
Additional Information
In case the hostname resolution does not work, for a Dollar Universe node you can register the node using the IP address instead of the hostname.
Else, you can always add an entry in the local hosts file, but this is not recommended, the hostnames should be declared and resolved by your DNS server.
Else, you can always add an entry in the local hosts file, but this is not recommended, the hostnames should be declared and resolved by your DNS server.
Feedback
Yes
No
Powered by
