Operating System - HP-UX
1748065 Members
5714 Online
108758 Solutions
New Discussion юеВ

Re: Ignite core dump problem

 
SOLVED
Go to solution
Raj D.
Honored Contributor

Re: Ignite core dump problem

Fabian,


You have Ignite-UX 7.9.260 and looks it is very latest version,
>Do you have the pax cumulative patch installed correctly as per the latest Ignite-UX version .

# swlist -l product | grep -i pax


- What is the model of the server:


- Also as per the release note it says few core dump issue has been fixed in this version,

Ignite-UX version C.7.9.260 contains the following new features:
http://docs.hp.com/en/5992-5096/5992-5096.pdf

- Fixes for the following Change Requests:
* QXCR1000930732. Ignite-UX installs and rescan_hw_host involving
B.11.23 will no longer core dump and terminate when multi-pathed
devices are inventoried and some paths to the disk are "bad". Such
disks will be presented for install, and the itool interface will
no longer display disk device paths which are known to be "bad" for
possible selection.



Hth,
Raj.
" If u think u can , If u think u cannot , - You are always Right . "
Luitzen
Occasional Advisor

Re: Ignite core dump problem

Hello Fabian,

we didn't have the latest pax patch, we're running with the 2004 version:

PHCO_31634 1.0 Cumulative changes to pax(1)

I've updated to the latest version:

PHCO_39677 1.0 Cumulative changes to pax(1)

and tried to make a new make_net_recovery. This is the result:

# /opt/ignite/bin/make_net_recovery -A -P s -s igniteserver -x exclude=/var/adm/crash -x exclude=/tmp -x exclude=/var/tmp

* Creating NFS mount directories for configuration files.

======= 10/26/09 10:02:46 MET Started /opt/ignite/bin/make_net_recovery. (Mon
Oct 26 10:02:46 MET 2009)
@(#)Ignite-UX Revision C.7.9.260
@(#)ignite/net_recovery (opt) Revision:
/branches/IUX_RA0909_WEB/ignite/src@78846 Last Modified: 2009-08-13
14:15:12 -0600 (Thu, 13 Aug 2009)

* Checking Versions of Recovery Tools
Memory fault(coredump)

The message following the Version Check should be:

* Scanning system for IO devices...

I don't know id pax is in the picture, there's been no archiving done yet.

Kind regards, Luitzen
Dennis Handly
Acclaimed Contributor

Re: Ignite core dump problem

>Luitzen: I don't know if pax is in the picture, there's been no archiving done yet.

Please create your own thread so you can assign points. If there is something useful here, you can include a URL.

If you use "file core" you can see if created by pax.
Luitzen
Occasional Advisor

Re: Ignite core dump problem

Sorry to interrupt this thread, I thought it would be useful to hear about someone having the same problem... I will follow this thread silently...

Kind regards, Luitzen
Dennis Handly
Acclaimed Contributor

Re: Ignite core dump problem

>Luitzen: I thought it would be useful to hear about someone having the same problem.

Only if you have a suggestion/solution. :-)
Sorry, which I guess you did:
Falling back to the C.7.4.155 ... solves the problem
Fabian Brise├▒o
Esteemed Contributor

Re: Ignite core dump problem

Thanks for the replys.
My O.S is 11.11 running on a hp9000 rp4440.

I had ignite version C.7.5.142 installed and everithing worked fine.
I upgraded to version C.7.9.260, and that's when problems started.

The reason I upgraded is that I updated the ignite version on all ignite clients and server, this is the only server that is giving me problems.


Hello Dennis, I havent analized the core file with GDB.

gdb, where do I download this ?
I found this, HP WDB, is this the same as GDB ??

Luitzen, bundle T2775BA ??


RAJ.
I have patch PHCO_32438 1.0 pax(1) cumulative patch installed on the server having problems.

I checked a server that I recently patched and that server has pax patch PHCO_35998 1.0 pax(1) cumulative patch, maybe I could patch to sse if it works but luitzen keeps getting the problem ??

this is the set of patches I have installed,

Gold Applications Patches for HP-UX 11i v1, December 2004
Gold Base Patches for HP-UX 11i v1, December 2004

And if I do a bdf this is diplayed:
ig5470:/var/opt/ignite/clients
20480000 15095296 5343928 74% /var/opt/ignite/recovery/client_mnt

im not seing this mounted on other clients.


im will continue to analyze the server.

Thanks a lot for your input.
Knowledge is power.
Luitzen
Occasional Advisor

Re: Ignite core dump problem

Fabian,

T2775BA is a Serviceguard CFS (veritas 4.1) bundle. I've no problems on those servers.

For our Oracle-RAC clusters we need a more expensive version: T2777BA wich is the same including RAC extensions. With that bundle the Ignite problem starts....

Kind regards, Luitzen
Dennis Handly
Acclaimed Contributor

Re: Ignite core dump problem

>gdb, where do I download this? I found this, HP WDB, is this the same as GDB?

http://www.hp.com/go/wdb
Yes, provided you invoke it as gdb. And not the wdb GUI.
Fabian Brise├▒o
Esteemed Contributor

Re: Ignite core dump problem

I have runned gdb. This is the output, if im running it wrong please let me know, as always thanks for your help.

msmxpd:/opt/ignite/bin> /opt/langtools/bin/gdb64 /opt/ignite/bin/make_net_recovery -c core
Detected 32-bit executable.
Invoking /opt/langtools/bin/gdb32.
HP gdb 6.0 for PA-RISC 1.1 or 2.0 (narrow), HP-UX 11i
and target hppa1.1-hp-hpux11.00.
Copyright 1986 - 2009 Free Software Foundation, Inc.
Hewlett-Packard Wildebeest 6.0 (based on GDB) is covered by the
GNU General Public License. Type "show copying" to see the conditions to
change it and/or distribute copies. Type "show warranty" for warranty/support.
..
warning: Load module /opt/ignite/bin/make_net_recovery has been stripped

(no debugging symbols found)...

warning: core file may not match specified executable file.
Core was generated by `make_net_recov'.

warning: make_net_recov is 14 characters in length. Due to a limitation
in the HP-UX kernel, core files contain only the first 14 characters
of an executable's name. Check if make_net_recov is a truncated name.
If it is so, core-file, packcore and other commands dealing with
core files will exhibit incorrect behavior. To avoid this, issue
exec-file and symbol-file commands with the full name of the executable
that produced the core; then issue the core-file, packcore or other
core file command of interest.

Program terminated with signal 11, Segmentation fault.

(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...
#0 0xc0197998 in + 0x8 () from /usr/lib/libc.2
Knowledge is power.
Fabian Brise├▒o
Esteemed Contributor

Re: Ignite core dump problem

Hello.
A bit more information

msmxpd:/> what /usr/lib/libc.2
/usr/lib/libc.2:
malloc.c $Date: 2007/01/09 16:25:15 $Revision: r11.11/14 PATCH_11.11 (PHCO_35743)
$ PATCH_11.11/PHCO_35743 Jan 22 2007 04:25:33 $
Knowledge is power.