Re: netdump issue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



----- "Anirudh Srinivasan" <srianirudh@xxxxxxxxx> wrote:

> Yes the netdump server is rhel 5 . As you suggested , i downloaded the
> rpm kernel-debuginfo.2.4.21.40.EL.i686.rpm
> and found
> 
> /usr/lib/debug/boot/vmlinux-2.4.21-40.EL.debug
> /usr/lib/debug/boot/vmlinux-2.4.21-40.ELhugemem.debug
> /usr/lib/debug/boot/vmlinux-2.4.21-40.ELsmp.debug
> 
> Upon running the crash on vmcore now this is what i get :
> 
> [root@dump 10.21.14.175-2009-01-22-14:00]# crash /usr/lib/debug/boot/vmlinux-2.4.21-40.ELsmp.debug /var/crash/10.21.14.175-2009-01-22-14\:00/vmcore
> crash 4.0-3.14
> Copyright (C) 2002, 2003, 2004, 2005, 2006 Red Hat, Inc.
> Copyright (C) 2004, 2005, 2006 IBM Corporation
> Copyright (C) 1999-2006 Hewlett-Packard Co
> Copyright (C) 2005 Fujitsu Limited
> Copyright (C) 2005 NEC Corporation
> Copyright (C) 1999, 2002 Silicon Graphics, Inc.
> Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc.
> This program is free software, covered by the GNU General Public License,
> and you are welcome to change it and/or distribute copies of it under
> certain conditions. Enter "help copying" to see the conditions.
> This program has absolutely no warranty. Enter "help warranty" for details.
>
> crash: /usr/lib/debug/boot/vmlinux-2.4.21-40.ELsmp.debug: no text and data contents
> crash: The namelist argument supplied in this case is a debuginfo file,
> which must be accompanied by the kernel file from which it was derived.
> 
> I need further help to proceed with this as i am new to rhel , kidly
> help me guide through this. I know close to achieve this just that i
> need some proper guidance.

As the error message indicates, the .debug file must be accompanied
by the kernel file from which it was derived.

In RHEL3, the /boot/vmlinux-<release> file is stripped, and its
debuginfo data is located in its assocated vmlinux.<release>.debug 
file.  So the vmlinux-<release> and/or the vmlinux.<release>.debug
files are of no use without the other.  When they are "put back
together", they become useful to the crash utility. 

The /boot/vmlinux-<release> file has an embedded link in its
header to its /usr/lib/debug/boot/vmlinux-<release> file.
Therefore, if you are running the crash utility on the system
that crashed you can enter:

 $ crash /boot/vmlinux-2.4.21-40.ELsmp <path-to>/vmcore

and the crash utility will automatically look for and find
the linked /usr/lib/debug/boot/vmlinux-2.4.21-40.ELsmp.debug
file.

Alternatively, you can just put both files on the command line,
as in:

 $ crash <path-to>/vmlinux-2.4.21-40.ELsmp <path-to>/vmlinux-2.4.21-40.ELsmp.debug <path-to>/vmcore

Note that this is only necessary for RHEL3.  In RHEL4 and beyond
the vmlinux is not split, and you only need to put the single vmlinux 
file (from the debuginfo package) on the command line.

Dave

--
Crash-utility mailing list
Crash-utility@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/crash-utility

[Index of Archives]     [Fedora Development]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]

 

Powered by Linux