K Class Server with unusual long bootup time running HPUX 11.11

[javasoup]

Hi All, I'm facing this problem of extremely long bootup time for my server. It wasn't like this previously, i'm using a K580 running HPUX 11.11.

Currently it took 1hr 30mins to bootup. I've logged a case to investigate the problem but i would like to put it on forum to discuss with the experts.

Previously it took only 20mins, now i tried using single user mode and bootup to 3rd level, it took only 15mins.

I have simply no idea what is wrong with the normal bootup, could anyone kindly tell me how to look for the source of this long bootup problem?

I figured it that there might be some hardware monitoring process that needs a long time to process during the bootup before HPUX.

Anyone has any advise, please give me some tips, thanks!

Sincerely,
Edmund

[Arunvijai_4]

Hi Edmund,

it could be due to hardware monitoring process (diag) used by STM. You can simply disable it from startup. Go to /etc/rc.config.d/diagnostic and change DIAGNOSTICS=1
to DIAGNOSTICS=0 and save the file. It won't be started next time when you boot the server.

-Arun

[Muthukumar_5]

Same problem like,

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=291790

Try to remove the startup of diagnostic service on boot up time. Start it manually after successfully login.

May be patch update is needed.

--
Muthu

[Devender Khatana]

Hi,

If you monitor the boot process then at which point it seems to be stucked for very long. Disabling the same can lead to rectification of this problem.

HTH,
Devender

[Ted Buis]

I have seen problems in file systems and bad disks cause boot up to take very long times (hours), so check syslog.log to see what is in there once it boots, and dmesg.

[marie-noelle jeanson_1]

Hi,

Generally, long boot time may be due to file system, Veritas, or some init script taking a long time. You can always try to check the syslog file and see if you fiond anything abnormal there.

Marie.

[RAC_1]

Where does it spend most of the time?? Check /etc/rc.log file. also when it is booting up, monitor and note down where it spends most of the time. Also make sure that you do not have any unnecessary files in /sbin/init.d/ and in /etc/rc.config.d/ directory. The directory /etc/rc.config.d should have only the config files and nothing else.

[Don Mallory]

A couple of suggestions:

Does any ioscan -fn run with a reasonable return speed after boot?

I had a situation where a system was attached to a SAN (VA7400) without Secure LUN Manager enabled, so, every LUN was visible to every node, x2 paths for a total of 300 disks visible. ioscans took forever. It also didn't help that there was a patch for ioscan.

Second thing that I've seen that helps all around, if you aren't using VxVM, uninstall it. I found boot times were reduced by as much as 10 minutes while it waited to timeout.

Otherwise, agreed, check your rc.log

Oh, and you said it's okay to runlevel 3. What happens at runlevel 4?

As an all-around good piece of advice, examing what services you have running under /etc/rc.config.d and inetd.conf and determine if you have a real need for each. Disable and/or remove as necessary or required.

This will not only reduce your possible boot time, process list, memory usage, etc., but it will also reduce what you need to patch and be a security win at the same time.

Don