Dhcp3-server causes high hdd usage

[Ricardo Duarte]

After a while, my HDD starts having a large usage (noise and the led constantly
blinking), and dhcp3 stop working.
If I kill dhcp3-server, the disk immediatly starts to work fine.
The cpu usage from dhcp3 is normal thought.

The buggy dhcp3-server I'm using is the one in breezy, and the version is
3.0.2-1ubuntu6.
On the same machine, hoary works fine.

[Andrew Pollock (apollock)]

Hello,

I've had a Debian user report this problem with 3.0.2.

This sounds like the bug that was apparently fixed in 3.0 RC8.

I can't see any further mentions of it being re-fixed in any subsequent
versions. I'm planning on packaging up 3.0.3 shortly, so if this fixes the
problem I can close this bug with that upload.

If you maintain the Cc line of this email, any followup correspondence will
be captured by our bug tracking system.

regards

Andrew

On Wed, Aug 24, 2005 at 10:57:36AM -0600, Valerio Aimale wrote:
> Package: dhcp3-server
> Version: 3.0.2-3
> Severity: grave
> Justification: renders package unusable
>
>
> Hello,
>
> since when I upgraded to the most recent version of the package, I've noticed
> that if one-lease-per-client is set to on and a client releases the old IP
> and re-request new one (after a reboot for example), the dhcp server goes
> into an inifite loop and writes the same information to the
> dhcpd.leases file until it fills up the disk
>
> dhcpd.leases file:
>
> ===
> lease 192.168.2.210 {
> starts 3 2005/08/24 16:19:15;
> ends 3 2005/08/24 16:44:14;
> tstp 3 2005/08/31 16:19:15;
> binding state free;
> hardware ethernet 00:e0:81:2e:9e:7a;
> client-hostname "node1";
> }
> lease 192.168.2.210 {
> starts 3 2005/08/24 16:19:15;
> ends 3 2005/08/24 16:44:14;
> tstp 3 2005/08/31 16:19:15;
> binding state free;
> hardware ethernet 00:e0:81:2e:9e:7a;
> client-hostname "node1";
> }
> lease 192.168.2.210 {
> starts 3 2005/08/24 16:19:15;
> ends 3 2005/08/24 16:44:14;
> tstp 3 2005/08/31 16:19:15;
> binding state free;
> hardware ethernet 00:e0:81:2e:9e:7a;
> client-hostname "node1";
> }
> lease 192.168.2.210 {
> starts 3 2005/08/24 16:19:15;
> ends 3 2005/08/24 16:44:14;
> tstp 3 2005/08/31 16:19:15;
> binding state free;
> hardware ethernet 00:e0:81:2e:9e:7a;
> client-hostname "node1";
> }
> [...]
> =====
>
> This renders the server unusable where one-lease-per-client is needed
>
> my config
>
> ===============
> # option definitions common to all supported networks...
> option domain-name "cluster";
> option domain-name-servers 192.168.2.1, 192.168.1.2, 206.83.0.42;
>
> default-lease-time 604800;
> max-lease-time 604800;
>
> authoritative;
> log-facility local7;
>
> do-forward-updates on;
> ignore client-updates;
> ddns-updates on;
> ddns-update-style interim;
>
> subnet 192.168.2.0 netmask 255.255.255.0 {
> range 192.168.2.10 192.168.2.253;
> option routers 192.168.2.1;
> option domain-name "cluster";
> option broadcast-address 192.168.2.255;
> option domain-name-servers 192.168.2.1, 192.168.1.2, 206.83.0.42;
> option netbios-name-servers 192.168.1.2;
> option ntp-servers 192.168.2.1;
> ddns-update-style interim;
> update-static-leases true;
> one-lease-per-client on;
> }
> =================
>
>
> I think the same bug was present in one of the 3.0 release candidates,
> it might be the same surfacing again.
>
> Same behavior is present on i386 architectures.
>
>
> Thanks
>
> Valerio Aimale
>
>
> -- System Information:
> Debian Release: testing/unstable
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: amd64...

[Andrew Pollock (apollock)]

On Wed, Aug 24, 2005 at 07:26:34PM -0600, Valerio Aimale wrote:
>
> andrew,
>
> thank you for your reply, I will check 3.0.2 out and will report you my
> findings.
>

There is a preliminary package of dhcp3-3.0.3 available at
http://people.debian.org/~apollock/dhcp3

