Agent on machine has not responded in a timely fashion
book
Article ID: 129209
calendar_today
Updated On:
Products
CA Workload Automation AE - Business Agents (AutoSys)CA Workload Automation AE - Scheduler (AutoSys)CA Workload Automation Agent
Issue/Introduction
we are getting error as Agent on [xxxxxxxxx] has not responded in a timely fashion. We have also re-installed agent but issue still persists.
autoping status. CAUAJM_I_50023 AutoPinging Machine [xxxxxxxxx] CAUAJM_W_10496 Agent on [xxxxxxxxx] has not responded in a timely fashion. Try again later. [CA WAAE Autoping] CAUAJM_E_50281 AutoPing from the Scheduler WAS NOT SUCCESSFUL. CAUAJM_W_10496 Agent on [xxxxxxxxx] has not responded in a timely fashion. Try again later. [CA WAAE Autoping] CAUAJM_E_50283 AutoPing from the Application Server WAS NOT SUCCESSFUL. CAUAJM_E_50026 ERROR: AutoPing WAS NOT SUCCESSFUL.
The agent's transmitter.log shows a lot of "Address already in use (Bind failed)" errors that prevent it from opening a connection to the scheduler.
03/11/2019 16:21:55.946 IST+0530 1 TCP/IP Controller Plugin.Transmitter pool thread <Regular:1>.CybTargetHandlerChannel.constructConversation[:1198] - Error connecting to XXX_SCH: cybermation.library.communications.CybConversationConnectBindException: Address already in use (Bind failed)
That usually occurs when all the ephemeral ports are in use or in a pending state (CLOSE_WAIT, etc).
Environment
CA Workload Automation Agent 11.3, Build 979, Service Pack 7 Redhat Linux 7.x
Resolution
So stopped the agent ./cybAgent -s
output of netstat -anp showed that there were 28k processes with CLOSE_WAIT for port 35004 help by PID 9667 for java. This is perhaps not allowing the agent to get any more ephemeral ports.