Error: CAUAJM_W_00002 Listener could not be started on port 9000 due to SockAdapter ACL conflict

Products

• Autosys Workload Automation

Issue/Introduction

The AutoSys Application Server fails to start after a system reboot or security update, reporting that port 9000 is already in use.
This occurs despite no other process bound to that port.

This article explains how to identify and fix Access Control List (ACL) conflicts on the Secure Sockets Adapter (SSA) directory.

Symptoms

The as_server log or terminal shows the following:

text

 

[#### ####] CAUAJM_W_00002 Listener could not be started on port [9000]. Proceeding... [listen(): 98: Address already in use][#### ####] CAUAJM_E_10125 AutoSys Application Server failed to establish a listener at host [####:9000]. Exiting.

 

Environment

• roduct: AutoSys Workload Automation AE
• Version: 12.x and higher
• Operating System: Linux (RHEL 7.x, 8.x)
• Conflict Source: Security or monitoring agents (e.g., otelcol-contrib, Dataguard)

Cause

Security agents or OS patching cycles modify the default ACLs on the /opt/CA/SharedComponents/Csam/SockAdapter/ directory.
When the CSAM broker (csampmuxf) creates the .csam_broker socket, it inherits restrictive permissions that prevent the AutoSys user from writing to the socket, triggering a false "Address already in use" error.

Resolution

Follow these steps to compare and fix the permissions.

1. Compare working vs. non-working systems Run the following command on both a functional server and the impacted server: getfacl /opt/CA/SharedComponents/Csam/SockAdapter/

   Example Output (Non-Working):
   Note the default entries and restrictive masks introduced by monitoring agents:

   text

   owner: root
group: root

   user::rwx
user:otelcol-contrib:r-x
group::rwx
mask::r-x
other::r-x
default:user:otelcol-contrib:r-x
default:mask::r-w
Example Output (Working): Native permissions typically show no extended ACLs (no + sign in ls -l):

   text

   owner: root
group: root

   user::rwx
group::r-x
other::r-x

2. Reset the ACLs Strip the default inheritance rules to allow the system to use the software's native creation mask:
   setfacl -d -b /opt/CA/SharedComponents/Csam/SockAdapter/
3. Restart CSAM and AutoSys Restart the broker to recreate the socket file with correct permissions:
   bash

/opt/CA/SharedComponents/Csam/SockAdapter/bin/csampmux stop
/opt/CA/SharedComponents/Csam/SockAdapter/bin/csampmux start
unisrvcntr start waae_server.####
   
   
4. Verification Confirm the socket .csam_broker now has srwxrwxrwx permissions: ls -l /opt/CA/SharedComponents/Csam/SockAdapter/.csam_broker