On 2025-05-31, Sonic <sonicsm...@gmail.com> wrote: > Found Kea did not start after the pkg upgrade to 2.4.2. Mostly due to > some of the paths tied to down those compiled in unless overridden > with an env variable. > However I cannot specify a control-socket in the kea-dhcp4.conf file > without creating an issue where Kea will not start at boot. The reason > is: > "As of Kea 2.4.2, control sockets may only reside in the directory > determined during compilation as "[kea-install-dir]/var/run/kea", > which must also have 0750 access rights." > And indeed if I 'chmod 750 /var/run/kea' then Kea will start, however > on a reboot the permissions on /var/run/kea get changed to 775 and > therefore Kea will not start an fails with: > "ERROR DHCP4_INIT_FAIL failed to initialize Kea server: configuration > error using file '/etc/kea/4kea.conf': 'socket-name' is invalid: > socket path:/var/run/kea does not exist or does not have permssions = > 750" > Workaround for now is to leave the control-socket parameters out of > the conf file(s), but this should not be necessary. > Looks like changing the following line /etc/rc.d/kea : > install -d -o root -g _kea -m 775 /var/run/kea > to > install -d -o root -g _kea -m 750 /var/run/kea > may resolve the issue.
Update packages again, that is done in kea-2.4.2p0 -- Please keep replies on the mailing list.
