search cancel

Autosys agent not connecting to Autosys scheduler

book

Article ID: 188789

calendar_today

Updated On:

Products

CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - System Agent (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent CA Workload Automation AE

Issue/Introduction

WA Agent showing in blocked state and does not respond to autoping command.

Machine Name            Max Load   Current Load Factor  O/S         Status
_______________________ __________ ____________ _______ ___________ ______

machine_name            ---        ---          1.00    Sys Agent   Blocked


CAUAJM_I_50023 AutoPinging Machine [machine_name]
CAUAJM_E_10229 Communication attempt with the CA WAAE Agent has failed! 
CAUAJM_E_50281 AutoPing from the Scheduler WAS NOT SUCCESSFUL.
CAUAJM_E_10229 Communication attempt with the CA WAAE Agent has failed! [machine_name:7520]
CAUAJM_E_50283 AutoPing from the Application Server WAS NOT SUCCESSFUL.
CAUAJM_E_50026 ERROR: AutoPing WAS NOT SUCCESSFUL.

 

Cause

Check the port for agent is open from Autosys Application Server to Agent host.

If multiple agents are installed on same agent machine, then check if agent port is correctly defined in machine definition.

Environment

Release : 11.x/R12.x

Component : CA Workload Automation System Agent

Resolution

Check agent(s) port in agentparm.txt file.  Make sure the agent is listening on the port and it accessible from App server (AutoSys).

Use different agent port for multiple agents.

Note: A port can be used by only one service.  An agent port used by an agent cannot be used by another agent or any other service on that host.

 

Example of two agents below

Agent1 : 7520
Agent2 : 7521