The second node in a multi-AE server does not connect to the first node:Name or service not known'

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

The WPs and CPs on second node in a multi-AE server do not connect to the AE systems after the first node is started.

 

Based on these logs, the hostname [Server name 2] is not reachable or has some connection issue from [Server name 1 FQDN] .

 

JWP of node1 (servername):

=========================================================================================

20220825/163546.238 - 50     U00003490 Connection to '[Server name 2]:2270' initiated, client connection '44'

20220825/163546.239 - 50               Unhandled Exception in thread Timer-1 ID=50

20220825/163546.239 - 50     U00045014 Exception 'java.nio.channels.UnresolvedAddressException: "null"' at 'sun.nio.ch.Net.checkAddress():131'.

20220825/163546.239 - 50     U00003620 Routine 'com.automic.kernel.impl.DefaultExceptionHandler' forces trace because of error.

=========================================================================================

 

 

WP of node1 ([Server name 1 FQDN]):

============================================================

20220825/161252.160 - U00003525 UCUDB: ===> 'UPDATE UC_TABLE SET TABLE_Check = TABLE_Check WHERE TABLE_Name = ?'

20220825/161253.259 - U00003412 Agent 'getaddrinfo("[Server name 2]") - Name or service not known' logged on (Client connection='').

20220825/161253.259 -          Unknown error -2

20220825/161303.361 - U00003412 Agent 'getaddrinfo("[Server name 2]") - Name or service not known' logged on (Client connection='').

20220825/161303.361 -          Unknown error -2

20220825/161313.461 - U00003412 Agent 'getaddrinfo("[Server name 2]") - Name or service not known' logged on (Client connection='').

20220825/161313.461 -          Unknown error -2

============================================================

 

 

Environment

Release : 12.3

Component : Automation Engine

Cause

Network configuration issue

Resolution

Please do the following:

 

-Check with the network administrator to make sure [server name 2] is reachable from [server name 1 FQDN] and check why [server name 2] is not using FQDN

 

-Check if [server name 2] is defined on the DNS. It is possible that it is not properly defined.