SiteMinder : Capturing packages for Core files on UNIX with Policy Server
search cancel

SiteMinder : Capturing packages for Core files on UNIX with Policy Server


Article ID: 254752


Updated On:


CA Single Sign On Agents (SiteMinder) CA Single Sign On Federation (SiteMinder) CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) SITEMINDER


Steps for enabling to write core file and packaging the core file using pkgapp. 



Policy server version :12.8.X
OS : Linux


Core dump analysis, pointing out "Problem seems like a race condition with the APM Introscope agent during policy server Startup / shutdown - likely accessing a pointer that became NULL during shutdown.".


Please open a support ticket to investigate the core dumps.

Enabling Core file on Linux OS

How To Enable Core Dumps In RHEL 
1. Edit /etc/security/limits.conf, notice this is set to all processes but if you have a process running as a service account replace the * with the service account (example smpolicysrv). You will have to restart the process for this change to go into effect. 
# vi /etc/security/limits.conf 
#* soft core 0 
* soft core unlimited 

2. Edit /etc/sysctl.conf and add where to put the core file and any naming standard. 
# vi /etc/sysctl.conf 
kernel.core_pattern = /tmp/core-%e-%s-%u-%g-%p-%t 
fs.suid_dumpable = 2 
Filename variables: 
%e is the filename 
%g is the gid (groupID)the process was running under 
%p is the pid of the process 
%s is the signal that caused the dump 
%t is the time the dump occurred 
%u is the uid the process was running under 

3. Edit the /etc/sysconfig/init and set a core file limit. 

# vi /etc/sysconfig/init 

4. Check core status – validates core locations 
# sysctl -p

### Additional insights

-You may need to specify the command 'ulimit -c unlimited' before you invoke the policy server process and reproduce the crash in order to obtain a core file with the crash.

-Also check to be sure you know where the cores will be located via the 'sysctl -p' command.

-You may want to reproduce the issue 3 times so we can be sure all crashes are from the same issue.

-Pkgapp utility should be run against core files in the location the cores where initially generated.(Do not move cores to different directory before running pkgapp)

Core file packaging.

pkgapp -ir -p <Current active pid value for the secure proxy server> -a <secure proxy server installation/bin/> -c <path to the core file> -s <path to store the output> 

example:  pkgapp -ir -p 14367 -a /opt/CA/sitemider/bin/smplocysrv -c /var/tmp/cores/core.124 -s /var/tmp/storage



1669074837359__oracle_pkgapp_linux_3.6.2.tar.gz get_app