ia64_corehw defunct OnlineDiag

[Maurinho]

RP8420 HP-UX 11.11 v1 running OnlineDiag B.11.11.18.05 Support Tools Bundle Dec 2006.
CSTM Version A.53.05 (Product B4708AA).
Patched with PHSS_35808 .
ia64_corehw zombie.
Ha anyone encountered this problem with Ver A.53.05 ( Patch PHSS_35808 ) and how to fix?

Thanks

[Torsten.]

Hi,

regarding the "defunc" read this:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=837725&admit=-682735245+1181242298746+28353475

The "ia64_corehw" is running on a PA_RISC system with 11.11 too, see

http://docs.hp.com/en/diag/ems/emd_ia64core.htm

"...On cellualr systems, these errors will be reported to the Forward Progress Log (FPL). The monitor will make these available to the FPL Monitor (fpl_em) for further processing.

On HP-PA systems, the monitor will receive the PCI error data and make it available to the FPL monitor (fpl_em) for further processing..."

[Torsten. · Accepted solution]

Also see this:

http://www4.itrc.hp.com/service/cki/docDisplay.do?docLocale=en&docId=emr_na-c00961919-1

"...HP-UX STM: ia64_corehw processes exist; is this normal?

...

This is normal, and does not indicate any problem ..." (followed by some explainations)

[Aussan]

i saw this a wile ago but forgot the link to it..it's normal

"The parent ia64_corehw periodically (every minute) forks a child to process one of the log files. The child exits as soon as it has finished doing so (which is usually very soon after starting, as there are not many log entries added). The parent process only checks for the child exiting every minute, so until that time the child shows as "defunct". (If the child was still alive, processing the log file, then a new one would not be forked.)

This is known behavior, and is not optimal, but it is not incorrect behavior. It is not having any effect on the system beyond the overhead of forking the child process and dealing with its cleanup each time.

There are currently no plans to change this.

If it is causing a problem beyond being unexpected, please give details either here or via HP support. "

[Andrew Merritt_2]

Hi Maurinho,
Yes, it's perfectly normal to see a child of ia64_corehw; see the references above which explain why this is so. If you watch, you should notice that the process id of the child is changing (so in fact it is not the same child). There is only a problem if the same child process is there for more than a minute, or if there are multiple children. If either of those cases applies, please contact HP support.

Andrew

[Maurinho]

Thanks for all the responses..

Have a nice day..

[Maurinho]

Thanks..