Project

General

Profile

Actions
Copy link

Bug #16217

open

kea2unbound memory exhaustion in

Added by Kevin Burge 3 days ago. Updated 3 days ago.

Status:
New
Priority:
Very Low
Assignee:
-
Category:
DHCP (IPv4)
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.8.0
Affected Architecture:
amd64

Description

Upgraded to 2.8.x yesterday:

2.8.0-RELEASE (amd64)
built on Wed May 21 18:12:00 CDT 2025
FreeBSD 15.0-CURRENT

I am receiving frequent crashes reported:

[29-May-2025 11:08:56 US/Central] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 4096 bytes) in /usr/local/bin/kea2unbound on line 524

I have several VLANs as well as a VPN set up. I'm using IPv4 / IPv6 DHCP servers.

Files

PHP_errors.log (34.3 KB) PHP_errors.log Kevin Burge, 05/29/2025 04:23 PM
Actions
Copy link
 #1

Updated by Jim Pingle 3 days ago

  • Priority changed from Normal to Very Low

Most users who have encountered this were using pfBlockerNG and were not using python mode. Changing pfBlockerNG to python mode eliminated any errors as it does not load all of that data into Unbound directly.

While it may be possible for kea2unbound to somehow detect/skip entries from pfBlockerNG in the future, it may not be viable. Using python mode in pfBlockerNG is much more efficient and the best practice workaround.

Actions
Copy link
 #2

Updated by Kevin Burge 3 days ago

Switched. Thank you!

Actions
Copy link

Also available in: Atom PDF