/sbin/rc2.d/S340net not found

[ITeam]

Hi,

I have a problem with an rx4640 it crashed in the night and had to have its processor extender board replaced. When I boot the server it comes up ok; however there are errors in /etc/rc.log saying /sbin/rc2.d/S340net not found - I've looked in /sbin/rc2.d and all of the files (links) appear to be there and pointing to /sbin/init.d/net is there and is viewable. I tried running the command from the command line but get the same error. This message is displayed for several other files in /sbin/rc2.d but it doesn't appear for all files in /sbin/rc2.d so I'm confused as to whats happening. I can't start S340net so have no network connection other than console. At the moment I am recovering sbin/rc2.d directory from backup tape and was going to overwrite the current sbin/rc2.d directory - then try rebooting and see if this has sorted the problem out - can anyone advise something diferent, or has anyone seen this problem before if so how did you fix it.

Many thanks

Annelise

[Duncan Edmonstone · Accepted solution]

Annelise,

This could be down to any number of things, but a hunch says it might be a typo in a config file in /etc/rc.config.d (as these are the ones that are more likely to get changed by hand than anything in the /sbin/rcX.d directories.

Check the config files in /etc/rc.config.d are all OK by starting a sub-shell and sourcing each one in turn. This should do this for you:

sh
ls /etc/rc.config.d/* | while read x
do
echo $x
. $x 2>&1
done | more
exit

This will print a list of the files in /etc/rc.config.d - If any of them have bogus entries then you should see a:

sh .... not found

message on the following line.

Remember to exist the subshell after you are done, as these commands will have stuffed a load of entries into you shells environment which you don't want.

HTH

Duncan

[ITeam]

Hi thanks for response I did that and the only one that had a@not found@ on the following line was:

/etc/rc.config.d/netconf

I've looked in this file and it appears to look ok - any ideas?


Cheers,

Annelise

[Duncan Edmonstone]

Annelise,

There's something in that file it doesn't like...

run :

cat -v /etc/rc.config.d/netconf

And look for any strange characters (cat -v shows any strange non-printable characters in the file). I'm afraid you're just going to have to go through it very carfeully...

HTH

Duncan

[Bill Hassell]

Also check that the parent directories did not get clobbered by the failure:

ll -d / /sbin /sbin/init.d /etc /etc/rc.config.d

drwxr-xr-x 29 root root 8192 Jun 19 12:36 //
dr-xr-xr-x 31 bin bin 8192 Jul 28 12:59 /etc/
drwxr-xr-x 2 bin bin 8192 Dec 3 2006 /etc/rc.config.d/
dr-xr-xr-x 14 bin bin 8192 Feb 23 20:20 /sbin/
dr-xr-xr-x 2 bin bin 8192 Dec 3 2006 /sbin/init.d/

Because of the random failures you're seeing, I would suspect filesystem corruption. Run a full fsck on the / filesystem. Also run swverify (if it will run at all). You may have a lot more wrong than just a few startup links. Look at /etc/rc.log to see what else is broken.

[Aashique]

Hi,
Please remove your link file and create the link file again.

Thanks & Regards

A. Aashique

[ITeam]

Hi all,

Thanks for the prompt responses, I eventually sorted the problem out - it was a problem with the /etc/rc.config.d/netconf file - after fixing this file I manually ran /sbin/rc2.d/S340net start - and it worked fine, so I reboot serve and it cam up fine.

Thank you all for your prompt responses,

Cheers,

Annelise

[ITeam]

see previous notes - corruption in /etc/rc.config.d/netconf