<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 6/1/2022 2:22 PM, Gregory Sloop
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1984155955.20220601122252@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 probably (almost certainly) don't have the time
to address all your issues - and I didn't see the initial
post....</p>
<p class="norm">...But some details would perhaps help.</p>
<p class="norm"> </p>
<p class="norm">What OS/Distro, and version? (debian, cent os,
ubuntu etc, / 20.04, 21.10 etc)</p>
<p class="norm">Did you install the distro packages for dhcpd, or
compile your own? (or something else)</p>
<p class="norm">What version of dhcpd?</p>
</blockquote>
<p> That is all in the initial post from the 24th. I will
re-post some parts of it.<br>
</p>
<p><br>
</p>
<p> Debian Bullseye, installed from distro, isc-dhcpd-4.4.1<br>
</p>
<p><br>
</p>
<p> Here is the functional declaration of dhcpd.conf on the
secondary (malfunctioning) server:
<br>
<br>
ddns-update-style none;
<br>
default-lease-time 3600;
<br>
max-lease-time 7200;
<br>
authoritative;
<br>
log-facility local7;
<br>
failover peer "dhcp-failover" {
<br>
address 192.168.1.51;
<br>
port 647;
<br>
peer address 192.168.1.50;
<br>
peer port 647;
<br>
max-response-delay 30;
<br>
max-unacked-updates 10;
<br>
load balance max seconds 3;
<br>
split 0;
<br>
mclt 3600;
<br>
}
<br>
<br>
subnet 192.168.1.0 netmask 255.255.255.0 {
<br>
filename "pxelinux.0";
<br>
next-server 192.168.1.50;
<br>
option routers 192.168.1.1;
<br>
option domain-name "att.net";
<br>
option domain-name-servers 8.8.8.8, 68.94.156.9, 68.94.157.9;
<br>
pool {
<br>
failover peer "dhcp-failover";
<br>
range 192.168.1.220 192.168.1.240;
<br>
}
<br>
}
<br>
<br>
include "/etc/dhcp/dhcpd.static";
<br>
</p>
<blockquote type="cite"
cite="mid:1984155955.20220601122252@sloop.net">
<p class="norm"> </p>
<p>If you only answer some things - those above are the most
important.</p>
<p> </p>
<p class="norm">---</p>
<p class="norm">You mention "secondary" server. Does this mean
just a second server (serving it's own ip block[s]), or a
load-balanced/peer set of servers?</p>
<p class="norm">Running load-balancing/peer servers is quite a bit
more complicated. (Lots of moving parts to go wrong, in weird
ways, unanticipated corner cases etc.)</p>
</blockquote>
Load balancing, but the issues are only on the secondary peer.<br>
<blockquote type="cite"
cite="mid:1984155955.20220601122252@sloop.net">
<p class="norm"> </p>
<p class="norm">You say it's "working" - but how do you know it's
working?</p>
</blockquote>
<p><br>
</p>
<p> It is servicing DHCP requests, and there are no errors in the
log file. The issues are the same whether the primary server is
up and running or disabled.<br>
</p>
<blockquote type="cite"
cite="mid:1984155955.20220601122252@sloop.net">
<p class="norm"> </p>
<p class="norm">But I think getting the basics of what you've done
and intend to do is a good place to start.</p>
<p class="norm"> </p>
<p class="norm">-Greg <br>
</p>
<p class="norm"><br>
</p>
<blockquote class="Odd QOdd rt" prefix="LR> "> I posted
previously about the issues I am having. Nothing I tried,
including completely purging and reinstalling isc-dhcp-server,
would get DHCP to work on my secondary server, so I completely
wiped the server and reloaded the OS. The server is mostly
working now, but there are still some annoying issues. Stopping,
starting, and restarting the server don't quite work properly.<br>
</blockquote>
<p class="norm"><br>
</p>
<blockquote class="Odd QOdd rt" prefix="LR> "> 1.
Systemd reports a spurious error when starting the server from a
clean slate.<br>
</blockquote>
<p class="norm"><br>
</p>
<blockquote class="Odd QOdd rt" prefix="LR> "> isc-dhcp-server.service
- LSB: DHCP server<br>
Loaded: loaded (/etc/init.d/isc-dhcp-server; generated)<br>
Active: failed (Result: exit-code) since Wed 2022-06-01
13:21:26 CDT; 1min 10s ago<br>
Docs: man:systemd-sysv-generator(8)<br>
Process: 19134 ExecStart=/etc/init.d/isc-dhcp-server start
(code=exited, status=1/FAILURE)<br>
Tasks: 4 (limit: 4461)<br>
Memory: 4.8M<br>
CPU: 124ms<br>
CGroup: /system.slice/isc-dhcp-server.service<br>
/usr/sbin/dhcpd -4 -q -cf /etc/dhcp/dhcpd.conf enp11s0<br>
</blockquote>
<p class="norm"><br>
</p>
<blockquote class="Odd QOdd rt" prefix="LR> ">Jun 01 13:21:24
Backup dhcpd[19159]:<br>
Jun 01 13:21:24 Backup dhcpd[19159]: exiting.<br>
Jun 01 13:21:26 Backup isc-dhcp-server[19134]: Starting ISC
DHCPv6 server: dhcpd6check syslog for diagnostics. ...<br>
Jun 01 13:21:26 Backup isc-dhcp-server[19164]: failed!<br>
Jun 01 13:21:26 Backup isc-dhcp-server[19165]: failed!<br>
</blockquote>
<p class="norm"><br>
</p>
<blockquote class="Odd QOdd rt" prefix="LR> "> It
doesn't say what the error is, but the exit code is 1. This
causes the system to think the server has failed to start, but
it does load and remains in memory. It seem to be working
pretty well. Is there some way to get the server to report a
bit more in the way of diagnostics, perhaps in the log, or even
just stderr? Obviously, this isn't a show stopper, but it is a
bit annoying, and it is possible there is something a bit more
insidious going on.<br>
</blockquote>
<p class="norm"><br>
</p>
<blockquote class="Odd QOdd rt" prefix="LR> "> I tried
running the server from the CL with the -d option, but it
doesn't produce any output.<br>
</blockquote>
<div class="email-signature"><br>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
</blockquote>
</body>
</html>