startup too slow

[bassey essien_1]

my server was bounced this morning after
the modification of hostname form the /sbi/set_parms. the hpux startup in process
sequence is very slow, the status indicates that it is busy, it has been rebooted for nearly 30 minutes, it seems that there is a hung process stalling clean startup. Do i need to power the system off again ?.
thanks.

[Steffi Jones_1]

Hi Bassey,

hard to say why it is hung during bootup without more information of the system.

What does the console display?
Did you check if the box has a possible hw failure? Check (if existing) for a little LED display on the box and see if you get warning mesages there too.

How did you reboot after the set_parms command?

For a try I would TOC the box. That gives you a little bit better shutdown then just powering the box off the "hard way".

Steffi Jones

[Alan Riggs]

You say that you changed the hostname. Are you using DNS for name resolution? If so, did you update the hostname on your name servers as well?

How far into the boot process did you get. Does the console show you are stuck an a particular startup script (nfs.client, for example).

[Eddie Warren]

There are a couple of things you can check. first of all when you used "set_parms" to change your hostname, is the new hostname known to the network? If it is not it will take forever for your system to come up. You can boot it to single user by doing "cntrl b" then "rs" to restart the system. At the prompt you have 10 seconds to halt boot proces, hit your spacebar to interrupt. at the ISL prompt type "hpux -is" to boot to single user. At this point your can create an alias for your new hostname and old hostname in your /etc/hosts file. for example.

192.0.0.192 new_host_name Old_host_name

Reboot and it should be able to resolve this if your new_host_name was unknown to the network.

Regards

[Devbinder Singh Marway]

Have you changed your IP address ? and do you have NFS running , I have seen in the past , if the ip address has been changed and the /etc/hosts file has not been changed then it will wait, and the only way to overcome this is to boot into single user mode , and edit the hosts file.

If this is not the case , then specify at which point it is hanging ?