Boot failure messages

[Pamela Hammitt]

After recovering from tape to a new harddrive, my system has a few fails when booting. I have looked at the logs, but they don't say very much, any ideas???

Configure LAN interfaces: FAIL
/sbin/rc2.d/S350outbound_promisc: adb: not found.

HP OpenView License Manager: FAIL
/sbin/rc2.d/S604ovlmd start" failed

/sbin/rc2.d/S901almd start" ERROR (Unknown error occurred).

Thanks for your insights...I'm new at this...
Pam

[Steven E. Protter · Accepted solution]

These messages are relatively self explanatory.

A softlink or binary that a softlink is pointing too in /sbin/rc2.d is missing.

It would appear also that either a LAN interface is missing, or has failed.

I would do the following, if the machine actually booted:

ioscan -fnC lan or btlan

run the mstm or cstm or xstm utility and use the excercize test on all lan cards to see if they are working properly.

Check the softwlinks in /sbin/rc2.d

ll /sbin/rc2.d/S350outbound_promisc


If the system does not boot there are limited hardware diagnostics available from the boot console which you get by restarting the server and pressing a console key at the 10 second prompt.

Or do a hardware call.

Openview is probably failing due to the LAN card issue.

SEP

[A. Clay Stephenson]

The first one appears easy. The absolute debugger appears to be missing. It's normal location is /usr/bin.

I would try to execute each of these manually and note any errors.

e.g.

/sbin/rc2.d/S604ovlmd start

[Kent Ostby]

/sbin/rc2.d/S350outbound_promisc

This doesnt appear to be a standard script but was likely written locally.

The error probably indicates that the script is calling "adb" instead of "/usr/bin/adb".

I think you just need to fix the path.

Not sure on the other two although the suggestion of trying to start them manually is a good place to start.

[Stephen Keane]

S350outbound_promisc is a softlink in /sbin/rc2.d that linked to the script /sbin/init.d/outbound_promisc. The script /sbin/init.d/outbound_promisc usually contains the following

echo 'lanc_outbound_promisc_flag/W 1' | adb -w /stand/vmunix /dev/mem

As you can see, it doesn't have a path on adb (which should be /usr/bin/adb or /bin/adb)

Whether you actually need the script is another matter. It is usually found on older HPUX 10 boxes and its purpose was to turn on a kernel switch at boot time. It's all to do with capturing outbound packets.