Red Hat Bugzilla – Bug 445457
dhcp reclaims abandoned leases when free leases are available
Last modified: 2009-05-18 16:06:27 EDT
Description of problem:
A DHCP client (usually a Windows client) cannot be assigned an IP
address. The following messages appear in the syslog:
dhcpd: Reclaiming abandoned IP address 10.196.143.58.
dhcpd: DHCPDISCOVER from 00:16:d4:2f:a5:b0 via eth0
dhcpd: DHCPOFFER on 10.196.143.58 to 00:16:d4:2f:a5:b0 (Notebook1)
dhcpd: DHCPREQUEST for 10.196.143.58 (10.196.143.205) from
00:16:d4:2f:a5:b0 (Notebook1) via eth0
dhcpd: DHCPACK on 10.196.143.58 to 00:16:d4:2f:a5:b0 (Notebook1)
dhcpd: Abandoning IP address 10.196.143.58: declined.
dhcpd: DHCPDECLINE of 10.196.143.58 from 00:16:d4:2f:a5:b0
(Notebook1) via eth0: not found
It appears that dhcp is trying to re-use an abandoned IP address.
According to the DHCP 3.0.6 Release Notes, this appears to be
fixed in dhcp-3.0.2:
Changes since 3.0.2rc1
* allocate_lease() was rewritten to repair a bug in which the
server would try to allocate an ABANDONED lease when FREE
leases were available.
Version-Release number of selected component (if applicable):
Not reproducible, but happens often. Current workaround is to
delete the leases file and restart dhcpd service. Seems to happen
more quickly with Windows clients.
Steps to Reproduce:
1. Let dhcp server run for a while with Windows DHCP clients.
Eventually a client will end up in a state where it can't get an
dhcp server assigns addresses without the need to restart the service.
Possible patch attached. Patch was generated by running a diff
between dhcp-3.0.2rc2 and dhcp-3.0.2rc1. The patch applies cleanly
to RHEL 4.6 (dhcp-3.0.1-59.EL4), but test results aren't available
Created attachment 304691 [details]
Patch available, which pulls in the changes for allocate_leases() post 3.0.1. Seems reasonable enough to fix (and easy enough).
Sounds good, Ben. Thanks.
Patch applied. Fix will be in dhcp-3.0.1-63.EL4.
are you able to test this issue with the latest rel-eng or nightly builds ?
(In reply to comment #9)
> are you able to test this issue with the latest rel-eng or nightly builds ?
Unfortunately, I was never able to reproduce the problem (didn't have the right equipment). I've asked the customer who originally reported the problem to provide feedback on some test packages that I gave them. I'll forward whatever information I receive.
do you have any feedback from the customer? RTT can't test this. We don't have Windows machines to act as DHCP clients.
For the record:
Proposed patch is included in the srpm as dhcp-3.0.2-fix-allocate-lease.patch without any modifications and is being applied to the sources in the .spec file.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.