<html><head>
<style type="text/css" title="rt_noDelete">
blockquote.rt {
margin: 0 0 15px;
border-left: 4px solid #81c784;
padding: 0 0 0 12px;
display: block;
}
p { margin: 0 0 0 0 }
.email-signature {font-family:"Arial"; font-size: 8pt; font-style: italic; font-weight: normal; text-decoration: none; }
</style></head><body><p class="norm">I'm not at all sure your servers are running well, or that they're handling leases the way you think.</p><p class="norm"> </p><p>One probably trivial thing.</p><p class="norm">In the config you sent, you have a very odd split, of zero.</p><p class="norm">That forces all the balance to one side. Toward the secondary, IIRC. Perhaps you're only testing something I don't know. I think 128 is a "normal" split. (I don't think there's any good reason not to balance them evenly - at least I've never heard a use case that made sense.)</p><p class="norm"> </p><p>More toward things that sure seem like symptoms of your peers not communicating properly.</p><p> </p><p>In the logs;</p><p class="norm">Do you see the two peers go to "normal" when you start them both up. And interrupted when one is down?</p><p class="norm">something like:</p><p>failover peer dhcp-failover: peer moves from normal to communications-interrupted </p><p>failover peer dhcp-failover: I move from startup to normal </p><p>failover peer dhcp-failover: peer moves from communications-interrupted to normal </p><p>failover peer dhcp-failover: Both servers normal </p><p> </p><p class="norm">Are you seeing balance messages every hour as the two re-balance the available lease pool?</p><p class="norm"> </p><p>You say they are both handling leases properly, but how do you know this? (That a machine gets a lease from somewhere is not good evidence.)</p><p> </p><p>A packet capture in front of the secondary might be helpful to see what traffic is passing - both to the peer and to clients.</p><p> </p><p>(I hate making captures, at least as much as the next person, but dang if they don't, nearly always, show something that was different than I assumed. So, I've just gotten a lot less averse to getting captures. Yeah, they'll probably take me extra time to setup and get and paw through, [all when I could be fixin' stuff!] but they can save hours or days of fruitless searching for a fix, when I don't even really *know* what's wrong yet. Don't know about anyone else, but fixing problems gets a whole lot easier when I actually know what's wrong, or at least have a good idea what's going on. :)</p><p> </p><p>-Greg</p><p class="norm"> <br/>
</p><p class="norm"><br/></p><p class="norm"></p><blockquote class="rt">
<p> I don't think so. The secondary server seems to have gone
completely silent, now, but I am getting a ton of them on the
primary server, now.<br/>
</p>
<div class="moz-cite-prefix">On 6/2/2022 8:06 PM, Richard L.
Hamilton wrote:<br/>
</div>
<blockquote cite="mid:7C852502-1E98-4EDF-9293-6DF289BFFB24@smart.net" type="cite">
<meta http-equiv="Content-Type" content="text/html;"/>
<a class="moz-txt-link-freetext" href="https://serverfault.com/questions/313008/isc-dhcp-fails-to-sync-leases-between-peers" moz-do-not-send="true">https://serverfault.com/questions/313008/isc-dhcp-fails-to-sync-leases-between-peers</a>
<div class=""><br/>
</div>
<div class="">Probably the two DHCP servers weren’t able to talk
to each other, not surprising when one was having problems.<br/>
<div><br/>
<blockquote class="" type="cite">
<div class="">On Jun 2, 2022, at 7:42 PM, Leslie Rhorer <<a class="moz-txt-link-freetext" href="mailto:lesrhorer@siliconventures.net" moz-do-not-send="true">lesrhorer@siliconventures.net</a>>
wrote:</div>
<br/>
<div class="">
<div class=""><br/>
During troubleshooting of my recent issue, I got
tons of duplicates of errors like the following. They
seem to have stopped, now, but I am curious what they
meant.<br/>
<br/>
<br/>
Jun 1 00:31:56 Backup dhcpd[15785]: DHCPDISCOVER from
60:01:94:f0:41:48 via enp11s0: not responding
(recovering)<br/>
<br/>
-- <br/>
ISC funds the development of this software with paid
support subscriptions. Contact us at <a class="moz-txt-link-freetext" href="https://www.isc.org/contact/" moz-do-not-send="true">https://www.isc.org/contact/</a>
for more information.<br/>
<br/>
dhcp-users mailing list<br/>
<a class="moz-txt-link-freetext" href="mailto:dhcp-users@lists.isc.org" moz-do-not-send="true">dhcp-users@lists.isc.org</a><br/>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/dhcp-users">https://lists.isc.org/mailman/listinfo/dhcp-users</a><br/>
<br/>
</div>
</div>
</blockquote>
</div>
<br/>
</div>
<br/>
<fieldset class="moz-mime-attachment-header"></fieldset>
</blockquote>
</blockquote><div class="email-signature"><br/>
</div></body>