KEA service stopping through the day

[Gertjan]

@rafal-arciszewski

As you have a 3100, 'arm' base (32 bits !?) you would be way better of using ISC for the moment.

[propeto13]

before:

Diagnostics > Command Prompt >

Execute Shell Command

rm /tmp/kea4-ctrl-socket.lock

Back to Dashboard and START the kea-dhcp4 service

after:

-this is the way.

[Gertjan]

@propeto13 said in KEA service stopping through the day:

this is the way.

Its 'a' way.
If the /tmp/kea4-ctrl-socket.lock exist, or, as seen here on the forum about kea related posts, the pid file exists when kea starts, it will not core dump, but simply refuse to start.
And it's normal that these files exist, as 'core-dumping' isn't a clean process exist, so these files remain in place = not good.
And you can't start the process kea anymore without manually deleting them.
I think there is a Netgate pfSense System patches (you have this package, right ?) patch that handles this issue.

Ones thse files are gone, you can start kea.
And then, suddenly, it core dumps .... and it's rinse-and-repaet time.