To facilicate a LINUX core dump, follow these steps:
(NOTE: These example commands are only applicable to a SAM server.)
Running from the command line:
<BASEDIR>/smarts/bin/sm_server -n InCharge-SAM -c ics -b localhost:427 --ignore-restore-errors --output --daemon
To confirm it's stopped, execute:
<BASEDIR>/smarts/brcontrol
When it's installed as a service:
<BASEDIR>/smarts/bin/sm_service stop InCharge-SA1. Enable core file dumping
To confirm the service is stoppped, execute:
<BASEDIR>/smarts/sm_service show
<BASEDIR>/smarts/ulimit -c unlimited
Running from the command line:
<BASEDIR>/smarts/bin/sm_server -n InCharge-SAM -c icf --bootstrap=bootstrap-am-pm.conf -b localhost:427 --output --daemon
To confirm the domain has started, execute this command:
<BASEDIR>/smarts/bin/brcontrol
When it's installed as a service:
<BASEDIR>/smarts/bin/sm_service start InCharge-SAM
To confirm the domain has started, excecute this command:
<BASEDIR>/smarts/bin/sm_service show
<base dir>/SAM/smarts/bin
<base dir>/SAM/smarts/local/logs
/home/usr
To cause a memory dump to happen at will, follow one of these two suggestions.
Running GDB:
(gdb) attach <pid>
(gdb) generate-core-file <optional-filename>
(gdb) detach
NOTE: If you cannot generate a core file because gdb is not installed, you can use "gdb" which is shipped with Smarts products (located at <Base dir>/smarts/bin/gdb) to generate a core file. This can be done as follows:
Edit the following commands into a file called gcore.gdb:
set pagination off
set width 65536
gcore
detach
quit
Run the following command:
smarts/bin/gdb -x gcore.gdb -p <pid>
Using the kill signal command:
kill -s SIGABRT <pid>
NOTE: Look for the memory dump files in the folder where the application was started from, or from these locations:
<base dir>/SAM/smarts/bin
<base dir>/SAM/smarts/local/logs
/home/usr