Scheduler not picking up new IP for machine

Products

• Autosys Workload Automation

Issue/Introduction

When a DNS alias pointing to a Scheduler agent machine is updated from machineA to machineB, the Scheduler continues to route jobs to machineA rather than picking up the new IP address.

Environment

• Workload Automation / AutoSys Scheduler

• Multi-node / DNS Alias configuration across multiple machines

 

Cause

The Scheduler parameter EnableIPCaching=1 is set in the $AUTOUSER/config.$AUTOSERV file. When IP caching is enabled, the Scheduler caches the resolved IP address for a machine name or alias and continues to use it until:

1. A connection failure occurs when attempting to contact the agent at the cached IP address.

2. The Scheduler process is restarted.

If the agent on machineA remains active after the DNS alias is repointed to machineB, connections to machineA do not fail. Consequently, the Scheduler does not trigger a fresh DNS lookup and relies on the cached IP.

Resolution

To force the Scheduler to perform a new DNS/IP lookup for the alias, perform one of the following actions:

• Option 1 (No Scheduler Restart): Stop the agent service on machineA. The next connection attempt by the Scheduler will fail, causing it to clear the cached IP and resolve the new IP address for machineB.

• Option 2: Restart the Scheduler service to clear the IP cache.

(Optional) To disable IP caching permanently, set EnableIPCaching=0 in the $AUTOUSER/config.$AUTOSERV file and restart the Scheduler.

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on the respective region.