[K12OSN] DHCP gone wild
Jack
jackpal at cfl.rr.com
Fri Apr 2 23:27:20 UTC 2004
Lately my test system has been crashing mysteriously. /var/log/messages
contains the following:
Apr 2 06:35:20 tserver ntpd[3399]: kernel time discipline status change
41
Apr 2 06:37:30 tserver ntpd[3399]: kernel time discipline status change
1
Apr 2 06:38:24 ws243 -- MARK --
Apr 2 07:07:53 ws248 -- MARK --
Apr 2 07:29:21 ws252 -- MARK --
Apr 2 07:38:23 ws243 -- MARK --
Apr 2 08:07:53 ws248 -- MARK --
Apr 2 08:29:21 ws252 -- MARK --
Apr 2 08:38:23 ws243 -- MARK --
Apr 2 09:07:53 ws248 -- MARK --
Apr 2 09:28:18 tserver ntpd[3399]: synchronisation lost
Apr 2 09:29:21 ws252 -- MARK --
Apr 2 09:32:10 tserver dhcpd: Wrote 0 deleted host decls to leases
file.
Apr 2 09:32:10 tserver dhcpd: Wrote 0 new dynamic host decls to leases
file.
Apr 2 09:32:10 tserver dhcpd: Wrote 12 leases to leases file.
Apr 2 09:32:10 tserver dhcpd: DHCPREQUEST for 192.168.0.251 from
00:a0:c9:75:ca:27 via eth0
Apr 2 09:32:10 tserver dhcpd: DHCPACK on 192.168.0.251 to
00:a0:c9:75:ca:27 via eth0
Apr 2 09:32:10 tserver dhcpd: DHCPREQUEST for 192.168.0.242 from
00:06:29:a2:a7:7d via eth0
Apr 2 09:32:10 tserver dhcpd: DHCPACK on 192.168.0.242 to
00:06:29:a2:a7:7d via eth0
Apr 2 09:32:11 tserver dhcpd: DHCPREQUEST for 192.168.0.251 from
00:a0:c9:75:ca:27 via eth0
Apr 2 09:32:11 tserver dhcpd: DHCPACK on 192.168.0.251 to
00:a0:c9:75:ca:27 via eth0
Apr 2 09:32:14 tserver dhcpd: DHCPREQUEST for 192.168.0.251 from
00:a0:c9:75:ca:27 via eth0
Apr 2 09:32:14 tserver dhcpd: DHCPACK on 192.168.0.251 to
00:a0:c9:75:ca:27 via eth0
Apr 2 09:32:15 tserver dhcpd: DHCPREQUEST for 192.168.0.251 from
00:a0:c9:75:ca:27 via eth0
Apr 2 09:32:15 tserver dhcpd: DHCPACK on 192.168.0.251 to
00:a0:c9:75:ca:27 via eth0
Apr 2 09:32:15 tserver dhcpd: DHCPREQUEST for 192.168.0.242 from
00:06:29:a2:a7:7d via eth0
Apr 2 09:32:15 tserver dhcpd: DHCPACK on 192.168.0.242 to
00:06:29:a2:a7:7d via eth0
Apr 2 09:32:15 tserver dhcpd: DHCPREQUEST for 192.168.0.242 from
00:06:29:a2:a7:7d via eth0
Apr 2 09:32:15 tserver dhcpd: DHCPACK on 192.168.0.242 to
00:06:29:a2:a7:7d via eth0
Apr 2 09:32:18 tserver dhcpd: DHCPREQUEST for 192.168.0.251 from
00:a0:c9:75:ca:27 via eth0
Apr 2 09:32:18 tserver dhcpd: DHCPACK on 192.168.0.251 to
00:a0:c9:75:ca:27 via eth0
Apr 2 09:32:19 tserver dhcpd: DHCPREQUEST for 192.168.0.242 from
00:06:29:a2:a7:7d via eth0
Apr 2 09:32:19 tserver dhcpd: DHCPACK on 192.168.0.242 to
00:06:29:a2:a7:7d via eth0
Apr 2 09:32:21 tserver dhcpd: DHCPREQUEST for 192.168.0.251 from
00:a0:c9:75:ca:27 via eth0
Apr 2 09:32:21 tserver dhcpd: DHCPACK on 192.168.0.251 to
00:a0:c9:75:ca:27 via eth0
Apr 2 09:32:21 tserver dhcpd: DHCPREQUEST for 192.168.0.242 from
00:06:29:a2:a7:7d via eth0
Apr 2 09:32:21 tserver dhcpd: DHCPACK on 192.168.0.242 to
00:06:29:a2:a7:7d via eth0
Apr 2 09:32:26 tserver dhcpd: DHCPREQUEST for 192.168.0.251 from
00:a0:c9:75:ca:27 via eth0
Apr 2 09:32:26 tserver dhcpd: DHCPACK on 192.168.0.251 to
00:a0:c9:75:ca:27 via eth0
Apr 2 09:32:27 tserver dhcpd: DHCPREQUEST for 192.168.0.251 from
00:a0:c9:75:ca:27 via eth0
Apr 2 09:32:27 tserver dhcpd: DHCPACK on 192.168.0.251 to
00:a0:c9:75:ca:27 via eth0
Apr 2 09:32:27 tserver dhcpd: DHCPREQUEST for 192.168.0.242 from
00:06:29:a2:a7:7d via eth0
Apr 2 09:32:27 tserver dhcpd: DHCPACK on 192.168.0.242 to
00:06:29:a2:a7:7d via eth0
Apr 2 09:32:29 tserver dhcpd: DHCPREQUEST for 192.168.0.242 from
00:06:29:a2:a7:7d via eth0
Apr 2 09:32:29 tserver dhcpd: DHCPACK on 192.168.0.242 to
00:06:29:a2:a7:7d via eth0
Apr 2 09:32:36 tserver dhcpd: DHCPREQUEST for 192.168.0.251 from
00:a0:c9:75:ca:27 via eth0
Apr 2 09:32:36 tserver dhcpd: DHCPACK on 192.168.0.251 to
00:a0:c9:75:ca:27 via eth0
Apr 2 09:32:39 tserver dhcpd: DHCPREQUEST for 192.168.0.242 from
00:06:29:a2:a7:7d via eth0
Apr 2 09:32:39 tserver dhcpd: DHCPACK on 192.168.0.242 to
00:06:29:a2:a7:7d via eth0
Apr 2 09:32:44 tserver dhcpd: DHCPREQUEST for 192.168.0.251 from
00:a0:c9:75:ca:27 via eth0
-snip This goes on until the server crashes..
Apr 2 12:14:37 tserver dhcpd: DHCPACK on 192.168.0.242 to
00:06:29:a2:a7:7d via eth0
Apr 2 12:14:51 tserver dhcpd: DHCPREQUEST for 192.168.0.242 from
00:06:29:a2:a7:7d via eth0
Apr 2 12:14:51 tserver dhcpd: DHCPACK on 192.168.0.242 to
00:06:29:a2:a7:7d via eth0
Apr 2 12:15:22 tserver dhcpd: DHCPREQUEST for 192.168.0.242 from
00:06:29:a2:a7:7d via eth0
Apr 2 12:15:22 tserver dhcpd: DHCPACK on 192.168.0.242 to
00:06:29:a2:a7:7d via eth0
Apr 2 12:15:52 tserver dhcpd: DHCPREQUEST for 192.168.0.242 from
00:06:29:a2:a7:7d via eth0
Apr 2 12:15:52 tserver dhcpd: DHCPACK on 192.168.0.242 to
00:06:29:a2:a7:7d via eth0
Apr 2 12:16:16 tserver dhcpd: DHCPREQUEST for 192.168.0.242 from
00:06:29:a2:a7:7d via eth0
Apr 2 12:16:16 tserver dhcpd: DHCPACK on 192.168.0.242 to
00:06:29:a2:a7:7d via eth0
Apr 2 12:17:02 tserver dhcpd: DHCPREQUEST for 192.168.0.242 from
00:06:29:a2:a7:7d via eth0
Apr 2 12:17:02 tserver dhcpd: DHCPACK on 192.168.0.242 to
00:06:29:a2:a7:7d via eth0
Apr 2 12:17:13 tserver dhcpd: DHCPREQUEST for 192.168.0.242 from
00:06:29:a2:a7:7d via eth0
Apr 2 12:17:13 tserver dhcpd: DHCPACK on 192.168.0.242 to
00:06:29:a2:a7:7d via eth0
Apr 2 12:17:31 tserver dhcpd: DHCPREQUEST for 192.168.0.242 from
00:06:29:a2:a7:7d via eth0
Apr 2 12:17:31 tserver dhcpd: DHCPACK on 192.168.0.242 to
00:06:29:a2:a7:7d via eth0
Apr 2 12:17:42 tserver dhcpd: DHCPREQUEST for 192.168.0.242 from
00:06:29:a2:a7:7d via eth0
Apr 2 12:17:42 tserver dhcpd: DHCPACK on 192.168.0.242 to
00:06:29:a2:a7:7d via eth0
Apr 2 12:18:01 tserver dhcpd: DHCPREQUEST for 192.168.0.242 from
00:06:29:a2:a7:7d via eth0
Apr 2 12:18:01 tserver dhcpd: DHCPACK on 192.168.0.242 to
00:06:29:a2:a7:7d via eth0
Apr 2 12:18:51 tserver dhcpd: DHCPREQUEST for 192.168.0.242 from
00:06:29:a2:a7:7d via eth0
Apr 2 12:18:51 tserver dhcpd: DHCPACK on 192.168.0.242 to
00:06:29:a2:a7:7d via eth0
Apr 2 12:19:44 tserver dhcpd: DHCPREQUEST for 192.168.0.242 from
00:06:29:a2:a7:7d via eth0
Apr 2 12:19:44 tserver dhcpd: DHCPACK on 192.168.0.242 to
00:06:29:a2:a7:7d via eth0
Apr 2 18:00:02 tserver syslogd 1.4.1: restart (remote reception).
Apr 2 18:00:02 tserver syslog: syslogd startup succeeded
Apr 2 18:00:02 tserver kernel: klogd 1.4.1, log source = /proc/kmsg
started.
I'm planning on just reinstalling but I'm looking for ideas. Anyone?
Jack
More information about the K12OSN
mailing list