Package: dhcp3-server Version: 3.1.1-5 Severity: important I have a pair of DHCP servers (both i386 architecture) running fine with failover peering since 2004. They started as Woody or Sarge.
Yesterday I dist-upgraded the master server from Etch to Lenny which worked fine. Peering still worked between 3.0.4 (slave, Etch) and 3.1.1 (master, Lenny) although there's no warranty for that by upstream. So today I dist-upgraded the slave server (called ruchen). That worked fine, too -- until the first restart of the DHCPd on the master server (called stock). Since then the DHCPd on the master server always stops working with the following error message: failover peer ruchen: I move from normal to startup Failover CONNECT from stock: unknown failover relationship name Only the slave server currently provides DHCP in our network. Modifying the states in the lease file (as suggested somewhere on the mailing list) didn't work, neither did starting with an empty lease file. The I ran the DHCPd in debug mode from the command line and it seems to have crashed: r...@stock:/var/lib/dhcp3 # dhcpd3 -d Internet Systems Consortium DHCP Server V3.1.1 Copyright 2004-2008 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Wrote 0 deleted host decls to leases file. Wrote 0 new dynamic host decls to leases file. Wrote 0 leases to leases file. Listening on LPF/eth2/00:0a:5e:54:6b:f8/VLAN136 Sending on LPF/eth2/00:0a:5e:54:6b:f8/VLAN136 Listening on LPF/eth1/00:0a:5e:54:ce:c2/VLAN745 Sending on LPF/eth1/00:0a:5e:54:ce:c2/VLAN745 Listening on LPF/eth0/00:11:09:c7:83:1b/VLAN137 Sending on LPF/eth0/00:11:09:c7:83:1b/VLAN137 Sending on Socket/fallback/fallback-net failover peer ruchen: I move from normal to startup Failover CONNECT from stock: unknown failover relationship name *** glibc detected *** dhcpd3: free(): invalid pointer: 0x09e4a9d4 *** ======= Backtrace: ========= /lib/i686/cmov/libc.so.6[0xb7e74624] /lib/i686/cmov/libc.so.6(cfree+0x96)[0xb7e76826] dhcpd3[0x8060f5d] dhcpd3[0x8061fdb] dhcpd3[0x80684ca] dhcpd3[0x80afaf7] dhcpd3[0x80a9194] dhcpd3[0x80adad0] dhcpd3[0x8081de8] dhcpd3[0x804b906] /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7e1c455] dhcpd3[0x8049ed1] ======= Memory map: ======== 08048000-080c9000 r-xp 00000000 09:01 524425 /usr/sbin/dhcpd3 080c9000-080cc000 rw-p 00080000 09:01 524425 /usr/sbin/dhcpd3 080cc000-080d6000 rw-p 080cc000 00:00 0 09e44000-09f59000 rw-p 09e44000 00:00 0 [heap] b7b00000-b7b21000 rw-p b7b00000 00:00 0 b7b21000-b7c00000 ---p b7b21000 00:00 0 b7cbf000-b7ccb000 r-xp 00000000 09:01 655503 /lib/libgcc_s.so.1 b7ccb000-b7ccc000 rw-p 0000b000 09:01 655503 /lib/libgcc_s.so.1 b7cd3000-b7df9000 rw-p b7cd3000 00:00 0 b7df9000-b7e03000 r-xp 00000000 09:01 655428 /lib/i686/cmov/libnss_files-2.7.so b7e03000-b7e05000 rw-p 00009000 09:01 655428 /lib/i686/cmov/libnss_files-2.7.so b7e05000-b7e06000 rw-p b7e05000 00:00 0 b7e06000-b7f5b000 r-xp 00000000 09:01 655391 /lib/i686/cmov/libc-2.7.so b7f5b000-b7f5c000 r--p 00155000 09:01 655391 /lib/i686/cmov/libc-2.7.so b7f5c000-b7f5e000 rw-p 00156000 09:01 655391 /lib/i686/cmov/libc-2.7.so b7f5e000-b7f62000 rw-p b7f5e000 00:00 0 b7f67000-b7f68000 rw-p b7f67000 00:00 0 b7f69000-b7f6a000 rw-p b7f69000 00:00 0 b7f6a000-b7f6b000 r-xp b7f6a000 00:00 0 [vdso] b7f6b000-b7f85000 r-xp 00000000 09:01 655363 /lib/ld-2.7.so b7f85000-b7f87000 rw-p 0001a000 09:01 655363 /lib/ld-2.7.so bfb71000-bfb86000 rw-p bffeb000 00:00 0 [stack] Aborted r...@stock:/var/lib/dhcp3 # Here's the gdb backtrace: Program received signal SIGABRT, Aborted. 0xb7fd6424 in __kernel_vsyscall () (gdb) bt #0 0xb7fd6424 in __kernel_vsyscall () #1 0xb7e9d640 in raise () from /lib/i686/cmov/libc.so.6 #2 0xb7e9f018 in abort () from /lib/i686/cmov/libc.so.6 #3 0xb7eda34d in __libc_message () from /lib/i686/cmov/libc.so.6 #4 0xb7ee0624 in malloc_printerr () from /lib/i686/cmov/libc.so.6 #5 0xb7ee2826 in free () from /lib/i686/cmov/libc.so.6 #6 0x08060f5d in ?? () #7 0x08f21554 in ?? () #8 0x080bcfe4 in ?? () #9 0x0000100f in ?? () #10 0x0806159c in ?? () #11 0x00000008 in ?? () #12 0x080bcfe4 in ?? () #13 0x00000fd7 in ?? () #14 0x01ee2826 in ?? () #15 0x00000000 in ?? () (gdb) The master server stock (on which this happens) already runs the Lenny 2.6.26 kernel (see also below), while ruchen, the slave server, already has Lenny userland but has not yet been rebooted since the dist-upgrade and still runs Etch's 2.6.18 kernel, since I can't risk a downtime of our remaining working DHCP server. Since our configuration has a lot of include files and nearly a thousand configured static IPs (biggest network is a /21), I do not include it here, but will provide a tar ball with the whole configuration and lease files of both servers on request by e-mail if necessary. -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages dhcp3-server depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii debianutils 2.30 Miscellaneous utilities specific t ii dhcp3-common 3.1.1-5 common files used by all the dhcp3 ii libc6 2.7-18 GNU C Library: Shared libraries ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip dhcp3-server recommends no packages. Versions of packages dhcp3-server suggests: pn dhcp3-server-ldap <none> (no description available) -- debconf information: * dhcp3-server/new_auth_behavior: * dhcp3-server/interfaces: * dhcp3-server/new_next-server_behaviour: * dhcp3-server/config_warn: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
