New or migrated remote agent fails to start due to an "UnresolvedAddressException" error
search cancel

New or migrated remote agent fails to start due to an "UnresolvedAddressException" error

book

Article ID: 103095

calendar_today

Updated On:

Products

CA Automic Applications Manager (AM)

Issue/Introduction

After installing or migrating a Remote Agent to a new domain the, agent does not start and is stuck in a SRVC_DOWN status. The below error is seen in the agent logs:

ErrorMsg: AwE-5107 awcomm connection error
Details: R:AMPROD appworx.xx.yyy:2136 <- 0.0.0.0/0.0.0.0:0
awcomm connection error : R:AMPROD appworx.xx.yyy:2136 <- 0.0.0.0/0.0.0.0:0 : java.nio.channels.UnresolvedAddressException

An nslookup command on the master's hostname from the agent will usually fail.

Environment

Release: 9.x
Component: CA Automic Applications Manager (AM)

Cause

This is likely an issue with DNS not being configured correctly.

Resolution

While referring to the network/server admin is recommended, possible solutions include the following:

  1. There is may be a missing resolv.conf file that is typically used to translate a hostname to an IP address. This issue can be encountered if the system doesn't have one
  2. The agent's /etc/hosts file may be missing an entry for the Automation Engine's (master) server