Your message dated Wed, 05 Aug 2026 17:31:09 +0000
with message-id <[email protected]>
and subject line Bug#1143544: Removed package(s) from unstable
has caused the Debian Bug report #559415,
regarding dhcp3-server: occasional segfault soon after startup when configured
for failover
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
559415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559415
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dhcp3-server
Version: 3.1.3-1
Severity: normal
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)
--- End Message ---
--- Begin Message ---
Version: 4.4.3-P1-8+rm
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
[email protected].
Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
