Agents not coming online
search cancel

Agents not coming online


Article ID: 108079


Updated On:


DSERIES- SERVER CA Workload Automation DE - System Agent (dSeries)


New install agents on Linux server not going online.


CA Workload Automation Agents


It's possible that the manager port is not open on the firewall for Agent and scheduling manager to communicate. Check the agent's receiver and transmitter logs for communication messages between the agent and scheduling manager, if the agent can receive the message from the manager and send massages back to the agent.

If the agent cannot connect with the manager, you can see exception like this in the agent's transmitter log;

07/25/2018 10:45:19.230 EDT-0400 5 TCP/IP Controller Plugin.Transmitter pool thread <Slow:1>.CybTargetHandlerChannelLogHelper.logConnectionAttempt[:75] - Attempting to open conversation to ESP_TESTSCHD_7500@TESTSCHD:7507 using plain socket

07/25/2018 10:45:29.286 EDT-0400 1 TCP/IP Controller Plugin.Transmitter pool thread <Slow:1>.CybTargetHandlerChannel.constructConversation[:1190] - cybermation.library.communications.CybConversationException: connect timed out

If the agent receiver.log has no message entry from the scheduling manager, it means that manager cannot connect to the agent.


Make sure the agent and manager ports (default ports 7520 and 7507) are open on the firewall for agent and scheduling manager to communicate. 

You can check the ports configured for agent and manager in agent's agentparm.txt file. For example;

communication.inputport=7520        > port number the agent uses to listen for incoming messages from the scheduling manager

communication.managerport_1=7507        > port number the scheduling manager listens on for communication from agents

Note: Firewall can also be run locally on some servers such as Windows and Linux based systems. You'll want to check that as well as with your Network Administrators.

The agent and manager should be able to connect both ways.


Additional Information

Once you identify the manager addresses and ports that the agent is trying to communicate with, you can manually test the connection with something like: 

  • Windows/Powershell: Test-NetConnection -ComputerName <manager ip address|and/or|hostname> -Port <manager port>
  • Linux: curl -v telnet://<manager ip address|and/or|hostname>:<manager port>