Autoping not working, logs show connection refused or Address already in use bind failed
search cancel

Autoping not working, logs show connection refused or Address already in use bind failed

book

Article ID: 200671

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 Autosys Workload Automation

Issue/Introduction

Autoping command fails.  

The transmitter.log, we can see these messages. 

01/01/2020 00:00:12.345-0400 5 TCP/IP Controller Plugin.Transmitter pool thread <Slow:1>.CybTargetHandlerChannel.call[:747] - Attempting to send:    20200925 12363847+0400 USER1234 . CONTROL ACTIVE OSText(Linux for amd64) ByUser(rootuser) AgentRelease(11.4)  AgentBuild(1609, Service Pack 00, Maintenance Level 0)  User(USER1234) Host(server.example.com)
01/01/2020 00:00:12.345-0400 5 TCP/IP Controller Plugin.Transmitter pool thread <Slow:1>.CybTargetHandlerChannelLogHelper.logConnectionAttempt[:75] - Attempting to open conversation to [email protected]:7612 using plain socket
01/01/2020 00:00:12.345-0400 1 TCP/IP Controller Plugin.Transmitter pool thread <Slow:1>.CybTargetHandlerChannel.a[:1202] - Error connecting to ACE_SCH:                                                                                            cybermation.library.communications.CybConversationConnectBindException: Address already in use (Bind failed)

 

Environment

Release : 11.4

Component : CA Workload Automation System Agent

Cause

Ports to Application server are not open from Agent.  If Application server is on port 7500, then that port must be open from Agent host.

Also, check if the OS ephemeral ports are available from the Agent host.

Resolution

 

Open the Application port from agent machine.

Also, it is likely that agent system was running out of ephemeral ports at that time.  When the agent needs to connect to a server port, it needs a temporary port from the system as well. When the ephemeral port is not available, you will get that error message in the transmitter.log.

A reboot of the system may also clear the issue.


Additional Information

See this for more details on ephemeral ports

https://en.wikipedia.org/wiki/Ephemeral_port