Send dhcp-users mailing list submissions to
dhcp-users@lists.isc.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
dhcp-users-requ...@lists.isc.org
You can reach the person managing the list at
dhcp-users-ow...@lists.isc.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."
Today's Topics:
1. Re: DHCP issues 2 (Simon)
2. Re: DHCP issues 2 (Leslie Rhorer)
3. Re: DHCP issues 2 (Leslie Rhorer)
4. Re: DHCP issues 2 (Leslie Rhorer)
----------------------------------------------------------------------
Message: 1
Date: Thu, 2 Jun 2022 20:00:23 +0100
From: Simon <dh...@thehobsons.co.uk>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: DHCP issues 2
Message-ID: <6fbd8744-8f19-4a5f-adb4-11e4510b1...@thehobsons.co.uk>
Content-Type: text/plain; charset=utf-8
Leslie Rhorer <lesrho...@siliconventures.net> wrote:
> 2. Stopping the service does not actually do anything. The .pid file
> remains intact and the service remains in memory. Having to manually delete
> the .pid file and manually kill the daemon is a pain, especially right now
> since I am setting things up and restarting the service a lot.
That is easy to answer - it?s NOT a DHCP server issue, that?s a
distro/packaging issue.
Since I don?t use systemd, I can?t help further in terms of the
startup/shutdown problems.
Simon
------------------------------
Message: 2
Date: Thu, 2 Jun 2022 17:52:41 -0500
From: Leslie Rhorer <lesrho...@siliconventures.net>
To: dhcp-users@lists.isc.org
Subject: Re: DHCP issues 2
Message-ID: <823d3957-91b7-90b1-2c0d-c324fbcfb...@siliconventures.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
On 6/2/2022 2:00 PM, Simon wrote:
> Leslie Rhorer <lesrho...@siliconventures.net> wrote:
>
>> 2. Stopping the service does not actually do anything. The .pid file
>> remains intact and the service remains in memory. Having to manually delete
>> the .pid file and manually kill the daemon is a pain, especially right now
>> since I am setting things up and restarting the service a lot.
> That is easy to answer - it?s NOT a DHCP server issue, that?s a
> distro/packaging issue.
> Since I don?t use systemd, I can?t help further in terms of the
> startup/shutdown problems.
I would be inclined to agree, except for two things:
1. Why is it happening on the secondary and not the primary? They are the
same version of the same distro.
2. Why is dhcpd sending an exit code of 1? That is why systemd thinks there
is a failure. Dhcpd (or any daemon) is supposed to send an exit code of 0.
------------------------------
Message: 3
Date: Thu, 2 Jun 2022 18:09:41 -0500
From: Leslie Rhorer <lesrho...@siliconventures.net>
To: dhcp-users@lists.isc.org
Subject: Re: DHCP issues 2
Message-ID: <836b9e6c-186d-c82d-4a1f-be3d0bf3c...@siliconventures.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
??? OK, this seems a little odd, but maybe it is normal operation.?
Shouldn't the daemon be writing to the leases file? It doesn't seem to
be.? It creates two files per server, one named xxx.leases and one named
xxx.leases~.? The "~" usuallty means a temporary file, doesn't it??
Neither is written to after the daemon is stable.
On 6/2/2022 5:52 PM, Leslie Rhorer wrote:
> On 6/2/2022 2:00 PM, Simon wrote:
>> Leslie Rhorer <lesrho...@siliconventures.net> wrote:
>>
>>> ???? 2. Stopping the service does not actually do anything.? The
>>> .pid file remains intact and the service remains in memory.? Having
>>> to manually delete the .pid file and manually kill the daemon is a
>>> pain, especially right now since I am setting things up and
>>> restarting the service a lot.
>> That is easy to answer - it?s NOT a DHCP server issue, that?s a
>> distro/packaging issue.
>> Since I don?t use systemd, I can?t help further in terms of the
>> startup/shutdown problems.
>
> ????I would be inclined to agree, except for two things:
>
> 1.? Why is it happening on the secondary and not the primary? They are
> the same version of the same distro.
>
> 2.? Why is dhcpd sending an exit code of 1?? That is why systemd
> thinks there is a failure.? Dhcpd (or any daemon) is supposed to send
> an exit code of 0.
>
------------------------------
Message: 4
Date: Thu, 2 Jun 2022 18:30:12 -0500
From: Leslie Rhorer <lesrho...@siliconventures.net>
To: dhcp-users@lists.isc.org
Subject: Re: DHCP issues 2
Message-ID: <9199916e-61f7-d154-dddb-2f23328c7...@siliconventures.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
On 6/2/2022 5:52 PM, Leslie Rhorer wrote:
> On 6/2/2022 2:00 PM, Simon wrote:
>> Leslie Rhorer <lesrho...@siliconventures.net> wrote:
>>
>>> ???? 2. Stopping the service does not actually do anything.? The
>>> .pid file remains intact and the service remains in memory.? Having
>>> to manually delete the .pid file and manually kill the daemon is a
>>> pain, especially right now since I am setting things up and
>>> restarting the service a lot.
>> That is easy to answer - it?s NOT a DHCP server issue, that?s a
>> distro/packaging issue.
>> Since I don?t use systemd, I can?t help further in terms of the
>> startup/shutdown problems.
>
> ????I would be inclined to agree, except for two things:
>
> 1.? Why is it happening on the secondary and not the primary? They are
> the same version of the same distro.
>
> 2.? Why is dhcpd sending an exit code of 1?? That is why systemd
> thinks there is a failure.? Dhcpd (or any daemon) is supposed to send
> an exit code of 0.
??? I found the problem.? It was not a distro issue.? It was my error.?
Before I wiped the OS, there was some sort of fatal error going on.? For
testing purposes, I disabled IPv6 in the /etc/defaults/isc-dhcp-server
file, but I accidentally neglected to comment out the INTERFACESv6
line.? This was causing dhcpd to issue an exit code of 1.? This not only
caused the start option to report an error, but also was preventing the
stop option from cleaning up the .pid file and terminating the daemon.?
Before wiping the OS, I copied all the config files to a backup and
restored them after the re-install.? This cleared whatever was causing
the fatal issue, but retained the spurious error report.
------------------------------
Subject: Digest Footer
_______________________________________________
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users
------------------------------
End of dhcp-users Digest, Vol 164, Issue 3
******************************************
