Linux agent doesn't start: U02000320 ... bin./security' not a dir or no permissions
search cancel

Linux agent doesn't start: U02000320 ... bin./security' not a dir or no permissions

book

Article ID: 404802

calendar_today

Updated On:

Products

Automic SaaS CA Automic Workload Automation - Automation Engine

Issue/Introduction

When starting a Linux Agent, it may fail to start due to the below error found in the Agent's "/temp/*_00.txt" log file:

20250718/150031.970 - U02000320 The selected path '/automic/agent/bin/./security' is either not a directory, or does not have the required permissions to read and write files.
20250718/150031.971 - U02000299 Error during handling Certificate Signing Request: 'Cannot write or read from path /automic/agent/bin/./security'.
20250718/150031.972 - U02000041 Shutdown Agent 'AutomicAgent'.
20250718/150031.973 - U02000010 Connection to Server 'example.automic.com/<unresolved>:443' terminated.
20250718/150031.976 - U02000002 Agent 'AutomicAgent' version '24.4.0+hf.3.build.1747989755151' ended abnormally.

Cause

Caused by file permission issue or related settings

Resolution

The Linux Agent can only operate with full capabilities if it is installed as a privileged process. There are a few ways to do this which is described in the documentation link below:

Installing the Agent for IBM AIX, Linux x64, and PowerPC 64 LE (Java)   See topic "Privileged and Unprivileged Mode"

While the documentation describes a few options for setting up the Agent permissions, a common cause of a 'Cannot write or read from path /automic/agent/bin/./security' error is if ucxjlx6 is missing the SetUID (s-bit) for the Agent file owner.

Check if ucxjlx6 has the s-bit for it's file permission. If it does not, s-bit can be added by running the below command in the Agent's bin directory:

chmod 4755 ucxjlx6