topic Re: cfg2html hangs in Operating System - HP-UX

cfg2html hangs

Rick Garland — Thu, 26 Oct 2006 14:19:02 GMT

Hi all:

HPUX 11.11 rp7420
1 npar 4vaps
STM = A.52.00
PHKL_31847 installed (supercedes PHKL_29798)

Running the cfg2html hangs at the Diags collection. Per the instructions of the cfg2html I have STM greater than A.42 and I have the PHKL patch installed

What else should I be looking for?

Thanks

Re: cfg2html hangs

Steven E. Protter — Thu, 26 Oct 2006 14:49:09 GMT

Shalom Rick,

A different version of cfg2html.

If its from another source get another version. If its from HP file a bug report.

SEP

Re: cfg2html hangs

Rick Garland — Thu, 26 Oct 2006 15:11:21 GMT

Hi SEP:

Using the one from Ralph Roth (come.to/cfg2html)

I didn't know that HP was putting out the cfg2html

Is this the HP version?

Re: cfg2html hangs

Ivan Krastev — Thu, 26 Oct 2006 18:06:57 GMT

I see somewhere that cfg2html have problem when staring OnlineDiags - the program cannot operate normally when the root user is shadowed - you have root:x:... in passwd file. In that case script cannot su to root users and OnlineDiags hangs. The solution is listed in cfg2html:

#echo "Problem If cfg2html hangs on Hardware, press twice ENTER"
#echo " or Ctrl-D. Then check or update your Diagnostics!"
echo "WARNING USE AT YOUR OWN RISK!!! :-))"

":-))" is my favorite part

regards,
ivan

Re: cfg2html hangs

Petr Simik_1 — Fri, 27 Oct 2006 05:50:59 GMT

I experienced , my cfg2html hanged on HW problem when it reads cfg from the system. Can you something in log generated by cfg2html? Check the last line in the output, this causes the problem.

Re: cfg2html hangs

Rick Garland — Mon, 30 Oct 2006 09:32:32 GMT

I went ahead and bounced the system since I had the downtime. The DIAGs created all kinds of problems since the reboot.

The load on the system went up dramatically (> 12) and brought the system to a crawl.

Killed the DIAGs and turned off from boots. System holds steady now. Call to HP says that the firmware is 6 revs behind!

The firmware is to be updated tonight.

I am expecting this to resolve the issue. Will let you know.