PAMSC error seoswd: Exec of /opt/CA/PAMSC/bin/SEOS

Products

CA Privileged Access Manager - Server Control (PAMSC)

Issue/Introduction

We noticed that in /var/log/messages of all servers (any RedHat release) where PAMSC is installed, every hour we have the following error lines:

seoswd: Exec of /opt/CA/PAMSC/bin/SEOS_load failed (errno 2) [No such file or directory]

Environment

PAMSC 14.1 cp06

Cause

The periodic syslog messages are explained by the watchdog attempting to unload the SEOS kernel module in case it is unused as per the following two tokens in seos.ini:

; Specifies whether to attempt to unload unused seos kernel modules.
; Default Value: yes
unload_unused_seos = yes

; Interval between attempting to unload unused seos kernel modules
; Default Value: 1 Hour
unload_unused_seos_interval = 3600

Resolution

unload_unused_seos = no

Additional Information

The periodic syslog messages are explained by the watchdog attempting to unload the SEOS kernel module in case it is unused as per the following two tokens in seos.ini:

; Specifies whether to attempt to unload unused seos kernel modules.
; Default Value: yes
unload_unused_seos = yes

; Interval between attempting to unload unused seos kernel modules
; Default Value: 1 Hour
unload_unused_seos_interval = 3600

I would recommend disabling that feature on Linux (i.e., setting token unload_unused_seos to no. On RHEL PIM runs as a service controlled by systemd, so external management of its functionality should be avoided in order not to get service into a faulty/unknown state.

--

and the error shown in the "Exec of /opt/seos/bin/SEOS_load failed (errno 2) [No such file or directory]" message is misleading because it is reported not immediately after failed exec API call and apparently a non-fatal errno=2 occurs in the code between exec and actual logging.