I have seen this.
in startup script and also a crontab we do :
*/10 * * * * root chmod 770 /var/run/kea/kea4-ctrl-socket*
(perhaps that should be changed to 660 )
On 3/6/26 10:06 AM, Uwe Jasper wrote:
Hello all,
After the recent Stork update my Stork agent can no longer work with
the Kea control agent to read the DHCP server state. Every time I
restart the Kea DHCP4 service it recreates the socket with the default
permissions and Stork fails. When I manually update the permissions on
run/kea/kea4-ctrl-socket to 660 everything works again, but only till
the next restart.
Has anyone else seen this or now how to permanently fix it?
Thanks,
Uwe Jasper
SYSTEM ADMINISTRATOR
*RiverWoods Group *
121 Technology Drive, Suite A105
Durham, NH 03824
P: 603.658.1707
[email protected] <mailto:[email protected]>
*Check Out Our New Website!* <http://www.riverwoodsnh.org/>
Follow us on LinkedIn <https://www.linkedin.com/company/883471/admin/>
--
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.
[email protected]
