We finally noticed, shortly before your email came in, that we're having issues with comms as well. Did some service restarts, as well as upgrading the stork agents on the server. Stork working-ish, but still having issues (retrieving HA status, for example).
Jason Creviston Network Engineering Team Lead P: 765-795-9305 2 S. West Street - P.O. Box 237, Cloverdale, IN 46120 Book an appointment with me!<https://outlook.office365.com/owa/calendar/[email protected]/bookings/> [cid:codetwo-signature-logo-endeavor_1c9b8f6f-f797-4b22-a7d8-b9c8f1b0c327.png] [cid:codetwo-gigtel-logo2_e109b7e4-b185-40fc-94f2-947f96c612cf.png] [cid:endeavor-it-signature-2_cad37e9b-ad7b-4219-a677-f37914c8d32a.png] weEndeavor.com<http://weendeavor.com/> GigTel.com<http://gigtel.com/> EndeavorIT.com<http://EndeavorIT.com> CONFIDENTIALITY NOTICE: The information in this Email and my attachments are confidential and may be privileged. This Email is intended solely for the named recipient or recipients. If you are not the intended recipient, any use, disclosure, copying or distribution of this Email is prohibited. If you are not the intended recipient, please inform us by replying with the subject line "Wrong Address" and then delete this Email and any attachments. Endeavor Communications uses regularly updated anti-virus software in an attempt to reduce the possibility of transmitting computer viruses. We do not guarantee, however, that any attachments to this Email are virus-free. ________________________________ From: Kea-users <[email protected]> on behalf of Uwe Jasper <[email protected]> Sent: Friday, March 6, 2026 10:06 AM To: [email protected] <[email protected]> Subject: [Kea-users] Stork agent cannot read Kea control agent socket CAUTION: This email is from OUTSIDE our organization. Please do not open/download any attachment or click any link unless you know it's safe. 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]
