resolving conflicts: dhcp service unavailable

[Matt Causey]

I did some digging, and the problem is easily reproduced by placing  
both boxen in partner-down, then throwing in a potential-conflict  
state somewhere.  Both boxes then stop delivering addresses with the  
resolving conflicts message.

I've upgraded in one of our sites, and it certainly does solve the  
comms-interrupted reconnect bug.  We actually  have a resource  
contention problem causing the pair to drop into comms-interrupted  
every few hours and it seems to recover quickly.

Speaking of resource contention, do you guys have any tuning advice?   
I'm working to shift some workload away from these servers, but the  
servers are -not- heavily loaded and something is causing them to miss  
heartbeats.  Is there some queue there that gets deprioritized when  
the server is busy?

--
Matt

On Jul 2, 2010, at 16:47, "David W. Hankins" <dhankins at isc.org> wrote:

> On Fri, Jun 25, 2010 at 12:25:29PM -0700, Matt Causey wrote:
>> 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?
>
> I don't think any of our bugs caused servers to enter potential-
> conflict, which I think is what you're reporting, but there were some
> bugs e.g. that kept servers from reconnecting, which could have
> prolonged the situation (servers should work out of potential-
> conflict on their own).
>
> Regardless, we won't be able to help you very well if you don't
> upgrade eventually, so it is a good place to start.
>
> -- 
> 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
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users