Problem to Unload Syscall after appying package 14.10.70.x

Products

• CA Privileged Access Manager - Server Control (PAMSC)

Issue/Introduction

Trying to install package 14.10.70.116  you see that active syscalls cannot be unloaded

# SEOS_load -u
SEOS_load: Executing un/load exit file,  /opt/seos/exits/LOAD/SEOS_unload_int.always -pre
Ports - nothing to do ...
SEOS_load: Executing un/load exit file,  /opt/seos/exits/LOAD/SEOS_unload_unab.always -pre
ERROR: cannot unload SEOS_syscall.
       There are active system calls.
       Run secons -scl to list active system calls.

and

# SEOS_load -u
SEOS_load: Executing un/load exit file,  /opt/seos/exits/LOAD/SEOS_unload_int.always -pre
Ports - nothing to do ...
UNIX sockets - nothing to do ...
SEOS_load: Executing un/load exit file,  /opt/seos/exits/LOAD/SEOS_unload_unab.always -pre

successfully disabled module seos_1410_70_113.
rmmod: ERROR: Module seos_1410_70_113 is in use
ERROR: cannot unload SEOS_syscall.
SEOS_load: Executing un/load exit file,  /opt/seos/exits/LOAD/SEOS_unload_int.always -post
SEOS_load: Executing un/load exit file,  /opt/seos/exits/LOAD/SEOS_unload_unab.always -post

 

When Check_active_syscalls aborts the unloading of the syscall, syscall remains marked as active, it keeps /proc/seos_enabled
Then after applying the fix, when we start etrust, the new syscall is not loaded

Environment

PAMSC 14.1 cp07

Cause

The previous changes that added check_active_syscalls() in SEOS_load was intended to provide correct message and improve performance but it failed to disable the SEOS_syscall module.  Without disabling the module, when restarting PAMSC after applying a patch, the new SEOS_syscall module will not be loaded.  Instead, the still active SEOS_syscall module will continue to be used. 

Resolution

Open a case in support to obtain the following package,  The fix is to disable the module when attempting to unload but finding there are still active processes.

DE652024/14.10.70.127/acpatch-DE652024-14.10.70.127