Agent polling behaviour
search cancel

Agent polling behaviour

book

Article ID: 92138

calendar_today

Updated On:

Products

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

Issue/Introduction



After an upgrade, we have noticed is the large amount of agent polling that's going on: [28/03/2018 13:43:47.7554] CAUAJM_E_00046 The UNIX function getaddrinfo failed to resolve hostname [sp1incr1cum2_703_xxxxxxxxxx.com] after retrying. System message: Name or service not known [28/03/2018 13:43:47.7752] CAUAJM_E_00046 The UNIX function getaddrinfo failed to resolve hostname [sp1incr1cum2_703_xxxxxxxxxx.com after retrying. System message: Name or service not known [28/03/2018 13:43:47.7753] CAUAJM_E_00046 The UNIX function getaddrinfo failed to resolve hostname [sp1incr1cum2_703_xxxxxxxxxx.com] after retrying. System message: Name or service not known [28/03/2018 13:43:47.7761] CAUAJM_E_00046 The UNIX function

These are non existent agents that we created for testing purposes a while back. Does it run through all the agents at start up?
Does this happen before scheduling resumes?
Does the polling take precedence over jobs running?
We have a large amount of agents in production (Over 6.5K on a single instance) so if we can amend the interval, does this start from the beginning or end of the polling?
What would be the impact if we set this to an extremely high number?

Environment

Upgrade  from R11.3.6 SP6 to SP7 

Resolution

When the agent is back online, AutoSys registers itself with the agent and sends the hostname name to use. Autosys uses the gethostname() O/S API to get the hostname.
This explains the behavior you are seeing. You could delete these machines as they are no longer used.

For exemple :
 

delete_machine: name_of_real_machine

[remove_references: y]

[force: y]