[stork-users] Agent quits after receiving SIGHUP

Kevin P. Fleming kevin at km6g.us
Sat Feb 5 13:23:29 UTC 2022


I've just installed Stork 1.1.0 on three machines, two are agents
talking to Kea 2.0. Functionality is great. I used the Cloudsmith
packages for Debian.

I've found a small problem though: running 'systemctl reload
isc-stork-agent' results in the agent shutting down, instead of
reloading its configuration. Here's a log snippet from the systemd
journal:

Feb 05 08:19:01 edge21-b systemd[1]: Reloading ISC Stork Agent...
Feb 05 08:19:01 edge21-b systemd[1]: Reloaded ISC Stork Agent.
Feb 05 08:19:01 edge21-b systemd[1]: isc-stork-agent.service:
Deactivated successfully.
Feb 05 08:19:01 edge21-b systemd[1]: isc-stork-agent.service: Consumed
50min 17.876s CPU time.

Is the agent intended to support SIGHUP for reloads?


More information about the Stork-users mailing list