AutoSys Command Job Generates KILLJOBFAIL Alert When term_run_time is Exceeded

Products

• Autosys Workload Automation

Issue/Introduction

Command jobs within AutoSys that exceed their configured term_run_time may unexpectedly generate a KILLJOBFAIL alert and terminate with an "Aborted, Signal 2" error. This behavior occurs even when the job definition explicitly sets alarm_if_fail and alarm_if_terminated to 0 (disabled), leading to confusion about the source of the KILLJOBFAIL alert.

Environment

• Product: AutoSys Workload Automation
• Component: Command Jobs, Scheduler, term_run_time attribute, KillSignals configuration

Resolution

This behavior is due to a known issue related to the KillSignals setting in the AutoSys scheduler configuration file. If the KillSignals parameter is configured with multiple signal numbers separated by commas, the scheduler may incorrectly issue a KILLJOBFAIL alert when a job is terminated due to exceeding its term_run_time.

To resolve this issue, modify the KillSignals parameter in the $AUTOUSER/config.$AUTOSERV file to use a single signal value:

1. Locate the config.$AUTOSERV file: This file is typically found in the $AUTOUSER directory on your AutoSys scheduler host.
2. Edit the KillSignals parameter:
   • Original (problematic) configuration example:
     KillSignals=2,9
   • Modified (recommended) configuration example:
     KillSignals=9
   • Important: Change the value to a single signal number (e.g., 9 for SIGKILL).
3. Restart the AutoSys Scheduler: After modifying the config.$AUTOSERV file, you must restart the AutoSys scheduler for the changes to take effect.

This is a known issue that will be addressed in future maintenance releases of AutoSys. For more details, refer to the official documentation on known issues:

• Known Issues in AutoSys 24.0.01