Segmentation Fault When Referencing Non-Existent Agent via VARA value

Products

• Automic Automation

Issue/Introduction

Introduction: 

When executing a Job or Jobplan that utilizes a variable extracted from a VARA object to define the host (agent) where the job should run, the Automation Engine may encounter a segmentation fault (SIGSEGV) if the referenced agent does not exist in the system. This issue typically surfaces after importing objects or transport cases where variable definitions point to legacy or non-existent agents.

This can produce force traces on the WP processes and some quarantine messages in client 0.

Environment

• Automic Automation (Automation Engine)
• Affected Versions: All currently supported versions (e.g., 24.4.x, 26.0.x)

Cause

This issue is identified as a software defect (DE210455). The Automation Engine core incorrectly handles the reference resolution when a Variable (VARA) used for the Host attribute contains an invalid or non-existent agent name, leading to an unexpected process abort (SIGSEGV) and memory dump.

Resolution

Mitigation: 

To maintain system stability while the defect is under review, please implement one of the following workarounds:

1. Validate Agent References: Review the contents of the Variable objects used in your jobs (e.g., VARA_NAME). Ensure that all HOST/AGENT values defined in the variable reference valid, active agents currently registered in the system.
2. Hardcode Host Attribute: For jobs experiencing this issue, temporarily bypass the use of the variable for the host attribute. Open the Job object, navigate to the Attributes page, and explicitly define HOST='YOUR_AGENT_NAME' instead of referencing a variable. This prevents the Automation Engine from attempting to resolve the invalid reference during the variable substitution phase.

Solution:

Update to a fix version listed below or a newer version if available.

Fix version:
Component(s): Automation Engine

Automation.Engine 24.4.5 HF2 - TBA
Automation.Engine 24.4.6 - TBA
Automation.Engine 26.1.0 - TBA

We recommend that you subscribe to this article to receive automatic updates on the status of this defect: How to subscribe to Knowledge Base articles.

Additional Information

Public Title: Fix crash on PUT_ATT on non-existing agent

Public Description: A work process crash has been fixed where a PUT_ATT was used on a non existing agent.

• If you continue to experience system instability, please collect the Automation Engine logs and trace files corresponding to the time of the SIGSEGV and reach out to our support team for further investigation.