aix:dump
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
aix:dump [2023/01/10 16:41] manu |
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. | A system dump indicates a severe problem with an AIX system. System dumps usually halt the system, necessitating a reboot. | ||
| Line 88: | Line 90: | ||
| 67145A39 0413095315 U S SYSDUMP SYSTEM DUMP | 67145A39 0413095315 U S SYSDUMP SYSTEM DUMP | ||
| </cli> | </cli> | ||
| + | |||
| + | To copy the core, be sure to have enough space ! | ||
| Copy the system dump from dumpdevice to a file | Copy the system dump from dumpdevice to a file | ||
| <cli prompt='#'> | <cli prompt='#'> | ||
| - | [root@labotest]/root# savecore | + | [root@labotest]/root# savecore -f -d /tmp |
| </cli> | </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: | Lastly, format the dump: | ||
| Line 100: | Line 110: | ||
| </cli> | </cli> | ||
| - | Next, uncompress the dump using the dmpuncompress command: | ||
| - | <cli prompt='#'> | ||
| - | [root@labotest]/root# dmpuncompress vmcore.0.BZ | ||
| Lastly, format the dump: | Lastly, format the dump: | ||
| + | <cli prompt='#'> | ||
| + | [root@labotest]/root# /usr/lib/ras/dmprtns/dmpfmt -c vmcore.0 | ||
| + | </cli> | ||
| - | /usr/lib/ras/dmprtns/dmpfmt -c vmcore.0 | + | Analyse the dump: |
| - | + | <cli prompt='#'> | |
| - | kdb vmcore.0 vmunix.0 | + | [root@labotest]/root# kdb vmcore.0 vmunix.0 |
| - | + | </cli> | |
| - | + | ||
| - | Reading a Dump | + | |
| Like using the dbx | Like using the dbx | ||
| Line 139: | Line 147: | ||
| 70000000 | 70000000 | ||
| </cli> | </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 | ||
aix/dump.1673365270.txt.gz · Last modified: 2023/01/10 16:41 by manu
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3
