Project

General

Profile

Actions

Bug #14572

closed

Unused DNSBL files may not be removed

Added by Jove Too 12 months ago. Updated 19 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
pfBlockerNG
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
24.08
Affected Version:
2.7.0
Affected Plus Version:
Affected Architecture:

Description

Hi,

I get the following crash report:

Crash report begins.  Anonymous machine information:

amd64
14.0-CURRENT
FreeBSD 14.0-CURRENT #1 RELENG_2_7_0-n255866-686c8d3c1f0: Wed Jun 28 04:21:19 UTC 2023     root@freebsd:/var/jenkins/workspace/pfSense-CE-snapshots-2_7_0-main/obj/amd64/LwYAddCr/var/jenkins/workspace/pfSense-CE-snapshots-2_7_0-main/sources/FreeBSD-src-REL

Crash report details:

PHP Errors:
[11-Jul-2023 22:58:39 Europe/Brussels] PHP Fatal error:  Uncaught TypeError: in_array(): Argument #2 ($haystack) must be of type array, null given in /usr/local/pkg/pfblockerng/pfblockerng.inc:8836
Stack trace:
#0 /usr/local/pkg/pfblockerng/pfblockerng.inc(8836): in_array('DNSBL_EasyList', NULL)
#1 /usr/local/www/pfblockerng/pfblockerng.php(162): sync_package_pfblockerng('cron')
#2 {main}
thrown in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 8836

Actions #1

Updated by Kris Phillips 11 months ago

Hello,

Is this with the devel or stable branch of pfBlockerNG?

Actions #2

Updated by Jove Too 11 months ago

Hi,

this is stable branch.

Actions #3

Updated by Jordan G 10 months ago

Kris Phillips wrote in #note-1:

Hello,

Is this with the devel or stable branch of pfBlockerNG?

devel and stable branch are effectively the same now fyi

Actions #4

Updated by Marcos M 27 days ago

  • Subject changed from pfBlocker Crash Report to Unused DNSBL files may not be removed
  • Status changed from New to Pull Request Review
  • Assignee set to Marcos M
  • Target version set to 2.8.0
  • Plus Target Version set to 24.08
  • Affected Architecture deleted (amd64)

https://gitlab.netgate.com/pfSense/FreeBSD-ports/-/merge_requests/400

The error is related to removing unused DNSBL files when DNSBL is enabled but not configured.

Actions #5

Updated by Marcos M 19 days ago

  • Status changed from Pull Request Review to Resolved
Actions

Also available in: Atom PDF