Kbase P77707: What to do when there is no core file produced on LINUX ?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/11/2008 |
|
Status: Verified
GOAL:
What to do when there is no core file produced on LINUX ?
FACT(s) (Environment):
Linux
Progress/OpenEdge Product Family
FIX:
There are times when the following message is in the database.lg file, and no core.<pid> file can be found with the same date | timestamp on the system.:
"** Save file named core for analysis by Progress Software Corporation. (439)"
The associated protrace.<pid> file will read something like the following:
PROGRESS stack trace as of Wed Apr 21 04:50:02 2004
Command line arguments are:
$DLC/bin/_mprosrv $WRKDIR/dbname -Mm 2048 -yy 1950 -cpinternal ISO8859-1 -cpstream ISO8859-1 -cpterm ISO8859-1 -cpcase Basic -cpcoll Basic -S 3201
Automatic Stack Trace Functionality not supported
In order to get the stack trace from the resulting core.<pid> file, refer to Progress Solution P58872, but first, you need the core.<pid> file.
STEPS: ( from the same terminal session )
1.) verify / set "ulimit -c" to unlimited
2.) temporarily set the permissions on the executable named in the protrace.<pid>, in the example above "$DLC/bin/_mprosrv" to 777
3.) re-start the database broker, adminserver, unified brokers - whatever is particular to your environment that is needed to re-create the issue where the core file was initially produced.
4.) now that you have the core file, you can obtain the stack trace by attaching a debugger as outlined in Solution P58872