PAMSC/PIM: can not start PAMSC on Solaris 11.4 RSU31
search cancel

PAMSC/PIM: can not start PAMSC on Solaris 11.4 RSU31

book

Article ID: 215591

calendar_today

Updated On:

Products

CA Privileged Access Manager - Server Control (PAMSC) CA Privileged Identity Management Endpoint (PIM)

Issue/Introduction

PAMSC 14.1 CP2 cannot start on Solaris 11.4 (SRU31 applied).
These error message is appeared when kernel is loading.
 
  SEOS_load: Executing un/load exit file,  /opt/CA/PAMSC/exits/LOAD/SEOS_load_int.always -pre
  SEOS_load: Adding device seos_14_10_0_XXXX.
  devfsadm: driver failed to attach: seos_14_10_0_XXXX
  Warning: Driver (seos_14_10_0_XXXX) successfully added to system but failed to attach
  Driver (seos_14_10_0_XXXX) installed.
  SEOS_load: Couldn't find device file .

Environment

Release : 14.1 CP2 (14.10.0.1265)

Component : PAM SERVER CONTROL ENDPOINT UNIX/LINUX

 OS: Solaris 11.4 : SunOS xxx 5.11 11.4.31.88.5 sun4v sparc sun4v as uname -a
 

Cause

 Solaris made changes in several internal kernel data structs in Solaris 11.4 SRU30 
 that broke many third-party kernel modules.
 This problem is one of the broken case.

Resolution

 Solaris have reverted back the changes in SRU32.
 So, please roll back to SRU29 or upgrade to SRU32 on Solaris side.

Additional Information

This problem is caused by OS change.  So, it is occurred on PIM 12.8 SP1, too.