Project

General

Profile

Actions
Copy link

Bug #16814

open

High CPU after upgrade to 26.03-RELEASE

Added by Israel Fleischer 21 days ago. Updated 11 days ago.

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

0%

Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
26.03
Affected Architecture:
1541

Description

I was running 25.07.1 and updated to 26.03 on 4-13-2026 06:15. Since updated CPU was spiking. Tracked it to pfblockerng, and specifically filterlog. Turning off pfblockerng normalizes CPU. Running it with larger blocklists logging off seemed to ease the CPU as well.
See attached images.

Files

Download all files
Screenshot 2026-04-27 170021.png (240 KB) Screenshot 2026-04-27 170021.png Israel Fleischer, 04/28/2026 10:46 PM
unnamed.png (16 KB) unnamed.png Israel Fleischer, 04/28/2026 10:46 PM
image-Apr-27-2026-09-14-56-5367-PM.png (60.1 KB) image-Apr-27-2026-09-14-56-5367-PM.png Israel Fleischer, 04/28/2026 10:46 PM
Screenshot 2026-05-07 113223.png (27.4 KB) Screenshot 2026-05-07 113223.png Israel Fleischer, 05/07/2026 03:32 PM
Screenshot_20260508_203738.png (86.7 KB) Screenshot_20260508_203738.png Kris Phillips, 05/09/2026 01:38 AM
Actions
Copy link
 #1

Updated by Kris Phillips 17 days ago

I'm unable to reproduce this with GeoIP, so this must specifically be an issue with DNSBL, as suspected.

Actions
Copy link
 #2

Updated by Israel Fleischer 16 days ago

DNSBL is not enabled - so that cannot be the issue.

Actions
Copy link
 #3

Updated by Israel Fleischer 12 days ago

Kris,

In your tests do you have any blocklists loaded? We do have somewhat of a larger setup with multiple lists one which is quite large (~87k records). However DNSBL is not enabled (I checked this as part of my initial troubleshooting).

I will disable the larger list and see if that does anything but the CPU seemed to have been tied directly to pfblockerng filterlog.

Actions
Copy link
 #4

Updated by Kris Phillips 11 days ago

Israel Fleischer wrote in #note-3:

Kris,

In your tests do you have any blocklists loaded? We do have somewhat of a larger setup with multiple lists one which is quite large (~87k records). However DNSBL is not enabled (I checked this as part of my initial troubleshooting).

I will disable the larger list and see if that does anything but the CPU seemed to have been tied directly to pfblockerng filterlog.

I have several large lists, but have no such high CPU usage. See attached.

Actions
Copy link

Also available in: Atom PDF