Bug 103284 - dhcpd not updating dhcpd.leases
Summary: dhcpd not updating dhcpd.leases
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: dhcp   
(Show other bugs)
Version: 9
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jason Vas Dias
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2003-08-28 15:21 UTC by Bastien Nocera
Modified: 2007-04-18 16:57 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-08-24 22:46:54 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2004:566 normal SHIPPED_LIVE Updated dhcp and dhclient packages 2005-05-26 04:00:00 UTC

Description Bastien Nocera 2003-08-28 15:21:07 UTC
dhcpd is not updating dhcpd.leases when giving away IP addresses.
The versions tested are:
3.0pl1-23 (stock RHL9)
3.0pl2-6.13 (lastest rawhide)

An lsof | grep dhcp should /var/lib/dhcp/dhcpd.leases being opened
IP addresses being assigned are showing in /var/log/messages

Comment 1 Jason Vas Dias 2004-08-24 22:46:54 UTC
dhcpd no longer records static leases in its database -
ie. leases of a 'fixed-address' :
 subnet xxx.xxx.xxx.xxx netmask mmm.mmm.mmm.mmm {
      host n {     
                 hardware ethernet XX:XX:XX:XX:XX;
                 fixed-address nnn.nnn.nnn.nnn;
This is a STATIC LEASE and will NOT be recorded in
the dhcpd.leases database.

Only DYNAMIC LEASES, such as
subnet xxx.xxx.xxx.xxx netmask mmm.mmm.mmm.mmm {
       range xxx.xxx.xxx.xxx yyy.yyy.yyy.yyy;
are recorded in the database - this works OK with

Comment 2 John Flanagan 2004-12-21 19:42:19 UTC
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 the 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.


Note You need to log in before you can comment on or make changes to this bug.