rc script hung on bootup

[John Peace]

K580
HP-UX 11.0

The server is located 6 hours away. I administer it remotely. I have someone at the site that can "turn the key" on.

Problem:

The server went down hard. There was a power outage at the site. When the server was turned back on, it started its boot process. It is hung after /sbin/rc2.d/S742diagnostic. The next script is /sbin/rc2.d/S744predictive.

I have checked the syslog and tombstones files. I can find no errors. Where else can I look? I only boot up to run level 2. I have a database package running, and 50 people connected. I have already planned a reboot later tonight.

What can I do to research the problem?

[Elmar P. Kolkman]

To start with, search for child processes of the script by doing "ps -ef | grep "
and then of all the found subprocesses, so you know what command hangs.

Do you have access to the console? Perhaps it is waiting for some user-input or the buffer of your console driver is full...

[T G Manikandan]

Just check /etc/rc.log.

check the STm logs

/var/stm/logs/os

Try stating manually the /usr/sbin/stm/uut/bin/sys/diagmond

This should start other services

REvert

[RAC_1 · Accepted solution]

When you have a reboot later tonight, Boot into single user mode, move sbin/rc2.d/S742diagnostic to sbin/rc2.d/TS742diagnostic. This will stop diagnostics.

When booted, try starting it manually and check. Also check if you are upto date on STM.

[John Peace]

No access to the console.

I had already checked the rc.log This is the tail of it:

# tail rc.log
----------------------------
cron started

Support Tools Informational Fileset
Output from "/sbin/rc2.d/S740supprtinfo start":
----------------------------

Start diagnostic subsystem
Output from "/sbin/rc2.d/S742diagnostic start":
----------------------------

Thats as far as it got. I will check patches. I am pretty sure I am up to date on this server ( I have 10 all configured the same). I will rename the startup tonight and manually start it.

[John Peace]

I renamed S742diagnostic, rebooted machine. Came up fine. I manually ran /sbin/init.d/diagnostic, it started. I renamed S742diagnostic back and rebooted machine. Everything came up fine. ? I did not change anything. Never know?

[Todd McDaniel_1]

One other thing, IF you can direct someone with console access...

The / key will abort a startup script. This will get you past the error next time.

[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

[Muthukumar_5]

Stop to start /sbin/rc2.d/S742diagnostic service on bootup. Start it manually after coming to terminal.

Change,

DIAGNOSTICS=0

on /etc/rc.config.d/diagnostic file.

It will not start that script. Are you getting any errors on syslog or console when starting up this.

--
Muthu