SEOS_syscall file is not created
Article ID: 97865
Updated On:
Products
CA Virtual Privilege Manager
CA Privileged Identity Management Endpoint (PIM)
CA Privileged Access Manager (PAM)
Issue/Introduction
[Environment]
AIX7.2 TL2
#oslevel -s 7200-02-02-1810
CA PAMSC14.0
[Issue]
Please try PAMSC14.0 on AIX7.2 TL2 box.
However, PAMSC servce is not started with "seload" command with the following errors.
# seload
CA Privileged Access Manager Server Control seload v14.00.0.654 - Loader Utility
Copyright (c) 2016 CA. All rights reserved.
SEOS_load: Executing un/load exit file /opt/CA/AccessControl/exits/LOAD/SEOS_load_int.always.
sysconfig[SYS_SINGLELOAD]: path(/opt/CA/AccessControl/bin/) module(/opt/CA/AccessControl/bin/SEOS_syscall) err(2) : No such file or directory
AIX7.2 TL2
#oslevel -s 7200-02-02-1810
CA PAMSC14.0
[Issue]
Please try PAMSC14.0 on AIX7.2 TL2 box.
However, PAMSC servce is not started with "seload" command with the following errors.
# seload
CA Privileged Access Manager Server Control seload v14.00.0.654 - Loader Utility
Copyright (c) 2016 CA. All rights reserved.
SEOS_load: Executing un/load exit file /opt/CA/AccessControl/exits/LOAD/SEOS_load_int.always.
sysconfig[SYS_SINGLELOAD]: path(/opt/CA/AccessControl/bin/) module(/opt/CA/AccessControl/bin/SEOS_syscall) err(2) : No such file or directory
Environment
AIX7.2 TL2
#oslevel -s 7200-02-02-1810
CA PAMSC14.0
#oslevel -s 7200-02-02-1810
CA PAMSC14.0
Cause
In AIX7.2TL2(oslevel : 7200-02-02-1810)
The "install_base" script cannot get correct OS version information.
So,a SEOS_syscall file is not created.
The "install_base" script cannot get correct OS version information.
So,a SEOS_syscall file is not created.
Resolution
Please apply acpatch-DE362670-14.01.0.454-_AIX5.zip.
Feedback
Yes
No
Powered by
