This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
aix:dump [2021/01/01 21:21] 127.0.0.1 external edit |
aix:dump [2023/01/10 17:15] (current) manu |
||
---|---|---|---|
Line 81: | Line 81: | ||
transfer mode: binary | transfer mode: binary | ||
</code> | </code> | ||
+ | |||
+ | ===== Analyse system dump ===== | ||
+ | |||
+ | A system dump indicates a severe problem with an AIX system. System dumps usually halt the system, necessitating a reboot. | ||
+ | |||
+ | <cli prompt='#'> | ||
+ | [root@labotest]/root# errpt | ||
+ | 67145A39 0413095315 U S SYSDUMP SYSTEM DUMP | ||
+ | </cli> | ||
+ | |||
+ | To copy the core, be sure to have enough space ! | ||
+ | |||
+ | Copy the system dump from dumpdevice to a file | ||
+ | <cli prompt='#'> | ||
+ | [root@labotest]/root# savecore -f -d /tmp | ||
+ | </cli> | ||
+ | |||
+ | Next, uncompress the dump using the dmpuncompress command, uncompress can be very big! | ||
+ | <cli prompt='#'> | ||
+ | [root@labotest]/root# dmpuncompress vmcore.0.BZ | ||
+ | </cli> | ||
+ | |||
+ | |||
+ | Lastly, format the dump: | ||
+ | <cli prompt='#'> | ||
+ | [root@labotest]/root# /usr/lib/ras/dmprtns/dmpfmt -c vmcore.0 | ||
+ | This dump appears complete - The end-of-dump component was found. | ||
+ | </cli> | ||
+ | |||
+ | |||
+ | Lastly, format the dump: | ||
+ | <cli prompt='#'> | ||
+ | [root@labotest]/root# /usr/lib/ras/dmprtns/dmpfmt -c vmcore.0 | ||
+ | </cli> | ||
+ | |||
+ | Analyse the dump: | ||
+ | <cli prompt='#'> | ||
+ | [root@labotest]/root# kdb vmcore.0 vmunix.0 | ||
+ | </cli> | ||
+ | |||
+ | Like using the dbx | ||
+ | <cli prompt='>'> | ||
+ | (0)> stat | ||
+ | SYSTEM_CONFIGURATION: | ||
+ | CHRP_SMP_PCI POWER_PC POWER_6 machine | ||
+ | with 2 available CPU(s) (64-bit registers) | ||
+ | |||
+ | SYSTEM STATUS: | ||
+ | sysname... AIX | ||
+ | nodename.. lpar_name | ||
+ | release... 1 | ||
+ | version... 7 | ||
+ | … lines omitted … | ||
+ | time of crash: Mon Apr | ||
+ | 13 09:52:09 2015 | ||
+ | age of system: 13 day, | ||
+ | 18 hr., 37 min., 28 sec. | ||
+ | xmalloc debug: enabled | ||
+ | FRRs active... 0 | ||
+ | FRRs started.. 0 | ||
+ | |||
+ | CRASH INFORMATION: | ||
+ | CPU -1 CSA 053A7E80 | ||
+ | at time of crash, error code for LEDs: | ||
+ | 70000000 | ||
+ | </cli> | ||
+ | |||
+ | This output contains key details. It tells you when your system crashed, along with your AIX version and when the system was installed. It also gives you an LED code (70000000 in this example) that mirrors the LED on the outside of your p Systems box. 70000000 is a program interrupt. | ||
+ | |||
+ | Now for the most telling command in this initial dump run-through. From your kdb prompt, enter "status": | ||
+ | <cli prompt='>'> | ||
+ | (0)> status | ||
+ | CPU INTR TID TSLOT PID | ||
+ | PSLOT PROC_NAME | ||
+ | 0 15000D9 336 6A006A 106 | ||
+ | sysdumpstart | ||
+ | 1 1B0037 27 F001E 15 | ||
+ | wait | ||
+ | 2-3 Disabled | ||
+ | </cli> | ||
+ | |||
+ | https://techchannel.com/SMB/02/2017/analyzing-aix-system-dumps |