AutoSys Agent Not Responding to Stop Commands After Installation

Products

• Autosys Workload Automation

Issue/Introduction

Following an installation or startup, attempts to stop the AutoSys System Agent using direct cybAgent command-line instructions fail or become unresponsive, often requiring manual PID termination.

Environment

 

• Product: AutoSys Workload Automation / System Agent

• Operating System: Linux / UNIX (utilizing systemd / systemctl)

 

Cause

This issue occurs because the agent process was originally launched as a system service via systemctl, but subsequent attempts to stop or restart it were performed using direct cybAgent CLI commands. Direct binary execution commands are incompatible with process instances actively managed by systemctl.

Resolution

To ensure proper process lifecycle management and prevent orphan processes:

• Standardize Service Management: Use systemctl exclusively for all lifecycle operations (e.g., systemctl restart autosys or systemctl restart waagent).

• Avoid Mixed Execution Methods: Do not combine systemctl service management with direct cybAgent command-line stops or starts on the same process.

• Maintain Process Control: Consistently managing the process via systemctl allows the service manager to handle agent execution properly, eliminating the need for manual PID termination.

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.