submerges /var/log/messages

[3a-informatique]

Since I'm using CentOS 5 , /var/log/messages gets submerged by the same log message all time over again:

Jun 28 17:14:13 s15394520 xinetd[2556]: START: smtp pid=22462 from=88.149.126.145
Jun 28 17:14:14 s15394520 xinetd[2556]: EXIT: smtp status=0 pid=22462 duration=1(sec)
Jun 28 17:14:21 s15394520 wdcollect[20430]: Database server connection has been established.
Jun 28 17:14:29 s15394520 xinetd[2556]: START: smtp pid=22463 from=218.48.126.30
Jun 28 17:14:31 s15394520 wdcollect[20430]: Database server connection has been established.
Jun 28 17:14:32 s15394520 xinetd[2556]: EXIT: smtp status=0 pid=22463 duration=3(sec)
Jun 28 17:14:34 s15394520 xinetd[2556]: START: smtp pid=22465 from=83.221.185.206
Jun 28 17:14:38 s15394520 xinetd[2556]: EXIT: smtp status=0 pid=22465 duration=4(sec)
Jun 28 17:14:41 s15394520 wdcollect[20430]: Database server connection has been

What's the cause and how can I fix it?

thank you

 

[IgorG]

It is not errors but just notifications. Why you want _fix_ it?

 

[3a-informatique]

take many place in the file log

wdcollect[20430]: Database server connection has been

 

[deeplist]

Any news on this? I am having the same problem. I can't even search /var/log/messages for what's important anymore because it is saturated with these notifications and I can't figure out how to disable them. Here's an example. There are several hundred per minute!!!!

Jul 5 13:49:19 saturn xinetd[2586]: EXIT: smtp status=0 pid=24336 duration=0(sec)
Jul 5 13:49:19 saturn xinetd[2586]: EXIT: smtp status=0 pid=24337 duration=0(sec)
Jul 5 13:49:21 saturn xinetd[2586]: START: smtp pid=24340 from=116.71.32.146
Jul 5 13:49:21 saturn xinetd[2586]: EXIT: smtp status=0 pid=24284 duration=31(sec)
Jul 5 13:49:21 saturn xinetd[2586]: START: smtp pid=24341 from=89.33.228.140
Jul 5 13:49:22 saturn xinetd[2586]: EXIT: smtp status=1 pid=24333 duration=4(sec)
Jul 5 13:49:23 saturn xinetd[2586]: START: smtp pid=24345 from=95.134.47.153
Jul 5 13:49:23 saturn xinetd[2586]: START: smtp pid=24347 from=61.100.219.50
Jul 5 13:49:23 saturn xinetd[2586]: EXIT: smtp status=0 pid=24345 duration=0(sec)
Jul 5 13:49:24 saturn xinetd[2586]: EXIT: smtp status=0 pid=24347 duration=1(sec)
Jul 5 13:49:26 saturn xinetd[2586]: START: smtp pid=24348 from=80.78.23.188
Jul 5 13:49:27 saturn xinetd[2586]: EXIT: smtp status=0 pid=24341 duration=6(sec)
Jul 5 13:49:27 saturn xinetd[2586]: START: smtp pid=24349 from=89.33.228.140
Jul 5 13:49:27 saturn xinetd[2586]: START: smtp pid=24350 from=119.155.117.247
Jul 5 13:49:27 saturn xinetd[2586]: EXIT: smtp status=1 pid=24263 duration=42(sec)
Jul 5 13:49:27 saturn xinetd[2586]: START: smtp pid=24351 from=77.29.53.73
Jul 5 13:49:27 saturn xinetd[2586]: EXIT: smtp status=0 pid=24348 duration=1(sec)
Jul 5 13:49:27 saturn xinetd[2586]: START: smtp pid=24352 from=61.100.219.50
Jul 5 13:49:27 saturn xinetd[2586]: START: smtp pid=24353 from=109.96.230.22
Jul 5 13:49:27 saturn xinetd[2586]: EXIT: smtp status=0 pid=24349 duration=0(sec)
Jul 5 13:49:27 saturn xinetd[2586]: EXIT: smtp status=0 pid=24351 duration=0(sec)
Jul 5 13:49:27 saturn xinetd[2586]: START: smtp pid=24354 from=89.33.228.140
Jul 5 13:49:28 saturn xinetd[2586]: EXIT: smtp status=0 pid=24350 duration=1(sec)
Jul 5 13:49:28 saturn xinetd[2586]: EXIT: smtp status=0 pid=24354 duration=1(sec)
Jul 5 13:49:28 saturn xinetd[2586]: EXIT: smtp status=0 pid=24352 duration=1(sec)
Jul 5 13:49:28 saturn xinetd[2586]: START: smtp pid=24355 from=61.100.219.50
Jul 5 13:49:29 saturn xinetd[2586]: EXIT: smtp status=0 pid=24355 duration=1(sec)
Jul 5 13:49:29 saturn xinetd[2586]: START: smtp pid=24356 from=59.95.109.56
Jul 5 13:49:29 saturn xinetd[2586]: EXIT: smtp signal=13 pid=24356 duration=0(sec)
Jul 5 13:49:32 saturn xinetd[2586]: START: smtp pid=24358 from=187.2.44.10
Jul 5 13:49:32 saturn xinetd[2586]: START: smtp pid=24360 from=61.100.219.50
Jul 5 13:49:32 saturn xinetd[2586]: EXIT: smtp status=0 pid=24358 duration=0(sec)


What can be done to stop this?!

 

[breun]

All I see is a bunch of hosts connecting to your SMTP server. That's pretty normal when running an SMTP server. I don't see a problem really.