ancient backup entries in dhcpd.leases and duplicate messages in syslog

[Randall C Grimshaw]

The question is whether this has been seen and fixed in 3.10 

There are multiple sources of 'duplicate on' messages that we would like
to identify. This observed source has little impact other than noise
that hinders our tracking of other issues.

The example below shows a system that was once given a dynamic address
192.168.25.85 but has since been given a static address of 192.168.25.25

The original address remains forever in the peer dhcpd.leases file as a
backup and the server continually complains of a duplicate.

I would expect the server to age these out also. The current server pair
is Internet Systems Consortium DHCP Server V3.0.6

 

Dhcpd.leases:

lease 192.168.25.85 {

  starts 6 2007/08/25 19:43:24;

  ends 3 2007/08/08 17:54:15;

  tstp 3 2007/08/08 17:54:15;

  tsfp 6 2007/08/25 19:43:24;

  atsfp 6 2007/08/25 19:43:24;

  cltt 3 2007/08/08 17:53:48;

  binding state backup;

  hardware ethernet 00:11:22:33:44:55;

  uid "\001\000\013l/\215\346";

}

 

Syslog:

Feb  4 08:29:04 server2/server2 dhcpd: [ID 702911 local3.info] DHCPACK
on 192.168.25.25 to 00:11:22:33:44:55 via 192.168.25.5

Feb  4 08:30:50 server2/server2 dhcpd: [ID 702911 local3.error] uid
lease 192.168.25.95 for client 00:11:22:33:44:55 is duplicate on
net-025-000

 

Thank you.

Randy Grimshaw

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20080204/8249b8d2/attachment.html>