1834944 Members
2370 Online
110071 Solutions
New Discussion

Re: Errors in rc.log

 
Bob Ferro
Regular Advisor

Errors in rc.log

When I start or stop sendmail, I received the attach errors. Also, i receive these errors in rc.log for kminit, hostname, etc. I contactec HP but no answers yet. Can someone shed some light?
16 REPLIES 16
Michael Schulte zur Sur
Honored Contributor

Re: Errors in rc.log

Hi,

can you post the sendmail start script as attachment?

thanks,

Michael
Shaikh Imran
Honored Contributor

Re: Errors in rc.log

Hi,
This Purely seems to be the Patch Problem.
Just serch for the latest sendmail patch depending on your O.S. version and install it.

Regards,

I'll sleep when i am dead.
Victor Fridyev
Honored Contributor

Re: Errors in rc.log

Hi,

It looks like you have a problem with a file in /etc/rc.config.d directory.
Look at the string
. /etc/rc.config
in the /sbin/init.d/sendmail file and read the file /etc/rc.config.

Good luck
Entities are not to be multiplied beyond necessity - RTFM
Bob Ferro
Regular Advisor

Re: Errors in rc.log

Thanks for responding. This is not just a sendmail problem. It seems to be a system msg. When the system is boot, the rc.log contains the following but not just these:

Initialize loadable modules
Output from "/sbin/rc1.d/S112kminit start":
----------------------------
/sbin/rc1.d/S112kminit[206]: udp: not found.
/sbin/rc1.d/S112kminit[206]: tcp: not found.
/sbin/rc1.d/S112kminit[206]: ticlts: not found.
/sbin/rc1.d/S112kminit[206]: ticotsord: not found.
/sbin/rc1.d/S112kminit[206]: ticots: not found.
* All configured modules are registered successfully.

NOTE: Module status

Name ID Status Type
=====================================================
krm 1 UNLOADED WSIO

Setting hostname
Output from "/sbin/rc1.d/S320hostname start":
----------------------------
/sbin/rc1.d/S320hostname[36]: udp: not found.
/sbin/rc1.d/S320hostname[36]: tcp: not found.
/sbin/rc1.d/S320hostname[36]: ticlts: not found.
/sbin/rc1.d/S320hostname[36]: ticotsord: not found.
/sbin/rc1.d/S320hostname[36]: ticots: not found.

When I issue the /sbin/init.d/sendmail command, I received the following:

Output from sendmail start/stop script:
/sbin/init.d/sendmail[37]: udp: not found.
/sbin/init.d/sendmail[37]: tcp: not found.
/sbin/init.d/sendmail[37]: ticlts: not found.
/sbin/init.d/sendmail[37]: ticotsord: not found.
/sbin/init.d/sendmail[37]: ticots: not found.

Snedmail script is attached.
Geoff Wild
Honored Contributor

Re: Errors in rc.log

What's the contents of:

/etc/rc.config

What's the permissions on /etc/rc.config.d

Mine is:

drwxr-xr-x 2 bin bin 8192 Mar 17 12:07 rc.config.d

It almost sounds like some services are not running - can you telnet to box?

Rgds...Geoff
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
Bob Ferro
Regular Advisor

Re: Errors in rc.log

Permissions are the same as yours. Rc.config ia attached. I will check which services did not start.

Thanks
Bob Ferro
Regular Advisor

Re: Errors in rc.log

There was a file /etc/rc.config.d/netconfig with the 5 entries in it. I renamed this file to netconfig.save, stopped and started sendmail and the 5 error msgs went away. I don't know what created this file or what it is used for. Can someone shed some light on this?

Thanks again
James A. Donovan
Honored Contributor

Re: Errors in rc.log

If you look at the sendmail startup script you'll see the following lines:

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

This sources a file called rc.config, which in turn sources all the configuration files in the /etc/rc.config.d directory, including that netconfig file. The error messages were being generated by this process.

Any startup script which sourced /etc/rc.config would generate these errors.
Remember, wherever you go, there you are...
Patrick Wallek
Honored Contributor

Re: Errors in rc.log

