AIX Frequently Asked Questions and Debugging Tips for CommandCentral Storage
Sharing a few knowledgebase articles with the CommandCentral Community. Please respond to this forum if you find these useful.
---------------------------------------------------------------
Document ID: 316604
http://support.veritas.com/docs/316604
How do I display process information on an AIX host?
/usr/bin/topas -P
How do I display available and configured swap space on an AIX host?
/usr/sbin/swap -l and /usr/sbin/swap -s:
Example Output:
# uname -a
AIX hal-ibmp610-1 2 5 0007B76A4C00
# /usr/sbin/swap -l
device maj,min total free
/dev/hd6 10, 2 512MB 508MB
#
# /usr/sbin/swap -s
allocated = 131072 blocks used = 770 blocks free = 130302 blocks
How do I display system errors on an AIX host?
/usr/bin/errpt -a
How do I determine the amount of paging space on an AIX host?
lsps
Other utilities:
svmon
vmstat
How do I capture and examine core files on an AIX host?
/usr/bin/errpt prints the stack traces written into AIX system logs.
errpt -aJ CORE_DUMP > /tmp/coreInfo.out
errpt can be used to capture the complete system logs too:
errpt -a > /tmp/syslogs.out
/usr/bin/snapcore can be used to collect a core and all the associated files, so that we have chance of getting a better stack on our in-house machines:
snapcore /var/VRTSccs/VRTShal/data/process/ApplicationExplorers/core /opt/VRTSccs/VRTShal/bin/wrap/halrun
Note: the /opt/VRTSccs/VRTShal/bin/halrun is a shell-script wrapper file which invokes the actual binary /opt/VRTSccs/VRTShal/bin/wrap/halrun. You must specify the actual binary, not the wrapper script.
To analyze the snapcore image:
tar extract it on an AIX host,
cd into the "snapcore" directory that the tarfile extraction created, and
run the following dbx command, including parameters (the name of the core will be different, i.e., not core.052808):
root@spcibm8:/nkapling/snapcore> dbx -p /opt=./opt:/usr=./usr opt/VRTShal/bin/wrap/halrun core.052808
Type 'help' for help.
[using memory image in core.052808]
reading symbolic information ...warning: "/usr/lib/libC.a(shrcore.o)" has changed since core creation
warning: "/usr/lib/libC.a(ansicore_32.o)" has changed since core creation
warning: is newer than ./opt/VRTShal/lib/librmm_xml_t.a
warning: Unable to access address 0x2f2f6d86 from core
pthreaded.c, 6076: PTHDB_CALLBACK (callback failed)
Segmentation fault in strcpy.strcpy [./opt/VRTShal/lib/liboraexp.so] at 0x31deabec
0x31deabec (strcpy+0x8c) 94e50004 stwu r7,0x4(r5)
(dbx) where
strcpy.strcpy() at 0x31deabec
oraDiscover.strcpyFPcPCc(0x339b7040, 0x339b6840), line 64 in "string.h"
unnamed block in getInstanceStatus(instance_t*)(instance = 0x2d586d78), line 730 in "oraDiscover.cpp"
getInstanceStatus(instance_t*)(instance = 0x2d586d78), line 730 in "oraDiscover.cpp"
/usr/bin/procstack displays the stack backtrace of an executing process.
procstack <PID>
procstack is available in 5.2 and 5.3 machines, but it works only on running processes (i.e., it accepts a PID) and not on cores.
Related Documents:
314431: Operating Systems Frequently Asked Questions and Debugging Tricks (r 1.17)
http://support.veritas.com/docs/314431
________________________________________
Products Applied:
CommandCentral Storage 5.0, 5.0 MP1, 5.0 MP1 RP1, 5.0 MP1 RP2, 5.0 MP1 RP3, 5.1
Last Updated: January 23 2009 10:54 PM GMT
Expires on: 12-14-2018
Subjects:
AIX
Information Development: Troubleshooting
CommandCentral Storage
Admin Tools/Utilities: Cli, Diagnostics
Languages:
English (US)
Operating Systems:
AIX
5.2, 5.3
Comments
thanks for the info!
thanks for the info!
Definitely helped me as I'm
Definitely helped me as I'm only a Windows guy. =)
Please mark my post as solution to help others also if it resolved your issue.
Would you like to reply?
Login or Register to post your comment.