usually if the system is experiencing panic, then the investigation which is conducted from the coredump, but sometimes not coredump file is created .. follows the steps to be able to make the coredump file
root # tail -f /var/adm/messages | grep savecore
Sep 14 11:08:58 myserver savecore: not enough space in /var/crash/myserver (2094 MB avail, 3634 MB needed)
hohoho...size in /var not enough for save this coredump..
root # df -h /tmp
swap                    47G   255M    46G     1%    /tmp
root # mkdir /tmp/corecore
root # cd /tmp/corecore
root # savecore -Ld .
dumping to /dev/dsk/c0t9d0s0, offset 65536, content: kernel
100% done: 282920 pages dumped, compression ratio 4.86, dump succeeded
System dump time: Tue Sep 14 13:38:16 2010
Constructing namelist ./unix.0
Constructing corefile ./vmcore.0
100% done: 282920 of 282920 pages saved
root #
savecore with option :
-L     Save  a  crash  dump  of  the  live  
        running Solaris  system,   without actually rebooting
        or altering the  system  in  any  way.
-d     Disregard  dump  header  valid  flag.  Force
       savecore  to  attempt  to  save a crash dump
       even if the header information stored on the
       dump  device  indicates the dump has already
       been saved.
--- $ ---
Thursday, September 16, 2010
Subscribe to:
Post Comments (Atom)
 
 
0 komentar:
Post a Comment