If the file netconfig.save is not needed, GET IT OUT OF THE /etc/rc.config.d directory.

There should NEVER be ANY backup files, save files, or any files other than files that are needed in /etc/rc.config.d. ALL files in this directory get sourced. If you have a bad file in there, even if it is named something.save, then you could see unexpected results when the system boots.

Keep that directory clean.
Bob Ferro
Regular Advisor

Re: Errors in rc.log

thanks
Fredrik Hansson
Occasional Advisor

Re: Errors in rc.log

I'm new on UNIX and I've got the same problem. I also get "not found" in my rc.log file.
This is a part of the script file that generates the not-found messages. my script file (sorry about the swedish...):

...
if [ -x $STARTSCRIPT ]; then
echo "Fredrik testar ls -lrt"
ls -lrt
echo "Fredrik testar ll"
ll
echo "Fredrik testar ls"
ls
su - sas -c "$STARTSCRIPT start"
set_return
echo $NAME "started."
else

... script continues...

This is what comes out in my rc.log


...

Start SAS Metadata Server
Output from "/sbin/rc3.d/S700sas_metadataserver start":
----------------------------
Fredrik testar ls -lrt
total 5548
-r--r--r-- 1 bin bin 965 Nov 14 2000 .profile
drwxr-xr-x 2 root root 96 Aug 28 2006 lost+found
dr-xr-xr-x 23 bin bin 8192 Aug 28 2006 usr
<-- I 've cut some rows here 2 save space -->
drwx------ 2 root root 96 Apr 4 12:10 .ssh
dr-xr-xr-x 16 bin bin 8192 Apr 4 12:12 dev
drwxrwxrwx 9 bin bin 8192 Apr 4 12:13 tmp

Fredrik testar ll
/sbin/rc3.d/S700sas_metadataserver[50]: ll: not found

Fredrik testar ls
.ICEauthority
.TTauthority
.Xauthority
.dt
<-- I 've cut some rows here 2 save space -->
tmp_mnt
usr
var

/sbin/rc3.d/S700sas_metadataserver[53]: su: not found

ERROR CODE 127
SAS Metadata Server started.
"/sbin/rc3.d/S700sas_metadataserver start" FAILED

... rc.log continues...

1. Is my problem also junk in the /etc/rc.config.d/ directory?
2. How can I figure out what file(s) that aren't supposed to be there?
3. How can strange files in that folder affect the execution of my scripts?
4. How can ls -lrt work an not ll?

I have attached the startupscript and the rc.log file. I think the neccessary information is pasted in this post though.
Dennis Handly
Acclaimed Contributor

Re: Errors in rc.log

>Fredrik: I'm new on UNIX

Since you can't award points, you should start your own thread.

Basically your problem is that in a RC script, your path is probably set to /usr/sbin/.
That has ls(1) but not ll(1). You would have to use ls -l. Or if you know that /usr/bin is mounted, you can add that to the path.

>1. Is my problem also junk in the /etc/rc.config.d/ directory?

Yes, never do that.

>2. How can I figure out what file(s) that aren't supposed to be there?

Look what you changed.

>3. How can strange files in that folder affect the execution of my scripts?

Because that's the way it works. ALL files are sourced.

>4. How can ls -lrt work an not ll?

See comments about about /usr/sbin.
Dennis Handly
Acclaimed Contributor

Re: Errors in rc.log

Oops, that was:
See comments above about /usr/sbin.

When you create a new thread, you can paste in the link of a previous one if that would help explain your new one better.
Fredrik Hansson
Occasional Advisor

Re: Errors in rc.log

Thank you Mr. Handly!

You were right about the path thing. When I added the path you suggested it worked.

I'm sorry I can't give you any points for your answer. I promise, next time I'll start an own thread.

Best regards

Fredrik Hansson
Dennis Handly
Acclaimed Contributor

Re: Errors in rc.log

>I'm sorry I can't give you any points for your answer. I promise, next time I'll start an own thread.

Well, if you want to be a nice guy, you can open a new thread and I can re-respond to it. ;-)
Fredrik Hansson
Occasional Advisor

Re: Errors in rc.log