CCI fails to start after automated reboot due to shared memory collision - AutoSys Workload Automation

Products

• Autosys Workload Automation

Issue/Introduction

After an automated reboot (such as during an OS patching cycle), the CA Common Services CCI (CA-cci) component fails to start.
This issue occurs because two separate processes attempt to initialize the CCI daemon simultaneously, leading to a resource collision.

Symptoms:

• CCI services do not come up automatically after a reboot.
• Manual ustat checks show CA-CCI Server as "not active" or "up" but non-functional.
• System journals or CCI logs show duplicate process IDs (PIDs) for caiccid at the same timestamp.
• Errors include:
  • .CAICCI_F_1011 Cannot create the CCI shared memory, error=<17>
  • .CAICCI_F_0001 CCI semaphore could not be obtained
  • caiccid[####]: segfault at ...

 

Environment

• AutoSys Workload Automation 12.x, 24.x
• Red Hat Enterprise Linux (RHEL) 8.x or 9.x
• CA Common Services (CCS) CCI

Cause

A race condition occurs during the boot sequence. Both the operating system's service manager and the AutoSys Scheduler's startup script attempt to launch CA-cci at the same time.
Because the caiccid daemon is not yet fully initialized when the second process checks its status, both processes attempt to create the same shared memory segments and semaphores, causing one or both to crash or enter a hang state.

Resolution

To resolve this issue, disable the operating system-level automatic startup for the CA-cci service. This allows the AutoSys Scheduler to manage the CCI startup exclusively, preventing the collision.

1. Log in as a user with root or sudo privileges.
2. Disable the service startup at the OS level: chkconfig CA-cci off (Note: On systems using systemd, this may also be accomplished via systemctl disable CA-cci).
3. Verify the service is disabled: systemctl is-enabled CA-cci
4. Reboot the server. The AutoSys Scheduler will now bring CCI online during its own initialization sequence without conflict.

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.