![\"\"](\"file:\/\/\/tmp\/moz-screenshot.jpg\")
<\/p>\nWhat follows is a document I found on the forums. It can also be found on the docs.hp.com site, but this is a paraphrase, with some extra commentary.<\/p>\n
1) You need to have foresight. Before you have a crash you must enable your system to save crash dumps.<\/p>\n
2) vi \/etc\/rc.config.d\/savecrash\u00a0\u00a0\u00a0 — set the first parameter to 1. Now when your system crashes, and some day it probably will you can perform q4 analysis and send the results to HP. I think this document originated within HP. I have one written somewhere on the forums, but his one is better.<\/p>\n
<\/p>\n
<\/p>\n
\n
————————————-<\/span><\/span><\/p>\n When a 11.X HP-UX system crashes, it saves a snapshot of RAM in swap and during the reboot, copies it into \/var\/adm\/crash. Because these files are binary, a utility called \u201cq4\u201d is used to analyze them and create readable text from which the response center can determine the failure cause.<\/span><\/p>\n \n Dumps are normally saved to \/var\/adm\/crash.<\/span><\/p>\n \n Verify you have a dump to analyze by doing:<\/span><\/p>\n \n # ll \/var\/adm\/crash\/cr*<\/span><\/p>\n \n You may see:<\/span><\/p>\n \/var\/adm\/crash\/crash.0\/INDEX<\/span><\/p>\n \/var\/adm\/crash\/crash.0\/vmunix.gz<\/span><\/p>\n \/var\/adm\/crash\/crash.0\/image.0.1.gz<\/span><\/p>\n \/var\/adm\/crash\/crash.0\/image.0.2.gz<\/span><\/p>\n \/var\/adm\/crash\/crash.0\/image.0.3.gz<\/span><\/p>\n \/var\/adm\/crash\/crash.0\/image.0.4.gz<\/span><\/p>\n ^ your suffix may vary<\/span><\/p>\n \n The INDEX file contains and the \/etc\/shutdownlog contains the \u201cpanic\u201d statement. <\/span><\/p>\n \n \n The following commands must all be run from the dump directory:<\/span><\/p>\n \n cd \tto the dump directory ie: cd \/var\/adm\/crash\/crash.0<\/span><\/span><\/p>\n<\/li>\n<\/ul>\n ^^^^ ^<\/span><\/span><\/p>\n your dump dir.<\/span><\/span><\/p>\n # \t\/usr\/contrib\/bin\/gunzip vmunix.gz<\/span><\/p>\n<\/li>\n<\/ul>\n (uncompresses the kernel file \u2013 may already be done)<\/span><\/p>\n \n # \tq4prep -p <\/span><\/p>\n<\/li>\n<\/ul>\n (ignore the error if this was previously done)<\/span><\/p>\n \n Now \ttype: <\/span><\/p>\n<\/li>\n<\/ul>\n # q4 -p . <\/span><\/p>\n ^ Notice this \u2018dot\u2019<\/span><\/span><\/p>\n This will put you at the q4 utility prompt: q4><\/span><\/p>\n \n The \tnext command will get you a \u201cfingerprint\u201d of what was going on \ton the system at the time of the failure. <\/span><\/p>\n<\/li>\n<\/ul>\n \n If \tyou are working with an HP RCE at this time, type the following line \tand read the results to him:<\/span><\/p>\n<\/li>\n<\/ul>\n \n trace event 0<\/span><\/p>\n \n Otherwise, simply type this next line and continue.<\/span><\/p>\n \n trace event 0 > trace<\/span><\/p>\n \n At \tthe prompt type: include analyze.pl <\/span><\/span><\/p>\n<\/li>\n<\/ul>\n \\_letter \u201cel\u201d<\/span><\/span><\/p>\n \n At \tthe next prompt type: run Analyze AU >> ana.out<\/span><\/span><\/p>\n<\/li>\n<\/ul>\n \n At \tthe next prompt type: exit<\/span><\/span><\/p>\n<\/li>\n<\/ul>\n \n \n============================ STEP 1 ===========================<\/h2>\n
============================ STEP 2 ===========================<\/h2>\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
============================ STEP 3===========================<\/h2>\n