How to speed up boot when networking isn't working?

[Geoff Wild]

This has been bothering me for 12 years now...

Had to reboot a 11.31 server today - and now it looks like something is misconfigured in the networking....

Configure LAN interfaces ...................................... FAIL *

then it arrives at:

Starting sendmail [Done] Starting sm-client [Done] ............

and taks about 20 minuts or so to time out...

then:

Start Runner ..................................................

and that's been waithing now for over 20 minutes...

Why does HP-UX take so long to boot if networking isn't working?

Why can't something be added to any package that if networking isn't available - then it won't attempt to start?

Maybe I answered my own question - just add a check in every /sbin/init.d/ script to see if networking was OK on startup...

Sigh....

Rgds...Geoff

[Geoff Wild]

Well - runner took about 40 minutes....

[Bill Hassell]

Historically, NFS and sendmail (especially current versions) will hang for a very long time when the primary LAN doesn't work. I've seen this since the days of 10.20. Since there isn't a list of hang-safe tests, I would try adding lanscan, netstat -in and perhaps lanadmin tests to these common networked-based rc scripts. Probably DCE too.

[Dennis Handly]

Did you want to do this automatically? Or is a manual process ok?
You could try hitting control shift \ to abort the current step.

[Geoff Wild]

ctrl shift \

Never tried that before...

Currently I't at the last rc script - but that has been hanging for about 20 minutes now...

Usage: /sbin/rc3.d/S900sapinit {start|stop|status|restart} ....


Looks like that script isn't clean...

Unfortunately - "ctrl shift \" doesn't seem to do anything....

Rgds...Geoff

[Dennis Handly]

>Unfortunately - "ctrl shift \" doesn't seem to do anything.

You may have to do it multiple times?

[John Payne_2]

(crtl shirt \) will only skip the current step if that step is listening for a signal. If it's stuck waiting on something else, and not listening, your results will vary.

You could try a couple of times, spaced apart, it's possible for the script to be in a piece of code that is ignoring you for the moment, you might come back to it when it's ready to pay attention to you...

Hope it helps
John

[Geoff Wild]

Had to:

vparreset -p vpar1104 -h

then

vparboot -p vpar1104 -o "-is"

Then in single user, fix the typo in the netconf, and reboot...

Rgds...Geoff

[Lars Christian Nilsen]

I would like to add that Ctrl-| actually works and really got things moving when LAN is misconfigured! Kudos to John for this tip

(Sorry for not giving away points since I'm not the initiator of the tread)

cheers,
Lars C

[Yong Mann Wai]

hi Geoff,

i am currently facing the same problem with that slow boot up. i usually hit Enter several times in the hope to accelerate the boot.

i also have the problem with netconf. didn't restart the server before doing network configuration changes and netconf was screwed up with similar entries of IP addresses in different interfaces.

what's worse: server hung while trying to get into CDE

got to use Ctrl + Shift + | to edit netconf.

i'm waiting for the server to boot up successfully while i'm typing this.

[Steven E. Protter]

Shalom,

boot to single user and disable network and network services in /etc/rc.config.d

Thats how I would do it.

I like your check for networking. Can we see the code. PLEASE!!!!

SEP

[Yong Mann Wai]

i can now see my CDE, but i get "the desktop messaging system could not be started" error.

looks like lots of trouble.

[Jeeshan]

first you can disable the network services and also with LAN interface to sppedup the system.

then check if any services left which are system hungry or need to resolve any other dependencies.

[Yong Mann Wai]

i've read somewhere about looking at dr_dt.

time is running today so i'll try tomorrow.

[Geoff Wild]

Solution was single user mode.

[Bakari]

my work is sap basis. i have same perplexity.
i find solution in sap Official Website .

Post Installation/Fix an already installed SAP system:

Edit /home/adm/.login and comment out (with #) the following line:

#eval `tset -s -Q -m ':?hp' `

Pre-Installation/Update HP-UX OS before installing SAP system

Edit the .login template file /etc/skel/.login and comment out the following line:

#eval `tset -s -Q -m ':?hp' `



Installing SAP after this should create a correct version of /home/adm/.login