Thousands of times the same line repeated in /var/log/messages. What can it be?

English Network/Internet
1

I’ve detected this in /var/log/messages. It’s repeated more than 1000 times per second. Maybe is a crazy client or is the server who has gone insane?


2014-10-03T21:28:00.310729+02:00 tutatis dhcpd: DHCPDISCOVER from 14:da:e9:38:60:9e (PC) via eth0
2014-10-03T21:28:00.311610+02:00 tutatis dhcpd: DHCPOFFER on 192.168.2.187 to 14:da:e9:38:60:9e (PC) via eth0
2014-10-03T21:28:00.312193+02:00 tutatis dhcpd: DHCPDISCOVER from 14:da:e9:38:60:9e (PC) via eth0
2014-10-03T21:28:00.312751+02:00 tutatis dhcpd: DHCPOFFER on 192.168.2.187 to 14:da:e9:38:60:9e (PC) via eth0
2014-10-03T21:28:00.313311+02:00 tutatis dhcpd: DHCPDISCOVER from 14:da:e9:38:60:9e (PC) via eth0
2014-10-03T21:28:00.313864+02:00 tutatis dhcpd: DHCPOFFER on 192.168.2.187 to 14:da:e9:38:60:9e (PC) via eth0
2014-10-03T21:28:00.315764+02:00 tutatis dhcpd: DHCPDISCOVER from 14:da:e9:38:60:9e (PC) via eth0
2014-10-03T21:28:00.316663+02:00 tutatis dhcpd: DHCPOFFER on 192.168.2.187 to 14:da:e9:38:60:9e (PC) via eth0
2014-10-03T21:28:00.326225+02:00 tutatis dhcpd: DHCPDISCOVER from 14:da:e9:38:60:9e (PC) via eth0
2014-10-03T21:28:00.327018+02:00 tutatis dhcpd: DHCPOFFER on 192.168.2.187 to 14:da:e9:38:60:9e (PC) via eth0
2

Hi
Looks like your missing the DHCPREQUEST from the client, ip address in use by another machine, firewall not letting the request out? Another dhcp server running?

3

On 2014-10-03 22:56, fperal wrote:
>
> I’ve detected this in /var/log/messages. It’s repeated more than 1000
> times per second. Maybe is a crazy client or is the server who has gone
> insane?
>
>
> Code:
> --------------------
>
> 2014-10-03T21:28:00.310729+02:00 tutatis dhcpd: DHCPDISCOVER from 14:da:e9:38:60:9e (PC) via eth0
> 2014-10-03T21:28:00.311610+02:00 tutatis dhcpd: DHCPOFFER on 192.168.2.187 to 14:da:e9:38:60:9e (PC) via eth0
> 2014-10-03T21:28:00.312193+02:00 tutatis dhcpd: DHCPDISCOVER from 14:da:e9:38:60:9e (PC) via eth0
> 2014-10-03T21:28:00.312751+02:00 tutatis dhcpd: DHCPOFFER on 192.168.2.187 to 14:da:e9:38:60:9e (PC) via eth0
> 2014-10-03T21:28:00.313311+02:00 tutatis dhcpd: DHCPDISCOVER from 14:da:e9:38:60:9e (PC) via eth0
> 2014-10-03T21:28:00.313864+02:00 tutatis dhcpd: DHCPOFFER on 192.168.2.187 to 14:da:e9:38:60:9e (PC) via eth0
> 2014-10-03T21:28:00.315764+02:00 tutatis dhcpd: DHCPDISCOVER from 14:da:e9:38:60:9e (PC) via eth0
> 2014-10-03T21:28:00.316663+02:00 tutatis dhcpd: DHCPOFFER on 192.168.2.187 to 14:da:e9:38:60:9e (PC) via eth0
> 2014-10-03T21:28:00.326225+02:00 tutatis dhcpd: DHCPDISCOVER from 14:da:e9:38:60:9e (PC) via eth0
> 2014-10-03T21:28:00.327018+02:00 tutatis dhcpd: DHCPOFFER on 192.168.2.187 to 14:da:e9:38:60:9e (PC) via eth0
>
> --------------------

Some client machine tries to get an IP from your DHCP server. It gets an
answer, to use “192.168.2.187”. Either it does not get the answer or
does not see it, because it ask again.

repeat for ever.

Try power cycle that client. Or restart its network.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

4

It seems it was a loop in a switch!!!