Cannot load Status > DHCP Leases Page
-
Hi all. I have a new Netgate 8200 that is set up with 15 VLANs with DHCP enabled. Static DHCP assignments made on almost all hosts. However today when I try to access the DHCP leases page the page tries to load for awhile before failing and showing 50x as an error code in the corner. When I view the crash log it shows the following. I am a little hesitant to reboot the DHCP server since this is a remote production appliance, but I really need to access that leases page so I can track down and make a few more assignments. Has anyone run into anything similar or have any ideas on what could be causing this? Prior to this the DHCP leases page was loading pretty slow, but would load.
Crash report begins. Anonymous machine information:
amd64
15.0-CURRENT
FreeBSD 15.0-CURRENT #0 plus-RELENG_24_03-n256311-e71f834dd81: Fri Apr 19 00:28:14 UTC 2024 root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-24_03-main/obj/amd64/Y4MAEJ2R/var/jenkins/workspace/pfSense-Plus-snapshots-24_03-main/sources/FreeBSCrash report details:
No PHP errors found.
No FreeBSD crash data found.
-
@wmw509 what is pfsense using for dns? If you have a lot of leases, and pfsense tries to do ptr for them to find their names - and its asking say google that can take a long time, and yeah maybe not load.
Whenever you look at the lease table - its going to generate a lot of PTRs... Here I just enabled query logging in unbound, and then went to the dchp leases page.. just a snip
Jun 14 20:03:36 unbound 82264 [82264:0] info: 127.0.0.1 225.2.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:1] info: 127.0.0.1 224.2.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:0] info: 127.0.0.1 219.2.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:0] info: 127.0.0.1 218.2.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:0] info: 127.0.0.1 213.2.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:3] info: 127.0.0.1 217.2.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:2] info: 127.0.0.1 215.2.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:2] info: 127.0.0.1 214.2.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:2] info: 127.0.0.1 228.2.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:0] info: 127.0.0.1 212.2.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:0] info: 127.0.0.1 211.2.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:0] info: 127.0.0.1 229.2.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:0] info: 127.0.0.1 227.2.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:0] info: 127.0.0.1 226.2.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:0] info: 127.0.0.1 223.2.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:0] info: 127.0.0.1 220.2.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:0] info: 127.0.0.1 109.3.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:0] info: 127.0.0.1 110.3.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:1] info: 127.0.0.1 111.3.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:0] info: 127.0.0.1 219.4.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:0] info: 127.0.0.1 220.4.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:0] info: 127.0.0.1 216.4.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:0] info: 127.0.0.1 208.4.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:0] info: 127.0.0.1 207.4.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:1] info: 127.0.0.1 202.4.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:0] info: 127.0.0.1 211.4.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:0] info: 127.0.0.1 200.4.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:1] info: 127.0.0.1 212.4.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:0] info: 127.0.0.1 204.4.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:0] info: 127.0.0.1 205.4.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:0] info: 127.0.0.1 213.4.168.192.in-addr.arpa. PTR IN Jun 14 20:03:36 unbound 82264 [82264:0] info: 127.0.0.1 218.4.168.192.in-addr.arpa. PTR INif you have hundreds or 1000s ? of leases and your not asking local dns - then yeah that could be a problem..
You can look directly in your lease file if your looking for something.. Or just change pfsense to point to your local dns should hopefully allow the page to load.
If you don't want to weed thru the whole file - you could grep for what your looking for
[23.09.1-RELEASE][admin@sg4860.home.arpa]/var/dhcpd/var/db: cat dhcpd.leases | grep -A 8 192.168.3.109 lease 192.168.3.109 { starts 2 2024/06/11 10:55:39; ends 4 2024/06/13 10:55:39; tstp 4 2024/06/13 10:55:39; cltt 2 2024/06/11 10:55:39; binding state free; hardware ethernet 02:11:32:28:ef:98; uid "\001\002\0212(\357\230"; } [23.09.1-RELEASE][admin@sg4860.home.arpa]/var/dhcpd/var/db:[23.09.1-RELEASE][admin@sg4860.home.arpa]/var/dhcpd/var/db: cat dhcpd.leases | grep -B 6 -A 2 28:ef:98 lease 192.168.3.109 { starts 2 2024/06/11 10:55:39; ends 4 2024/06/13 10:55:39; tstp 4 2024/06/13 10:55:39; cltt 2 2024/06/11 10:55:39; binding state free; hardware ethernet 02:11:32:28:ef:98; uid "\001\002\0212(\357\230"; } [23.09.1-RELEASE][admin@sg4860.home.arpa]/var/dhcpd/var/db:I tweaked my grep to just show one example of looking for an IP or a mac, etc.
-
@johnpoz my apologies it took so long to get back to this, but you were 100% right on. Changing the DNS settings to use only local DNS solved this almost immediately. I must have changed that from default on accident when I was adding a DNS server? I don't remember changing that from the default setting.
Anyway, thank you for the help!
-
@wmw509 glad you got it sorted.
