I hope this is not a duplicate, at least I didn't found an issue which matches our problem.

We upgraded our pfSense instance from 2.1.5 to 2.2.4. Everytime I change something on our dhcp service apply those changes or just restart the dhcp services, the leases files gets the wrong permissions, which leads into "no free leases" error in the logs. We do only use IPv4.

History

Our code doesn't set permissions on dhcpd.leases anywhere I see. I can't find any system that has it wrong, and a huge number of people would be screaming if the DHCP server didn't work at all (which would be the end result there). Even rare edge cases would have popped up multiple times by now.

Our code doesn't set permissions on dhcpd.leases anywhere I see. I can't find any system that has it wrong, and a huge number of people would be screaming if the DHCP server didn't work at all (which would be the end result there). Even rare edge cases would have popped up multiple times by now.

you have something non-stock on there?

Hmm, I just ran into this on a fresh install of 2.2.5-RELEASE. Out of the box dhcpd.leases is owned by root and I'm getting "no free leases" in the DHCPD logs.

chowning the file and restarting the dhcpd server results in the file being owned by root again.

Nothing non-stock. I used the latest live-cd/installer ISO and chose quick install then just configured subnets, hostnames, dns.

seems this is some unusual edge case from a recent change in dhcpd. But now I'm seeing it on 2.3 systems that have no problems handing out leases, updating their leases file and otherwise work just fine. Adding a chown dhcpd after where we touch dhcpd.leases if it doesn't exist doesn't change anything, as soon as dhcpd starts the permissions on dhcpd.leases go back to root:_dhcpd.

2.3 has the same dhcpd version as 2.2.6 though. Unless this also stopped in 2.2.6, there is probably some issue here.

Did you have a circumstance where this was reliably replicable before, and now isn't? That's a version prior to 2.3 since it has a System>Firmware menu item, so wouldn't have the dhcpd 4.3 update that we're hoping fixed whatever edge case happened here on occasion. It's something that happened only rarely.