HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

Server not creating a crash dump after it panics.

 
John E. Goetz
Frequent Advisor

Server not creating a crash dump after it panics.

I have a HP Integrity blade BL870 running 11.31 that crashed with a kernel panic but did not create a dump file. Here is my crash settings:
uxprdb04:root# crashconf
Crash dump configuration has been changed since boot.

CLASS PAGES INCLUDED IN DUMP DESCRIPTION

UNUSED 1054822 no, by default unused pages
USERPG 2797683 no, by default user process pages
BCACHE 93551 no, by default buffer cache pages
KCODE 11317 no, by default kernel code pages
USTACK 16716 yes, by default user process stacks
FSDATA 14 yes, by default file system metadata
KDDATA 1230064 yes, by default kernel dynamic data
KSDATA 7531 yes, by default kernel static data
SUPERPG 23429 no, by default unused kernel super pages

Total pages on system: 5235127
Total pages included in dump: 1254325

Dump compressed: ON

Dump Parallel: ON

DEVICE OFFSET(kB) SIZE (kB) LOGICAL VOL. NAME

1:0x000002 2088032 1048576 2:0x000001 /dev/vx/dsk/rootdg/swapvol
1:0x000003 544896 26214400 2:0x583220 /dev/vx/dsk/swapdg/swapvol01
------------
27262976
9 REPLIES
melvyn burnard
Honored Contributor

Re: Server not creating a crash dump after it panics.

what does the savecrash config file say?
and what does the shutdown log indicate was the crash? MCA?
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
John E. Goetz
Frequent Advisor

Re: Server not creating a crash dump after it panics.

Both savecrash and /etc/shutdownlog have no entries for this crash.
sujit kumar singh
Honored Contributor

Re: Server not creating a crash dump after it panics.

can the O/P of /etc/rc.config.d/savecarsh as well as that of /etc/rc.config.d/crashconf be posted.

is the crash dunp to be saved at some non-default directory than /var/adm/crash.
regards
Sujit
John E. Goetz
Frequent Advisor

Re: Server not creating a crash dump after it panics.

I have attached both outputs.
John E. Goetz
Frequent Advisor

Re: Server not creating a crash dump after it panics.

Attached crashconf PDF.
John E. Goetz
Frequent Advisor

Re: Server not creating a crash dump after it panics.

Attached savecrash PDF.
Don Morris_1
Honored Contributor

Re: Server not creating a crash dump after it panics.

What's in the console log at the time of the crash? (The crash panic stack or MCA information should be there, and whether a dump was saved or not should also be there).
John E. Goetz
Frequent Advisor

Re: Server not creating a crash dump after it panics.


End of Stack Trace

linkstamp: Sat Oct 10 09:11:09 CDT 2009
_release_version: @(#) $Revision: vmunix: B.11.31_LR FLAVOR=perf
Calling function e000000001a30b20 for Shutdown State 1 type 0x2
LLT INFO V-14-1-LLT links disabled because of panic

sync'ing disks (0 buffers to flush):
GAB WARNING V-15-1-20057 Port h process 12455 inactive 7 sec
GAB WARNING V-15-1-20057 Port h process 12455 inactive 8 sec
GAB WARNING V-15-1-20057 Port h process 12455 inactive 9 sec
GAB WARNING V-15-1-20057 Port h process 12455 inactive 10 sec
GAB WARNING V-15-1-20057 Port h process 12455 inactive 11 sec
GAB WARNING V-15-1-20057 Port h process 12455 inactive 12 sec
GAB WARNING V-15-1-20057 Port h process 12455 inactive 13 sec
GAB WARNING V-15-1-20057 Port h process 12455 inactive 14 sec
GAB WARNING V-15-1-20058 Port h process 12455: heartbeat failed, killing process
GAB INFO V-15-1-20059 Port h heartbeat interval 15000 msec. Statistics:
GAB INFO V-15-1-20129 Port h: heartbeats in 0 ~ 3000 msec: 38310621
GAB INFO V-15-1-20129 Port h: heartbeats in 3000 ~ 6000 msec: 0
GAB INFO V-15-1-20129 Port h: heartbeats in 6000 ~ 9000 msec: 0
GAB INFO V-15-1-20129 Port h: heartbeats in 9000 ~ 12000 msec: 0
GAB INFO V-15-1-20129 Port h: heartbeats in 12000 ~ 15000 msec: 0
GAB INFO V-15-1-20088 System information:
GAB INFO V-15-1-20089 number of cpu: 4
GAB INFO V-15-1-20090 physical memory: 20940508 K
GAB INFO V-15-1-20091 free memory: 5381608 K
GAB INFO V-15-1-20095 load average in 1 min: 0. 60
GAB INFO V-15-1-20096 load average in 5 min: 0. 71
GAB INFO V-15-1-20097 load average in 15 min: 0. 77
GAB INFO V-15-1-20099 pageout rate: 0
1 fcache page still dirty
0 buffers not flushed
0 buffers still dirty
i 0 pfn 0x1 pages 0x9f
i 1 pfn 0x100 pages 0x3dc2e
i 2 pfn 0x3e19a pages 0x38e
i 3 pfn 0x3fc00 pages 0x148
i 4 pfn 0x3fd4c pages 0xa
i 5 pfn 0x3fd7e pages 0x6
i 6 pfn 0x3fde6 pages 0x6
i 7 pfn 0x100000 pages 0x400000
i 8 pfn 0x10040000 pages 0xbf1fe
i 9 pfn 0x100ff200 pages 0xe00
*** Not enough CPUS for a compressed dump ***

*** A system crash has occurred. (See the above messages for details.)
*** The system is now preparing to dump physical memory to disk, for use
*** in debugging the crash.

*** The dump will be a SELECTIVE dump with
compression OFF and concurrency ON: 5242 of 20450 megabytes.
*** To change this dump type, press any key within 10 seconds.
*** Proceeding with selective dump, with compression off and concurrency on.

Primary Dump Header Location :
Device details:
Major number: 31 Minor number:0x61000

Loading 'SysROM:Floating-Point Software Assistance Handler'...
-- 'SysROM:Floating-Point Software Assistance Handler' returned Success
Loading 'SysROM:Broadcom Gigabit Ethernet Driver'...
sujit kumar singh
Honored Contributor

Re: Server not creating a crash dump after it panics.

Hi

in the file /etc/rc.config.d/savecrash can you uncomment these two lines.

# SAVECRASH=1
# SAVECRASH_DIR=/var/adm/crash

to

SAVECRASH=1
SAVECRASH_DIR=/var/adm/crash

and see

regards
sujit