Operating System - HP-UX
1751900 Members
5000 Online
108783 Solutions
New Discussion юеВ

Re: Ignite core dump problem

 
SOLVED
Go to solution
Fabian Brise├▒o
Esteemed Contributor

Ignite core dump problem

Hello guys, im getting this message when running an ignite backup with make_net_recovery:



/dev/vg25/lvsapdata65 /oracle/SMP/sapdata65 0

** 0 - The Volume Group or Filesystem is Not included in the
System Recovery Archive
** 1 - The Volume Group or Filesystem is Partially included in the
System Recovery Archive
** 2 - The Volume Group or Filesystem is Fully included in the
System Recovery Archive

* Checking Versions of Recovery Tools
Memory fault(coredump)


I'm using ignite version Ignite-UX C.7.9.260, this started happening when I installed this new version, since then I have uninstalled and installed again and problem continues, I have the same version on all clients this is the only one giving me problems, I also runned the following command:

swlist -l fileset Ignite-UX
# Initializing...
# Contacting target "msmxpd"...
#
# Target: msmxpd:/
#

# Ignite-UX C.7.9.260 HP-UX System Installation Services
Ignite-UX.BOOT-COMMON-PA C.7.9.260 Common Boot Components for PA-RISC clients
Ignite-UX.BOOT-KRN-11-11 C.7.9.260 Installation Boot Kernel for B.11.11 clients
Ignite-UX.BOOT-SERVICES C.7.9.260 Network Boot Services for System Installations
Ignite-UX.CD-TOOLS C.7.9.260 Tools for creating CD media
Ignite-UX.CD-TOOLS-DOC C.7.9.260 Documentation for CD-TOOLS
Ignite-UX.CD-TOOLS-SRC C.7.9.260 Source for CD-TOOLS
Ignite-UX.DVD-TOOLS C.7.9.260 Tools for creating DVD media
Ignite-UX.DVD-TOOLS-DOC C.7.9.260 Documentation for DVD-TOOLS
Ignite-UX.DVD-TOOLS-SRC C.7.9.260 Source for DVD-TOOLS
Ignite-UX.FILE-SRV-11-11 C.7.9.260 File Archives Used By Clients During HP-UX Install
Ignite-UX.IGNITE C.7.9.260 Graphical Ignite User Interface for Installations
Ignite-UX.IGNT-ENG-A-MAN C.7.9.260 Ignite-UX Manual Pages
Ignite-UX.IGNT-JPN-E-MAN C.7.9.260 Ignite-UX Japanese EUC Manual Pages
Ignite-UX.IGNT-JPN-S-MAN C.7.9.260 Ignite-UX Japanese SJIS Manual Pages
Ignite-UX.MGMT-TOOLS C.7.9.260 Tools for Managing Data Files on an Ignition Server
Ignite-UX.RECOVERY C.7.9.260 System disaster recovery tools

as you can see there are no software verision problems.


also checked /var/adm/syslog/syslog.log and found nothing, any help you could provide would be great. If you need any info please let me know.

Thanks in advanced.
Knowledge is power.
28 REPLIES 28
Raj D.
Honored Contributor

Re: Ignite core dump problem

Fabian,

What syntax are you using with the make_net_recovery ,

Check this out:
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=812024


Also:
- whether the backup completed successfuly at the end.
- what is the message at the end of the recovery.log file.


Hth,
Raj.
" If u think u can , If u think u cannot , - You are always Right . "
Michael Steele_2
Honored Contributor

Re: Ignite core dump problem

Hi

From a thread:

"...but fixed this by increasing the kernel parameter maxssiz from 8mb to 16mb:
received a SIGSEGV for stack growth failure.
Possible causes: insufficient memory or swap space,
or stack size exceeded maxssiz.

What is maxssiz and related kernel parms?
Support Fatherhood - Stop Family Law
Fabian Brise├▒o
Esteemed Contributor

Re: Ignite core dump problem

Hello guys, thanks for the reply.
Box config.
O.S: HPUX 11.11
RAM: 30 GB

Sintax I am using:
/opt/ignite/bin/make_net_recovery -s ig5470 -A -n 3 -P s -x inc_entire=vg00 -x exclude=/SAParchives -x exclude=/usrtemporal -x exclude=/var/adm/crash -v

output of swapinfo -tam
Mb Mb Mb PCT START/ Mb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 4096 0 4096 0% 0 - 1 /dev/vg00/lvol2
dev 5008 98 4910 2% 0 - 0 /dev/vg00/lvswap2
dev 5008 99 4909 2% 0 - 0 /dev/vg00/lvswap3
dev 5008 98 4910 2% 0 - 0 /dev/vg00/lvswap4
dev 5008 98 4910 2% 0 - 0 /dev/vg00/lvswap5
reserve - 23128 -23128
memory 23886 5161 18725 22%
total 48014 28682 19332 60% - 0 -


kernel values
maxssiz 0x800000
maxssiz_64bit 0x800000
maxswapchunks 12065
maxtsiz 0x4000000
maxtsiz_64bit 0x40000000

I am checking the thread you sent me.
Knowledge is power.
Michael Steele_2
Honored Contributor

Re: Ignite core dump problem

I'm confused, you have duplicater max's.

Also, list in dec please.
Support Fatherhood - Stop Family Law
Fabian Brise├▒o
Esteemed Contributor

Re: Ignite core dump problem

attaching recovery.log

Knowledge is power.
Fabian Brise├▒o
Esteemed Contributor

Re: Ignite core dump problem

max_thread_proc 256
xx maxdsiz 990056448
xx maxdsiz_64bit 4294967296
xx maxfiles 1024
xx maxfiles_lim 2048
xx maxssiz 8388608
xx maxssiz_64bit 8388608
xx maxswapchunks 12065
xx maxtsiz 67108864
xx maxtsiz_64bit 1073741824
Knowledge is power.
Michael Steele_2
Honored Contributor

Re: Ignite core dump problem

Hi

SIGSEGV is a segmentation fault and associated to stack growth.



http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1379087&admit=109447626+1255725561412+28353475

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=587531

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=11110

Possible patches
PHCO_38226

Didn't see anything in that attachment. What about these?

server:/var/opt/ignite/clients/0x00306E4B1A17/install.log

client: /var/opt/ignite/local/install.log
Support Fatherhood - Stop Family Law
Dennis Handly
Acclaimed Contributor

Re: Ignite core dump problem

>Memory fault(coredump)

Have you analyzed your corefile with gdb? Gotten a stack trace and register dump?
gdb ignite-executable core
(gdb) bt
(gdb) info reg
(gdb) disas $pc-4*16 $pc+4*4
(gdb) q

>Michael: SIGSEGV is a segmentation fault and associated to stack growth.

Possibly. But since it didn't say that, it isn't so likely.
That's why you need to look at the core file.
Luitzen
Occasional Advisor

Re: Ignite core dump problem

Hello,

I've got the same problem. We've two kinds of systems: one with HP-UX EOE 11.23 and the T2775BA bundle and one with HP-UX EOE 11.23 and the T2777BA bundle.

All systems with the T2775BA bundle have a correct make_net_recovery but those ones with the T2777BA bundle fail with the same "Memory fauke(coredump)"

Falling back to the C.7.4.155 Ignite-UX.RECOVERY fileset solves the problem but gives the expected warning of the older version of the software...