1833387 Members
3097 Online
110052 Solutions
New Discussion

syslog.log

 
Dan Lukac
New Member

syslog.log

Every second I have a process recorded in my syslog file.
An example is:
Feb 14 07:41:01 cars1 inetd[948]: lpn2/tcp: bind: Address already in use
Feb 14 07:41:01 cars1 inetd[948]: lnp2/tcp: Service enabled
How can I get this to stop getting these entries in the syslog?
5 REPLIES 5
Rita C Workman
Honored Contributor

Re: syslog.log

I haven't had my coffee yet...so hope I'm reading this right.
It looks like you have logging for inetd functions enabled. If you don't want these things recording in syslog - you need to turn off a couple things.

1. Edit /etc/inetd.conf remove that -l at the end of the telnet line.
2. Edit /etc/rc.config.d/netdaemons change that line that says export INETD_ARGS="-l" to ARGS=""

Then you can stop and restart inetd
/sbin/init.d/inetd stop
/sbin/init.d/inetd start

Hope this helps/rcw
Mike Williams_3
Advisor

Re: syslog.log

Hi,
It's possible you are trying to start two daemons utilising the same tcp port. Note the service lpn2 uses in /etc/inetd.conf - then check /etc/services for the port number.

Make sure there is not another entry in inetd.conf which uses a service with the same port number.

Hope that helps.

Mike
Donald Branch
Occasional Contributor

Re: syslog.log

Sounds to me like you have to inetd's running that will give you address already in use.
It' not over until the fat lady sings!
Richard Darling
Trusted Contributor

Re: syslog.log

I got this problem when we added U/SQL server and the startup script that came as part of the package uses port 7000. That port was already in use. After I changed the port to 7001 the problem and messages went away.
RD
Dan Lukac
New Member

Re: syslog.log

Thanks for you replies. In the inedt.conf file my arguement was lpn and it saw this as
a double entry.