Installing PAMSC 14.1 cumulative release cp08 on rhel 7.9 it can't load syscall
search cancel

Installing PAMSC 14.1 cumulative release cp08 on rhel 7.9 it can't load syscall

book

Article ID: 434375

calendar_today

Updated On:

Products

CA Privileged Access Manager - Server Control (PAMSC)

Issue/Introduction

When installing the PAMSC cumulative release cp08 on rhel 7.9 you are getting this error regarding syscall not being able to load 

RH7.9

Linux <server> 3.10.0-1160.135.1.el7.x86_64 #1 SMP Tue May 13 01:53:34 EDT 2025 x86_64 x86_64 x86_64 GNU/Linux
# SEOS_load
SEOS_load: Executing un/load exit file,  /opt/seos/exits/LOAD/SEOS_load_int.always -pre
CA Privileged Access Manager Server Control seversion v14.10.80.24 - Display module's version

Copyright (c) 2018 CA. All rights reserved.

Running under:  Linux
SEOS_load: "Red Hat Enterprise Linux" Kernel: 3.10.0-1160.135.1.el7.x86_64
SEOS_load: /opt/seos/bin/SEOS_syscall.70-3100-1160-62-1-RHELX86_64.MP.ko
CA Privileged Access Manager Server Control seversion v14.10.80.24 - Display module's version

Copyright (c) 2018 CA. All rights reserved.

Running under:  Linux

File name: /opt/seos/bin/SEOS_syscall
Version  : 14.10.80.24
Created  : Feb 27 2026 21:20:14
OS info  : Kernel: 3.10.0-1160.62.1.el7.x86_64-RH79

SEOS_load: dmesg:
SEOS_load: Executing un/load exit file,  /opt/seos/exits/LOAD/SEOS_load_int.always -post
SEOS_load: SEOS_syscall WASN'T loaded
]# cat /tmp/ins_mod.tmp
insmod: ERROR: could not insert module /opt/seos/bin/SEOS_syscall: Package not installed
# ll /opt/seos/bin/SEOS_syscall
lrwxrwxrwx. 1 root root 61 Mar  4 16:04 /opt/seos/bin/SEOS_syscall -> /opt/seos/bin/SEOS_syscall.70-3100-1160-62-1-RHELX86_64.MP.ko

Environment

Affected OS are rhel 7.x and PAMSC 14.1 cp08

Cause

The problem is in the signing process of the SEOS_syscall modules. This affects rhel 7.x (7.6, 7.9 etc) on Cumulative Release cp08 

 

Resolution

Fix to install post cp08 : acpatch-DE664856-14.10.80.28-_LINUX_X64.zip

Open a case in support to request this fix

From 13 april 2026 the Cumulative Release cp08 has been republished, so this is fixed in packages after this date, visit support matrix