missing some scripts

[simon_164]

I have the error on shutdown:

/sbin/rc2.d/K177hpws_apache[46]: 1: not found.
/sbin/rc2.d/K177hpws_tomcat[46]: 1: not found.
/sbin/rc2.d/K177hpws_webmin[45]: 1: not found.
/sbin/rc2.d/K177hpws_webproxy[44]: 1: not found.
/sbin/rc2.d/K177hpws_xmltools[42]: 1: not found.
/sbin/rc1.d/K300acct [39]: 1: not found.
/sbin/rc1.d/K410Rpcd[30]: 1: not found.
/sbin/rc1.d/K604runner[21]: 1: not found.


and the error on startup:

/sbin/rc2.d/S130pfilboot[5]: 1: not found.
/sbin/rc2.d/S131ipfboot[6]: 1: not found.
/sbin/rc2.d/S590Rpcd[30]: 1: not found.
/sbin/rc2.d/S606runner[21]: 1: not found.
/sbin/rc2.d/S700acct[39]: 1: not found.
/sbin/rc3.d/S823hpws_apache[46]: 1: not found.
/sbin/rc3.d/S823hpws_tomcat[46]: 1: not found.
/sbin/rc3.d/S823hpws_webmin[45]: 1: not found.
/sbin/rc3.d/S823hpws_webproxy[44]: 1: not found.
/sbin/rc3.d/S823hpws_xmltools[42]: 1: not found.


Any one have an idea? why i am missing these files?

[Victor Fridyev · Accepted solution]

Hi,

It looks that APACHE has been uninstalled wrongly.
Install it and the messages will disappear.

HTH

[OldSchool]

have any of the following occurred recently:

swinstall (possibly one that failed)
swremove
recent patching?

it looks like either some web services were removed, or that they didn't get all the way installed

[Peter Nikitka]

Hi,

I don't think, a file or command '1' is missing. I think, there is an invalid assignment to variables.
Look at this:

a= 1 # blank seperated
will result in
ksh: 1: not found

Check for such changes in
/etc/rc.config.d/*

mfG Peter

[simon_164]

I have a typical another server, do you think copying the scripts will be a good idea?

I checked Apache it seems ok, no unusual swremove has been done different than the other server. maybe some changes in /etc/rc.config.d/nfsconf but nothing more.

[Jonathan Fife]

I would bet that you have a file somewhere in /etc/rc.config.d that has some bad syntax.

Try the following (as just a normal user, not root):

set -x
. /etc/rc.config

See if the error pops up, and then see what fname= was immediately above it. The fname is a file, so look in /etc/rc.config.d at that file and see if there is a syntax issue somewhere.

[James R. Ferguson]

Hi Simon:

You don't have missing scripts but rather a corrupted file(s) in '/etc/rc.config.d/'.

If you look at the comments in '/etc/rc.config' you will see that files in this directory are expected to follow a strict naming convention if they are not to be processed during startup and shutdown.

When '/sbin/rc' runs, the '/etc/rc.config.d' directory is examined by the script '/etc/rc.config'. This script skips any file whose basename contains an "extension" that begins with the characters [.,~#].

Thus, it is permissible to have 'netconf' and 'netconf.old'. The '.old' backup will *not* be processed.

If, however, you had kept an old version of your 'netconf' file named as, 'oldnetconf', then *both* 'netconf' and 'oldnetconf' would be sourced. Since the letter "o" follows "n", the result would be undesirable insofar as the last variable declarations seen would be from the wrong file.

One way to find bogus files that cause prolems is to do:

# sh -vx /etc/rc.config 2>&1|more

Regards!

...JRF...

[OldSchool]

Check the directory contents in:
/etc/rc.config.d

If you do an ls -l, I'd almost bet you will find it comes up with trash, like a filename w/ control characters or something along those lines, maybe a 1.

this is related to your other post as well

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1050553

as the rpc daemons aren't coming up

the file listed are complaining about a file "1" not being found. The scripts referred to are running /etc/rc.config
which in turn tries to "source" files in /etc/rc.config.d.

[simon_164]

sh -vx --- did not show anything i can understand as errors.
ls -l also did not show any particular error.
I am comparing with a different system, I am having the same scripts and file on both systems in the same location. Any other idea?

[Patrick Wallek]

Try this:

# cd /etc/rc.config.d
# grep "= 1" *

And see what comes back. If anything is returned, the edit the script and remove the space between the = and the 1. There should never be and spaces between the variable names, the = signs and the values in any files. Everything should look like:

VAR=0
VAR=1