OE upgrade error

[chethan]

am doing OE upgrade from 11.11-11.23-11.31,I didnt face any problems in 11.11-11.23 but while upgrading to 11.31, at the final stage i got the error:

Pid 4557 received a SIGSEGV for stack growth failure.
Possible causes: insufficient memory or swap space,
or stack size exceeded maxssiz.
/var/adm/sw/tmp/update-ux/update-ux[109]: 4557 Memory fault(coredump)
ERROR: SWM terminated with errors without rebooting the system. See
/var/opt/swm/swm.log for details.
NOTE: Take appropriate corrective action and re-run update-ux to complete
the update.

======= Mon Apr 2 20:54:56 IST 2007 END update-ux
Possible causes: insufficient memory or swap space,
or stack size exceeded maxssiz.
/var/adm/sw/tmp/update-ux/update-ux[109]: 4557 Memory fault(coredump)
ERROR: SWM terminated with errors without rebooting the system. See
/var/opt/swm/swm.log for details.
NOTE: Take appropriate corrective action and re-run update-ux to complete
the update.

After this I ran the command:
kctune -s maxssiz=70611392
I got the following error:
ERROR: The requested changes could not be applied to the currently
running system, for the following reasons:
- The module 'adt' depends on the interface 'HPUX_11_31_PERF',
version 1.0, which is not supplied by any available kernel
module.
ERROR: The requested changes could not be held for next boot, for the
following additional reasons:
- The kernel rejected the proposed tunable value change.

Pls help me out in resolving this issue

[Steven E. Protter]

Shalom,

Version dot zero of 11.31 and its upgrade program.

No surprise it doesn't work. upgrade-ux has been broken since HP-UX 9.

Restore your Ignite backup and be happy your systemn runs 11.31.

SEP

[chethan]

No.. i cant agree this... i did OE upgrade from 11.23(0609)--> 11.31(0702) recently..
it was working fine....

[Dennis Handly]

You need to report this stack overflow to the Response Center, perhaps they have a solution.

It seems your idea of increasing maxssiz had merit but I don't know why kctune should complain about a dynamic tunable. What is the value of maxssiz_64bit? What was the old value of maxssiz?

You may want to use gdb on your corefile to see if you are in a recursive stack overflow. If so, you can't solve those by increasing maxssiz.

[chethan]

the following are the current values:
maxssiz=8388608
maxssiz_64bit=8388608

what is gdb? how to use it on corefile?

[Dennis Handly]

>the following are the current values:
maxssiz=8388608

That might be a little small.

>what is gdb? how to use it on corefile?

gdb is the wdb debugger. You can download it from http://www.hp.com/go/wdb

To execute:
$ gdb executable core
(gdb) bt
(gdb) q

Using "file core" may give you the executable or you must find it in the script:
/var/adm/sw/tmp/update-ux/update-ux[109]: 4557 Memory fault(coredump)

Probably on line 109.

[Darren Etheridge_2]

I too received this message when upgrading 11.23 to 11.31. Was there a resolve to the problem? If so, what was it?

[Eric SAUBIGNAC]

Bonjour,

Just got the same problem while trying to update latest HP-UX 11.23 (0712) to 11.31 (1403). Found nothing by myself, found nothing around the web too (but this post ;-), so the answer came from HP support. Thanks to them.

11.23 is now rather old, but because there are still some 11.23 boxes or VM that should be upgraded to 11.31, I guess that the solution has still some interest ?

In a few words, don't install "linker + fdp cumulative patch" newer than PHSS_42043 : with newer patches there is a compatibility issue between swm and libdl.so.1 . No issue of this kind known with PHSS_42043 or older.

If a newer patch is installed, remove it. In my own case patch PHSS_43742 was installed. Removing it also removes patch PHSS_43732 "LIBCL patch". No obvious side effect. And in fact, in most cases, we don't have to take care of any side effect on a 11.23 system since it is going to be upgraded to 11.31

Of course to easly downgrade patches, you must have kept something in /var/adm/sw/save ...

Hope this will help someone

Eric