cancel
Showing results for 
Search instead for 
Did you mean: 

hp ux boot sequence error help

 
SOLVED
Go to solution
Vincent_5
Super Advisor

hp ux boot sequence error help

Hi Guys,

      Can anyone help, Im having the error message below when I boot up my rx2800 server . Can someone advice.

Boot Up sequence

/sbin/rc[102]: -d: not found

 

/sbin/auto_parms: DHCP access is disabled (see /etc/auto_parms.log)

 

/sbin/rc2.d/S130pfilboot[5]: -d: not found.

/sbin/rc2.d/S131ipfboot[5]: -d: not found.

/sbin/rc[24]: /sbin/rc2.d/S21perf: not found.

/sbin/rc2.d/S590Rpcd[30]: -d: not found.

/sbin/rc2.d/S700acct[39]: -d: not found.

/sbin/rc2.d/S900drd[21]: -d: not found.

/sbin/rc2.d/S999tcpisn: ndd: not found.

/sbin/rc3.d/S823hpws22_apache[44]: -d: not found.

/sbin/rc3.d/S823hpws22_tomcat[46]: -d: not found.

Regards

Vincent

 

nothing is better than to know more
4 REPLIES 4
Patrick Wallek
Honored Contributor

Re: hp ux boot sequence error help

My first guess is that there is a "-d" somewhere in one of the files in the /etc/rc.config.d directory that shouldn't be there.

 

Try doing:

# cd /etc/rc.config.d

# grep "-d" *

 

See what that returns.

 

Dennis Handly
Acclaimed Contributor
Solution

Re: HP-UX boot sequence error help

> grep "-d" *

 

Quoting the "-d" won't help.  You need: grep -e -d *

Patrick Wallek
Honored Contributor

Re: HP-UX boot sequence error help

>>Quoting the "-d" won't help.  You need: grep -e -d *

 

You are correct.  Or you could just escape the "-d"

# grep "\-d" *

 

 

Bill Hassell
Honored Contributor

Re: hp ux boot sequence error help

 The entire directory (/etc/rc.config.d) content is executed many times during bootup, so you cannot have any temporary or junk files there. Start by seeing what has recently changed: 

# ls -lrt /etc/rc.config.d

 New and recently changed files will appear at the bottom of this listing.
Check to see if there is a file named:  -d
If there is , you'll have to remove it like this: rm -- -d

If that isn't the problem, then one of the files that has been recently added or edited is the culprit. Look in these files for -d which is the error source.



Bill Hassell, sysadmin