DHCPv4 not starting after update - solved by reboot, sorry

[meschmesch]

Hi everyone,
after upgrading to 21.1.1 my DHCPv4 server is not starting any more. However, the DHCP log files report that new devices are assigned respective IP-adresses. Further, the DHCP log file says:

2021-02-11T10:45:18   dhcpd[28766]   includes a bootp server.   
2021-02-11T10:45:18   dhcpd[28766]   are not running HP JetAdmin software, which   
2021-02-11T10:45:18   dhcpd[28766]   bootp in /etc/inetd.conf. Also make sure you   
2021-02-11T10:45:18   dhcpd[28766]   running and that there's no entry for dhcp or   
2021-02-11T10:45:18   dhcpd[28766]   Please make sure there is no other dhcp server   
2021-02-11T10:45:18   dhcpd[28766]   Can't bind to dhcp address: Address already in use

So, somehow the DHCP server is assigning DHCP leases, but doesn't work at the same time? I have no idea what to do. Thanks for any advice!

---

Problem was solved by a simple reboot. Sorry.

[Karl]

Hi,

just wanted to add: I had the same problem using 21.1.1!
I made some changes to the dhcpd via webGUI (changed the dhcp range, added another dhcp-range for another interface, more small stuff), opnsense saved everything without complaining, and then: same messages in log as meschmesch posted. Also: my new dhcp-range was not offered to the network, still old IPs were given out.
dhcpd status on dashboard was "red" (stopped), I could not start it by clicking on the "play" (start) button.
After the reboot everything worked (correct dhcp range offered, dhcpd webGUI dashboard button "green" again).
Took me a lot of time, until I found the forum post of meschmesch. Never would have thought I have to reboot a BSD to get something to work.
This seems lika a bug in opnsense to me.

[you]

Same here.

DHCPv4 shows "Stopped" on dashboard. However, according to logs it is still running and clients still receive IP addresses. A reboot indeed solves it, until changes are made. I did not touch DHCP settings though. The last change I did was related to DynDNS and Gateway Monitoring.

@franco might be worth to look at it?

@meschmesch: might be appropriate to temporarily change thread title to "not solved yet?" so that it gains attention.