Please test it (or build it on amd64 and test it) and copy the bug with your
findings.

regards

Andrew

[David W. Hankins (david-hankins)]

On Thu, Aug 25, 2005 at 09:25:25AM +1000, Andrew Pollock wrote:
> I've had a Debian user report this problem with 3.0.2.
>
> This sounds like the bug that was apparently fixed in 3.0 RC8.

This predates me.

But you do realize that 3.0.2 is later than 3.0rc8?

"3.0" would actually be better described as "3.0.0".

> I can't see any further mentions of it being re-fixed in any subsequent
> versions. I'm planning on packaging up 3.0.3 shortly, so if this fixes the
> problem I can close this bug with that upload.

I have no memory of this problem being reported.

I suspect if this is happening in 3.0.2, that it will still happen in
3.0.3.

--
David W. Hankins "If you don't do it right the first time,
Software Engineer you'll just have to do it again."
Internet Systems Consortium, Inc. -- Jack T. Hankins

[Valerio Aimale (vga)]

Andrew,

I've tested the preliminary 3.0.3-0 and it works fine with
one-lease-per-client set to on. Leases are obtained correctly and no
more infinite loops.

Thank you for your help

Valerio

> On Wed, Aug 24, 2005 at 07:26:34PM -0600, Valerio Aimale wrote:
> >
> > andrew,
> >
> > thank you for your reply, I will check 3.0.2 out and will report you my
> > findings.
> >
>
> There is a preliminary package of dhcp3-3.0.3 available at
> http://people.debian.org/~apollock/dhcp3
>
> Please test it (or build it on amd64 and test it) and copy the bug with your
> findings.
>
> regards
>
> Andrew

[Andrew Pollock (apollock)]

On Thu, Aug 25, 2005 at 09:31:49AM -0600, Valerio Aimale wrote:
>
> Andrew,
>
> I've tested the preliminary 3.0.3-0 and it works fine with
> one-lease-per-client set to on. Leases are obtained correctly and no
> more infinite loops.
>
> Thank you for your help
>

Great. I'll look at making a few cosmetic changes to the maintainer scripts
and another build, give the server a spot of testing, and make an upload of
3.0.3 today that closes this bug.

regards

Andrew

[Andrew Pollock (apollock)]

# Automatically generated email from bts, devscripts version 2.8.14
tags 324886 + pending

[Andrew Pollock (apollock)]

Source: dhcp3
Source-Version: 3.0.3-1

We believe that the bug you reported is fixed in the latest version of
dhcp3, which is due to be installed in the Debian FTP archive:

dhcp3-client-udeb_3.0.3-1_i386.udeb
  to pool/main/d/dhcp3/dhcp3-client-udeb_3.0.3-1_i386.udeb
dhcp3-client_3.0.3-1_i386.deb
  to pool/main/d/dhcp3/dhcp3-client_3.0.3-1_i386.deb
dhcp3-common_3.0.3-1_i386.deb
  to pool/main/d/dhcp3/dhcp3-common_3.0.3-1_i386.deb
dhcp3-dev_3.0.3-1_i386.deb
  to pool/main/d/dhcp3/dhcp3-dev_3.0.3-1_i386.deb
dhcp3-relay_3.0.3-1_i386.deb
  to pool/main/d/dhcp3/dhcp3-relay_3.0.3-1_i386.deb
dhcp3-server_3.0.3-1_i386.deb
  to pool/main/d/dhcp3/dhcp3-server_3.0.3-1_i386.deb
dhcp3_3.0.3-1.diff.gz
  to pool/main/d/dhcp3/dhcp3_3.0.3-1.diff.gz
dhcp3_3.0.3-1.dsc
  to pool/main/d/dhcp3/dhcp3_3.0.3-1.dsc
