Local Agent Validation Error seen on a Remote Agent

book

Article ID: 221058

calendar_today

Updated On:

Products

CA Automic Applications Manager (AM)

Issue/Introduction

A Remote Agent may fail to start and report an Agent Validation Error for a different Agent.

For example, if an Remote Agent is call APWXDEV and a Agent Validation Error occurs, the reported Agent should be APWXDEV as seen below:

ErrorMsg: AwE-5126 Agent validation error
Details: APWXDEV 111.111.111.111/111.111.111.111 50000
Agent validation error : APWXDEV 111.111.111.111/111.111.111.111 50000 : java.net.ConnectException: not authorized to make connection

However, it may report a different Agent in the error as seen below:

ErrorMsg: AwE-5126 Agent validation error
Details: DEVMASTER 111.111.111.111/111.111.111.111 50000
Agent validation error : DEVMASTER 111.111.111.111/111.111.111.111 50000 : java.net.ConnectException: not authorized to make connection

Cause

This is a configuration issue with an environment variable setting the wrong Agent. 

Environment

Release : 9.3

Component :

Resolution

Edit the $AW_HOME/site/sosite file and make sure the below variable is set to the correct Agent Name:

SO_OPERATOR=DEVMASTER;export SO_OPERATOR

Additional Information

This behavior should not occur in normal circumstances unless this sosite file environment variable is manually edited or if the file itself is being auto-generated for automatic deployment reasons.