#559415 dhcp3-server: occasional segfault soon after startup when configured for failover

#559415#5
Date:
2009-12-04 07:35:10 UTC
From:
To:
Occasionally, immediately after one of the failover peers starts up the
server will segfault. One thing I have noticed is that each time this
happens, the DHCP logs show something like the following:

Dec  3 20:39:04 server dhcpd: Wrote 11875 leases to leases file.
Dec  3 20:39:04 server dhcpd: failover peer mypeer: I move from communications-interrupted to startup
Dec  3 20:39:04 server dhcpd: DHCPREQUEST for 192.168.2.5 from xx:xx:xx:xx:xx:xx (hostname) via eth0: not responding (startup)
*** segfault happens here ***

Sometimes the state change is from 'normal' to 'startup', but the
pattern is always (or seems to be always):

- server starts up (finishes writing leases to file)
- transitions to 'startup' state
- DHCPREQUEST happens but is dropped due to being in the 'startup' state
- segfault happens almost immediately after

I started out with a stock Debian Lenny installation, running
dhcp3-server 3.1.1 when I first noticed this problem, so then I
installed the dhcp3-server package from testing (which I am reporting
this bug against) and the same problem occurred (segfault with the same
characteristics) but the only thing I noticed that was different was the
segfault log message:

- lenny (3.1.1) -
[2452859.456068] dhcpd3[13793]: segfault at 48 ip 4610d4 sp 7fffa2f51380 error 4 in dhcpd3[400000+89000]

- lenny with testing dhcp3-server package (3.1.3-1) -
[2688893.331140] dhcpd3[2544]: segfault at 841f17 ip 45c2a3 sp 7fff3d432068 error 6 in dhcpd3[400000+88000]

The servers' clocks are synced via the same NTP server, and there was no
noticeable time difference between the two, which I am led to understand
could cause crashes on (at least some) versions of dhcp3-server, so I
think that can be ruled out in my case.

Let me know if I can provide any more information.

The system is (currently) running lenny with only the dhcp3-server
packages from testing, but as I stated above, the issue occurred with
the stock lenny packages as well.

Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)

#559415#10
Date:
2010-06-24 09:06:05 UTC
From:
To:
after enabling failover there was also a segfault
on the system where dhcpd3 was installed without
failover before:

Jun 18 04:14:59 server dhcpd: timeout waiting for failover peer
dhcp-failover
Jun 18 04:14:59 server dhcpd: peer dhcp-failover: disconnected
Jun 18 04:14:59 server dhcpd: failover peer dhcp-failover: I move from
normal to communications-interrupted
Jun 18 04:15:04 server kernel: [523219.481139] dhcpd3[369]: segfault
at 48 ip 4610d4 sp 7fffffffccf0 error 4 in dhcpd3[400000+89000]

nearly same configuration:

Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-2-amd64 (smp w 4 Cores)

I did not try testing. dhcp3-server had no segfault running
standalone before on the same server for about 4 months. Switch to
failover was an Jun 12, first segfault on Jun 18 with above
logfile.

Let me know if I can give you more information.

#559415#15
Date:
2010-06-24 14:12:01 UTC
From:
To:
Same version of dhcpd for both partners in the failover pair?
#559415#20
Date:
2010-06-24 14:29:12 UTC
From:
To:
Am 24.06.2010 16:12, schrieb Andrew Pollock:

both up2date debian 5.0.4 with dhcp3-server_3.1.1-6+lenny4_amd64.deb

#559415#25
Date:
2010-06-24 14:53:12 UTC
From:
To:
That's inconsistent with the version in the initial bug report.
#559415#30
Date:
2010-06-24 15:05:34 UTC
From:
To:
Am 24.06.2010 16:53, schrieb Andrew Pollock:

you are right, sorry, I did take version information from first
bug reporter, 3.1.3-1 is testing and as I said I did not try testing,
only stable

#559415#41
Date:
2026-08-05 17:31:09 UTC
From:
To:
Dear submitter,

as the package isc-dhcp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1143544

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)