dhcp3_3.0.3.orig.tar.gz
  to pool/main/d/dhcp3/dhcp3_3.0.3.orig.tar.gz

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andrew Pollock <email address hidden> (supplier of updated dhcp3 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu, 25 Aug 2005 13:47:41 +1000
Source: dhcp3
Binary: dhcp3-client-udeb dhcp3-common dhcp3-relay dhcp3-dev dhcp3-client dhcp3-server
Architecture: source i386
Version: 3.0.3-1
Distribution: unstable
Urgency: low
Maintainer: Eloy A. Paris <email address hidden>
Changed-By: Andrew Pollock <email address hidden>
Description:
 dhcp3-client - DHCP Client
 dhcp3-client-udeb - DHCP Client for debian-installer (udeb)
 dhcp3-common - Common files used by all the dhcp3* packages
 dhcp3-dev - API for accessing and modifying the DHCP server and client state
 dhcp3-relay - DHCP Relay
 dhcp3-server - DHCP server for automatic IP address assignment
Closes: 320683 321028 321734 324886
Changes:
 dhcp3 (3.0.3-1) unstable; urgency=low
 .
   * New upstream release (closes: #324886)
   * Added NEWS.Debian regarding change in functionality with respect to
     next-server now being required for booting.
 .
 dhcp3 (3.0.2-4) unstable; urgency=low
 .
   * Added patch from Aurelien Jarno to support GNU/kFreeBSD (closes: #321028)
   * debian/dhcp3-server.preinst: fixed bashism
   * debian/dhcp3-relay.prerm: fixed bashisms
   * debian/dhcp3-client.preinst: fixed bashisms
   * Updated Czech debconf templates translation (closes: #321734)
   * debian/dhcp3-server.init.d: Applied patch from Stephen Gildea to provide
     status option (closes: #320683)
Files:
 8ee01fc27b5e4a29879bf92ddd507152 749 net extra dhcp3_3.0.3-1.dsc
 f91416a0b8ed3fd0601688cf0b7df58f 870240 net extra dhcp3_3.0.3.orig.tar.gz
 513857f52ef12b4a1479ed402ba140cc 52930 net extra dhcp3_3.0.3-1.diff.gz
 1d043dbe04148f47c9b28fe269734fbe 527068 net extra dhcp3-server_3.0.3-1_i386.deb
 9b106c9dc90a45c925393fec31bdf16...

[Ricardo Duarte (rjtd21)]

After a while, my HDD starts having a large usage (noise and the led constantly
blinking), and dhcp3 stop working.
If I kill dhcp3-server, the disk immediatly starts to work fine.
The cpu usage from dhcp3 is normal thought.

The buggy dhcp3-server I'm using is the one in breezy, and the version is
3.0.2-1ubuntu6.
On the same machine, hoary works fine.

[Matt Zimmerman (mdz)]

Run strace on the dhcp3-server process and see what it is doing.

[Emonib (emonib)]

I have the same problem with my config.
The problem is easily reproductible :
- start dhcp3-server on host "master"
- connect to "master" with the client "slave" (using dhcp)
- there is no problem, the ip is assigned correctly
- use the command "dhcp3 eth0" on the client (even if the client have already an ip)
- the client receive no response
- the server start an loop and write an infinite number of leases in the file
/var/log/dhcpd/dhcpd.leases (responsible of the hdd heavy load)

[Emonib (emonib)]

Created an attachment (id=4935)
strace -f -ff -F -i -r -tt -a 40 -p "PID_OF_DHCP3-SERVER"

The trace that appears when dhcp3-server start infinite loop.

[Emonib (emonib)]

(In reply to comment #2)
> I have the same problem with my config.
> The problem is easily reproductible :
> - start dhcp3-server on host "master"
> - connect to "master" with the client "slave" (using dhcp)
> - there is no problem, the ip is assigned correctly
> - use the command "dhcp3 eth0" on the client (even if the client have already
an ip)
> - the client receive no response
> - the server start an loop and write an infinite number of leases in the file
> /var/log/dhcpd/dhcpd.leases (responsible of the hdd heavy load)

The problem disappears when "one-lease-per-client" is disable...

[Emonib (emonib)]

(In reply to comment #4)
> (In reply to comment #2)
> > I have the same problem with my config.
> > The problem is easily reproductible :
> > - start dhcp3-server on host "master"
> > - connect to "master" with the client "slave" (using dhcp)
> > - there is no problem, the ip is assigned correctly
> > - use the command "dhcp3 eth0" on the client (even if the client have already
> an ip)
> > - the client receive no response
> > - the server start an loop and write an infinite number of leases in the file
> > /var/log/dhcpd/dhcpd.leases (responsible of the hdd heavy load)
>
> The problem disappears when "one-lease-per-client" is disable...

See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=324886
Please change the bug severity to major...

[Matt Zimmerman (mdz)]

Fixed in 3.0.3-1+:

     dhcp3 | 3.0.3-6ubuntu6 | http://us.archive.ubuntu.com dapper/main Sources