resolving conflicts: dhcp service unavailable

[Matt Causey]

Hello,

I had a problem with my dhcp server last night.  There was a network
hiccup between primary/secondary, and they both ended up in a state
where lots of this was happening on the secondary:

Jun 25 06:14:27 server-102 dhcpd: DHCPREQUEST for 172.24.103.176 from
00:15:70:89:38:91 via 172.24.100.2: not responding (resolving
conflicts)
Jun 25 06:14:27 server-102 dhcpd: DHCPREQUEST for 172.24.103.176 from
00:15:70:89:38:91 via 172.24.100.3: not responding (resolving
conflicts)
Jun 25 06:14:28 server-102 dhcpd: DHCPREQUEST for 172.24.97.175 from
00:26:0b:45:29:2e (xx) via eth0: not responding (resolving conflicts)
Jun 25 06:14:28 server-102 dhcpd: DHCPREQUEST for 172.24.97.32 from
00:26:0b:45:26:26 (xx) via eth0: not responding (resolving conflicts)
Jun 25 06:14:29 server-102 dhcpd: DHCPREQUEST for 172.24.97.54 from
00:26:0b:45:2b:76 (xx) via eth0: not responding (resolving conflicts)
Jun 25 06:14:29 server-102 dhcpd: DHCPREQUEST for 172.24.97.47 from
00:26:0b:45:2a:ca (xx) via eth0: not responding (resolving conflicts)

And this happening on the primary:

un 25 06:14:27server-101 dhcpd: DHCPREQUEST for 172.24.97.60 from
00:26:0b:45:29:30 (xx) via eth0: not responding (peer demands:
resolving conflicts)
Jun 25 06:14:27 server-101 dhcpd: DHCPREQUEST for 172.24.103.176 from
00:15:70:89:38:91 via 172.24.100.2: not responding (peer demands:
resolving conflicts)
Jun 25 06:14:27 server-101 dhcpd: DHCPREQUEST for 172.24.103.176 from
00:15:70:89:38:91 via 172.24.100.3: not responding (peer demands:
resolving conflicts)
Jun 25 06:14:29 server-101 dhcpd: DHCPREQUEST for 172.24.100.136 from
00:17:23:03:cf:87 via 172.24.100.2: not responding (peer demands:
resolving conflicts)
Jun 25 06:14:29 server-101 dhcpd: DHCPREQUEST for 172.24.100.136 from
00:17:23:03:cf:87 via 172.24.100.3: not responding (peer demands:
resolving conflicts)
Jun 25 06:14:29 server-101 dhcpd: DHCPREQUEST for 172.24.101.40 from
00:15:70:39:e4:46 via 172.24.100.2: not responding (peer demands:
resolving conflicts)
Jun 25 06:14:29 server-101 dhcpd: DHCPREQUEST for 172.24.101.40 from
00:15:70:39:e4:46 via 172.24.100.3: not responding (peer demands:
resolving conflicts)

Service was impaired until we bounced dhcpd and killed leases file on
one of the boxes.

We're running 3.1.1, and I see tons of 'lots of failover bugs fixed'
type messages in the stable 4.x stuff.  Is this a known failure that's
fixed there?

--
Matt