IP/TCP Parameters Via NDD

[Bob Ferro]

I have a question. When looking through the rc.log or doing a sendmail start, I receive the following messages about IP/TCP parameters not found. What does this mean? I issued a ndd -get and the following shows their values:

Starting sendmail [ OK ] Starting sm-client [ OK ]
Output from "/sbin/rc2.d/S540sendmail start":
----------------------------
/sbin/rc2.d/S540sendmail[115]: ip_forward_src_routed: not found.
/sbin/rc2.d/S540sendmail[115]: ip_respond_to_echo_broadcast: not found.
/sbin/rc2.d/S540sendmail[115]: tcp_isn_passphrase: not found.
Starting sendmail : send only [ OK ]
Starting sm-client : send only [FAILED]


ndd -get /dev/ip ip_forward_src_routed
0
ndd -get /dev/ip ip_respond_to_echo_broadcast
0
ndd -get /dev/tcp tcp_isn_passphrase 1

[mobidyc · Accepted solution]

Hello,

do you have any extra configuration in the /etc/rc.config.d/nddconf file ?

--
Regards,
Cedrick Gaillard

[Bob Ferro]

Attached is the nddconf file.

[TTr]

Can you check the S540sendmail link
ll /sbin/rc2.d/S540sendmail
See if it is linked to the right file, it should be pointing to /sbin/init.d/sendmail. Also what is in line 115 of the actual file that S540sendmail is pointing to. Something is either overwritten or wrongly edited there.

[Bob Ferro]

Here is the lines from /sbin/init.d/sendmail


114 if [ -f /etc/rc.config ] ; then
115 . /etc/rc.config

[TTr]

So the error is coming from sourcing the /etc/rc.config file which in turn is sourcing all files in /etc/rc.config.d

Check in /etc/rc.config.d if there are any additional files in it that should not be there, such as backup file of nddconf or any other file. This is what mobidyc hinted earlier.

A syntax error in any of the files in /etc/rc.config.d will throw this kind of error. Look for the recently modified files as suspects as well. If nothing obvius, you can source all the files in /etc/rc.config.d, one by one or in a loop to find out where the error is.

[Bob Ferro]

Thanks, I will check in morning and let you know.

[Bob Ferro]

There was a nddconf.org backup file in the /etc/rc.config.d directory. I am sending a request to our HQ to have the file deleted because this server is managed (root) by HQ. We don't have root acces on this server.

P.S. What is the rule about rc.config.d? I know I read it somewhere about having only certain files there.

[TTr]

If you look in /etc/rc.config, it is a script that it sources each and every file in /etc/rc.config.d. So if you make a backup copy of any file -nddconf in your case- both nddconf and nddconf.org will get sourced. And because of alphabetical order, nddconf will get sourced before nddconf.org. That means that a variable(s) that are set one way in nddconf may be changed to something wrong in nddconf.org.

And if there are syntax errors in nddconf.org processing may stop altogether and the booting process of the server may be affected. That is if the sourcing of /etc/rc.config.d files is stopped let's say at nddconf, the startup scripts that depend on files after nddconf, might not execute properly.

So the rules are, 1) when you edit files in /etc/rc.config.d be very careful that you don't make any syntax errors 2) do not leave any backup copies of files in this folder and 3) do not place any new files in this folder that are not needed by a startup script in /sbin/init.d.

[Bob Ferro]

Found the problem. In the /etc/rc.config.d/nddconf file, there was a space after the = sign that caused the error message. That would also mean that the tcp/ip parameter was never set.

[Bob Ferro]

Thanks again to everyone, I really learn a lot from this forum.