ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

What PIM (SeoS) and system information should I collect if I get a core dump on Solaris?


Article ID: 132365


Updated On:


CA Virtual Privilege Manager CA Privileged Identity Management Endpoint (PIM) CA Privileged Access Manager (PAM)


What PIM (SeoS) and system information should I collect if I get a core dump on Solaris?

My system got a kernel panic and the machine was rebooted.
I would like to investigate what may have caused the crashing condition.


Privileged Identity Manager 12.8


In order to analyze the cause of the problem, we will need the core-dump file and the seos logs.
Please follow the instructions here below in order to obtain the core file on a solaris computer:

Suggested Steps to Collect Dump Files

Go to the default crash dump directory by running:
# cd /var/crash/`uname n`

If the default crash dump directory does not exist, check the dump configuration by running:
# cd `dumpadm | awk -F' ' '/^Savecore directory/{print $NF}'`
# ls

Use the following command to find the latest dump, as it shows the next crash dump ID:
# cat bounds

If unix.n and vmcore.n don't exist but vmdump.n does, extract  unix.n and vmcore.n.
# save vf vmdump.n

Finally run the following commands to create the crash.n.tar.gz
# tar vcf crash.n.tar ./unix.n ./vmcore.n
# gzip crash.n.tar
# cksum unix.n vmcore.n crash.n.tar.gz

Open a support case in our support web site.
Attach the PIM logs and the crash.n.tar.gz file to it and provide the checksum.