[Kea-users] Updating kea.conf - does it need a daemon restart
Neil Briscoe
neil.briscoe at 6point6.co.uk
Thu Sep 14 16:39:52 UTC 2017
Thanks Jeff.
I had 1.1 on Centos, which *did* have keactrl, but even though it did start the daemon, when I needed to check that status, restart or stop it… it ignored me, did nothing and reporting that nothing was working anyway!
Maybe I will go for a clean centos install, with 1.2 from source and see how we get on.
Thankfully, we are just doing the initial proof of concept and have the backend MySQL sorted (which I can nicely report from as well as having 2 DHCP servers talking to the same DB – perfect for failover etc)… so I can afford to spin up 15 variants of kea!! :D
Cannot wait for a decent GUI to manage this – for both scope management and reporting. I am sure that will come along soon.
Meanwhile… AWS marketplace, new instance...!!
Neil Briscoe | e. neil.briscoe at 6point6.co.uk | t. +44 7793 056923 <tel:+44+7557+526+550> | w. www.6point6.co.uk <http://www.6point6.co.uk/>
On 14/09/2017, 17:34, "Kea-users on behalf of Jeff Kletsky" <kea-users-bounces at lists.isc.org on behalf of kea-dhcp at allycomm.com> wrote:
Gotta love systemd :(
I abandoned the packaged systemd service definitions and approach for a
more "sane" approach of starting keactrl and letting it manage the
various parts of kea, rather than having one service for each component.
I also install kea directly (to /opt, to keep things cleaner) as
Debian/Ubuntu is only on isc-kea-1.1.0-1
Jeff
On 9/14/17 8:49 AM, Neil Briscoe wrote:
> Ah ok. Thanks.
>
> I’ve just tried this and it kills the kea daemon completely. Ubuntu 16.04, kea 1.0.0 for the apt repo.
>
> Using “service kea-dhcp4-server start” to start the daemon.
>
> root at az01-dhcp-02:/# ps -ef | grep kea
> root 14798 1 0 16:39 ? 00:00:00 /usr/sbin/kea-dhcp4 -c /etc/kea/kea-dhcp4.conf
> root 14994 14631 0 16:47 pts/1 00:00:00 grep --color=auto kea
>
> root at az01-dhcp-02:/# kill -SIGHUP 14798
>
> root at az01-dhcp-02:/# ps -ef | grep kea
> root 14999 14631 0 16:47 pts/1 00:00:00 grep --color=auto kea
>
> root at az01-dhcp-02:/# ps -ef | grep kea
> root 15001 14631 0 16:47 pts/1 00:00:00 grep --color=auto kea
>
> root at az01-dhcp-02:/# ps -ef | grep kea
> root 15003 14631 0 16:47 pts/1 00:00:00 grep --color=auto kea
>
> root at az01-dhcp-02:/# ps -ef | grep kea
> root 15005 14631 0 16:47 pts/1 00:00:00 grep --color=auto kea
>
>
> Hmmm. There is no keactrl with the package either, may have to hunt that down in manually install it.
>
>
> Neil Briscoe | e. neil.briscoe at 6point6.co.uk | t. +44 7793 056923 <tel:+44+7557+526+550> | w. www.6point6.co.uk <http://www.6point6.co.uk/>
>
>
>
>
> On 14/09/2017, 16:45, "Thomas Markwalder" <tmark at isc.org> wrote:
>
> On 9/14/17 11:35 AM, Neil Briscoe wrote:
> > Thanks for the speedy reply Thomas.
> >
> > Is “kill –SIGHUP <pid for kea>” the same as “service kea-dhcp4-server restart” or is this slightly different?
> >
> > Thanks,
> >
> > Neil Briscoe | e. neil.briscoe at 6point6.co.uk | t. +44 7793 056923 <tel:+44+7557+526+550> | w. www.6point6.co.uk <http://www.6point6.co.uk/>
> >
> Sending SIGHUP instructs the running server to reload the configuration
> file. Using "service" to restart would actually tell the OS to stop the
> current instance of the server and then restart it.
>
> Thomas
>
>
>
> _______________________________________________
> Kea-users mailing list
> Kea-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/kea-users
_______________________________________________
Kea-users mailing list
Kea-users at lists.isc.org
https://lists.isc.org/mailman/listinfo/kea-users
More information about the Kea-users
mailing list