<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 6/2/2022 11:30 PM, Gregory Sloop
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:15810207371.20220602213019@sloop.net">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<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>
<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>
</blockquote>
That may well be true. Certainly I was unaware of the split
directive<br>
<blockquote type="cite"
cite="mid:15810207371.20220602213019@sloop.net">
<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>
</blockquote>
Fixed (or at least set to 128).<br>
<blockquote type="cite"
cite="mid:15810207371.20220602213019@sloop.net">
<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>
</blockquote>
<p> No, at this point, neither one is reporting a normal status,
either to or from. In the log file, the secondary shows</p>
<p><br>
</p>
<p>Jun 2 23:50:16 Backup dhcpd[70691]: Server starting service.<br>
Jun 2 23:50:16 Backup dhcpd[70691]: Failover CONNECTACK from
dhcp-failover: already connected<br>
Jun 2 23:50:16 Backup dhcpd[70691]: failover peer dhcp-failover:
I move from startup to recover<br>
Jun 2 23:50:16 Backup dhcpd[70691]: dhcp_failover_put_message:
something went wrong.<br>
Jun 2 23:50:16 Backup dhcpd[70691]: peer dhcp-failover:
disconnected<br>
Jun 2 23:50:21 Backup dhcpd[70691]: Failover CONNECTACK from
dhcp-failover: already connected<br>
Jun 2 23:50:21 Backup dhcpd[70691]: failover peer dhcp-failover:
peer moves from recover to recover<br>
Jun 2 23:50:21 Backup dhcpd[70691]: failover peer dhcp-failover:
requesting full update from peer<br>
Jun 2 23:50:21 Backup dhcpd[70691]: dhcp_failover_put_message:
something went wrong.<br>
Jun 2 23:50:21 Backup dhcpd[70691]: peer dhcp-failover:
disconnected<br>
Jun 2 23:50:21 Backup dhcpd[70691]: Failed to send update request
all message to dhcp-failover: socket is not connected<br>
Jun 2 23:50:26 Backup dhcpd[70691]: Failover CONNECTACK from
dhcp-failover: already connected<br>
Jun 2 23:50:26 Backup dhcpd[70691]: failover peer dhcp-failover:
peer moves from recover to recover<br>
Jun 2 23:50:26 Backup dhcpd[70691]: failover peer dhcp-failover:
requesting full update from peer<br>
Jun 2 23:50:26 Backup dhcpd[70691]: dhcp_failover_put_message:
something went wrong.<br>
Jun 2 23:50:26 Backup dhcpd[70691]: peer dhcp-failover:
disconnected<br>
Jun 2 23:50:26 Backup dhcpd[70691]: Failed to send update request
all message to dhcp-failover: socket is not connected</p>
<p><br>
</p>
<p> In the leases file, the secondary shows</p>
<p><br>
</p>
<p># The format of this file is documented in the dhcpd.leases(5)
manual page.<br>
# This lease file was written by isc-dhcp-4.4.1<br>
<br>
# authoring-byte-order entry is generated, DO NOT DELETE<br>
authoring-byte-order little-endian;<br>
<br>
failover peer "dhcp-failover" state {<br>
my state recover at 1 2022/05/30 09:56:55;<br>
partner state recover at 5 2022/06/03 04:42:48;<br>
}<br>
failover peer "dhcp-failover" state {<br>
my state recover at 1 2022/05/30 09:56:55;<br>
partner state recover at 5 2022/06/03 04:42:48;<br>
}<br>
server-duid "\000\001\000\001*'QgPF]e\025\234";<br>
<br>
failover peer "dhcp-failover" state {<br>
my state recover at 1 2022/05/30 09:56:55;<br>
partner state recover at 5 2022/06/03 04:42:48;<br>
}<br>
failover peer "dhcp-failover" state {<br>
my state recover at 1 2022/05/30 09:56:55;<br>
partner state recover at 5 2022/06/03 04:50:21;<br>
}<br>
failover peer "dhcp-failover" state {<br>
my state recover at 1 2022/05/30 09:56:55;<br>
partner state recover at 5 2022/06/03 04:50:26;<br>
}<br>
<br>
</p>
<p> In the log file, the primary shows</p>
<p><br>
</p>
<p>Jun 2 23:40:57 RAID-Server dhcpd[5057]: Internet Systems
Consortium DHCP Server 4.4.1<br>
Jun 2 23:40:57 RAID-Server dhcpd[5057]: Copyright 2004-2018
Internet Systems Consortium.<br>
Jun 2 23:40:57 RAID-Server dhcpd[5057]: All rights reserved.<br>
Jun 2 23:40:57 RAID-Server dhcpd[5057]: For info, please visit
<a class="moz-txt-link-freetext" href="https://www.isc.org/software/dhcp/">https://www.isc.org/software/dhcp/</a><br>
Jun 2 23:40:57 RAID-Server dhcpd[5057]: Wrote 0 deleted host
decls to leases file.<br>
Jun 2 23:40:57 RAID-Server dhcpd[5057]: Wrote 0 new dynamic host
decls to leases file.<br>
Jun 2 23:40:57 RAID-Server dhcpd[5057]: Wrote 0 leases to leases
file.<br>
Jun 2 23:40:57 RAID-Server dhcpd[5057]: failover peer
dhcp-failover: I move from recover to startup<br>
Jun 2 23:40:57 RAID-Server dhcpd[5057]: Server starting service.<br>
Jun 2 23:41:12 RAID-Server dhcpd[5057]: failover peer
dhcp-failover: I move from startup to recover<br>
Jun 2 23:41:12 RAID-Server dhcpd[5057]: DHCPDISCOVER from
64:db:a0:15:55:e0 via enp6s0: not responding (recovering)<br>
Jun 2 23:41:14 RAID-Server dhcpd[5057]: DHCPDISCOVER from
d8:1f:12:6a:8e:9b via enp6s0: not responding (recovering)<br>
Jun 2 23:41:25 RAID-Server dhcpd[5057]: DHCPDISCOVER from
64:db:a0:15:55:e0 via enp6s0: not responding (recovering)<br>
Jun 2 23:41:25 RAID-Server dhcpd[5057]: DHCPREQUEST for 0.0.0.0
from 20:17:42:1e:51:d5 via enp6s0: unknown lease 0.0.0.0.<br>
Jun 2 23:41:33 RAID-Server dhcpd[5057]: DHCPDISCOVER from
64:db:a0:15:55:e0 via enp6s0: not responding (recovering)<br>
Jun 2 23:41:41 RAID-Server dhcpd[5057]: DHCPDISCOVER from
64:db:a0:15:55:e0 via enp6s0: not responding (recovering)<br>
Jun 2 23:41:54 RAID-Server dhcpd[5057]: DHCPDISCOVER from
60:01:94:f0:41:48 via enp6s0: not responding (recovering)<br>
Jun 2 23:42:00 RAID-Server dhcpd[5057]: DHCPDISCOVER from
64:db:a0:15:55:e0 via enp6s0: not responding (recovering)<br>
Jun 2 23:42:14 RAID-Server dhcpd[5057]: DHCPDISCOVER from
d8:1f:12:6a:8e:9b via enp6s0: not responding (recovering)<br>
Jun 2 23:42:28 RAID-Server dhcpd[5057]: Failover CONNECTACK from
dhcp-failover: already connected<br>
Jun 2 23:42:28 RAID-Server dhcpd[5057]: failover peer
dhcp-failover: peer moves from recover to recover<br>
Jun 2 23:42:28 RAID-Server dhcpd[5057]: failover peer
dhcp-failover: requesting full update from peer<br>
Jun 2 23:42:28 RAID-Server dhcpd[5057]:
dhcp_failover_put_message: something went wrong.<br>
Jun 2 23:42:28 RAID-Server dhcpd[5057]: peer dhcp-failover:
disconnected<br>
Jun 2 23:42:28 RAID-Server dhcpd[5057]: Failed to send update
request all message to dhcp-failover: socket is not connected<br>
Jun 2 23:42:33 RAID-Server dhcpd[5057]: peer dhcp-failover:
disconnected<br>
Jun 2 23:42:38 RAID-Server dhcpd[5057]: peer dhcp-failover:
disconnected<br>
Jun 2 23:42:38 RAID-Server dhcpd[5057]: Failover CONNECTACK from
dhcp-failover: already connected<br>
Jun 2 23:42:38 RAID-Server dhcpd[5057]: failover peer
dhcp-failover: peer moves from recover to recover<br>
Jun 2 23:42:38 RAID-Server dhcpd[5057]: failover peer
dhcp-failover: requesting full update from peer<br>
Jun 2 23:42:38 RAID-Server dhcpd[5057]:
dhcp_failover_put_message: something went wrong.</p>
<p>Jun 2 23:42:38 RAID-Server dhcpd[5057]: peer dhcp-failover:
disconnected</p>
<p>...</p>
<p>Jun 3 00:17:14 RAID-Server dhcpd[5057]: DHCPDISCOVER from
d8:1f:12:6a:8e:9b via enp6s0: not responding (recovering)<br>
Jun 3 00:17:44 RAID-Server dhcpd[5057]: DHCPDISCOVER from
64:db:a0:15:55:e0 via enp6s0: not responding (recovering)<br>
Jun 3 00:17:55 RAID-Server dhcpd[5057]: DHCPDISCOVER from
60:01:94:f0:41:48 via enp6s0: not responding (recovering)<br>
Jun 3 00:17:56 RAID-Server dhcpd[5057]: DHCPDISCOVER from
64:db:a0:15:55:e0 via enp6s0: not responding (recovering)<br>
Jun 3 00:18:14 RAID-Server dhcpd[5057]: DHCPDISCOVER from
d8:1f:12:6a:8e:9b via enp6s0: not responding (recovering)<br>
Jun 3 00:18:16 RAID-Server dhcpd[5057]: DHCPDISCOVER from
64:db:a0:15:55:e0 via enp6s0: not responding (recovering)<br>
Jun 3 00:18:23 RAID-Server dhcpd[5057]: DHCPDISCOVER from
64:db:a0:15:55:e0 via enp6s0: not responding (recovering)<br>
Jun 3 00:18:55 RAID-Server dhcpd[5057]: DHCPDISCOVER from
60:01:94:f0:41:48 via enp6s0: not responding (recovering)<br>
Jun 3 00:18:55 RAID-Server dhcpd[5057]: DHCPREQUEST for
192.168.1.66 from 20:17:42:1e:51:d5 via enp6s0<br>
Jun 3 00:18:55 RAID-Server dhcpd[5057]: DHCPACK on 192.168.1.66
to 20:17:42:1e:51:d5 via enp6s0<br>
Jun 3 00:19:14 RAID-Server dhcpd[5057]: DHCPDISCOVER from
d8:1f:12:6a:8e:9b via enp6s0: not responding (recovering)<br>
Jun 3 00:19:36 RAID-Server dhcpd[5057]: DHCPDISCOVER from
64:db:a0:15:55:e0 via enp6s0: not responding (recovering)<br>
Jun 3 00:19:51 RAID-Server dhcpd[5057]: DHCPDISCOVER from
64:db:a0:15:55:e0 via enp6s0: not responding (recovering)<br>
Jun 3 00:19:55 RAID-Server dhcpd[5057]: DHCPDISCOVER from
60:01:94:f0:41:48 via enp6s0: not responding (recovering)<br>
Jun 3 00:20:12 RAID-Server dhcpd[5057]: DHCPDISCOVER from
64:db:a0:15:55:e0 via enp6s0: not responding (recovering)<br>
Jun 3 00:20:14 RAID-Server dhcpd[5057]: DHCPDISCOVER from
d8:1f:12:6a:8e:9b via enp6s0: not responding (recovering)<br>
Jun 3 00:20:22 RAID-Server dhcpd[5057]: DHCPREQUEST for
192.168.0.18 from 68:57:2d:a9:b0:f8 via enp6s0<br>
Jun 3 00:20:22 RAID-Server dhcpd[5057]: DHCPACK on 192.168.0.18
to 68:57:2d:a9:b0:f8 via enp6s0<br>
Jun 3 00:20:45 RAID-Server dhcpd[5057]: DHCPREQUEST for
192.168.0.23 from 68:57:2d:a9:b3:38 via enp6s0<br>
Jun 3 00:20:45 RAID-Server dhcpd[5057]: DHCPACK on 192.168.0.23
to 68:57:2d:a9:b3:38 via enp6s0<br>
</p>
<p> And in the leases file</p>
<p># The format of this file is documented in the dhcpd.leases(5)
manual page.<br>
# This lease file was written by isc-dhcp-4.4.1<br>
<br>
# authoring-byte-order entry is generated, DO NOT DELETE<br>
authoring-byte-order little-endian;<br>
<br>
failover peer "dhcp-failover" state {<br>
my state recover at 2 2020/02/11 08:30:01;<br>
partner state recover at 1 2022/05/30 09:57:06;<br>
}<br>
failover peer "dhcp-failover" state {<br>
my state recover at 2 2020/02/11 08:30:01;<br>
partner state recover at 1 2022/05/30 09:57:06;<br>
}<br>
server-duid "\000\001\000\001%\325\"\211\010bf\241@\223";<br>
<br>
failover peer "dhcp-failover" state {<br>
my state recover at 2 2020/02/11 08:30:01;<br>
partner state recover at 1 2022/05/30 09:57:06;<br>
}<br>
failover peer "dhcp-failover" state {<br>
my state recover at 2 2020/02/11 08:30:01;<br>
partner state recover at 5 2022/06/03 04:42:28;<br>
}<br>
failover peer "dhcp-failover" state {<br>
my state recover at 2 2020/02/11 08:30:01;<br>
partner state recover at 5 2022/06/03 04:42:38;<br>
}<br>
failover peer "dhcp-failover" state {<br>
my state recover at 2 2020/02/11 08:30:01;<br>
partner state recover at 5 2022/06/03 04:42:43;<br>
}<br>
failover peer "dhcp-failover" state {<br>
my state recover at 2 2020/02/11 08:30:01;<br>
partner state recover at 5 2022/06/03 04:42:48;<br>
}<br>
failover peer "dhcp-failover" state {<br>
my state recover at 2 2020/02/11 08:30:01;<br>
partner state recover at 5 2022/06/03 04:42:53;<br>
}<br>
failover peer "dhcp-failover" state {<br>
my state recover at 2 2020/02/11 08:30:01;<br>
partner state recover at 5 2022/06/03 04:50:16;<br>
}<br>
failover peer "dhcp-failover" state {<br>
my state recover at 2 2020/02/11 08:30:01;<br>
partner state recover at 5 2022/06/03 04:50:26;<br>
}<br>
</p>
<p>(Continued)<br>
</p>
</body>
</html>