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

Products

• 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

Issue/Introduction

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

 

Environment

Policy server version :12.8.X
component: Policy Server
OS : Linux

Resolution

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 the process is running as a service account replace the * with the service account (example smpolicysrv). Service  will have to  be restarted 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 
DAEMON_COREFILE_LIMIT=’unlimited’ 

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

### Additional insights

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

-Also check to ensure  the location of the cores file via the 'sysctl -p' command.

-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.

For Policy Server:
pkgapp -ir -p <Current active pid value for the smpolicysrv> -a <$nete_ps_root/bin/> -c <path to the core file> -s <path to store the output> 

example)

$ su -       ---> pkgapp will collect OS level system logs which require root access # source /opt/CA/siteminder/ca_ps_env.ksh       ---> Need access to Policy Server environment variables # cd $NETE_PS_ROOT # ps -ef |grep smpolicysrv And this returns PID 1234 # md -p /tmp/smps-crash # /app/pkgapp -ir -p 1234 -a /opt/CA/sitemindre/bin/smpolicysrv -c /opt/CA/siteminder/core.1234 -s /tmp/smps-crash       ---> Follow the message displayed by pkgapp, it will show you were the files are stored.

For Access Gateway
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 <secure proxy server installation/bin/> -c /var/tmp/cores/core.124 -s /var/tmp/storage