There were error(s) loading the rules: /tmp/rules.debug:35

nasheayahu

Just wondering if this should be a concern and is there anything I can do to correct it from happening again?

There were error(s) loading the rules: /tmp/rules.debug:35: cannot define table pfB_BlockListDE_v4: Cannot allocate memory - The line in question reads [35]: table <pfB_BlockListDE_v4> persist file "/var/db/aliastables/pfB_BlockListDE_v4.txt"
@ 2022-07-04 14:18:46

System Information:
BIOS Vendor: AMI
Version: F.46
Release Date: Tue Aug 3 2021
Version 2.6.0-RELEASE (amd64)
built on Mon Jan 31 19:57:53 UTC 2022
FreeBSD 12.3-STABLE

The system is on the latest version.
Version information updated at Mon Jul 4 13:21:52 MDT 2022

CPU Type Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz
4 CPUs: 1 package(s) x 4 core(s)
AES-NI CPU Crypto: Yes (active)
QAT Crypto: No

Hardware crypto AES-CBC,AES-CCM,AES-GCM,AES-ICM,AES-XTS
Kernel PTI Enabled
MDS Mitigation Inactive
Uptime 12 Days 22 Hours 13 Minutes 32 Seconds

Memory usage (Currently)
12% of 32403 MiB

This post is deleted!

bmeeks

This memory warning is not for conventional RAM that you see on the Dashboard stats. This is referring to special reserved memory for pf firewall table entries. There is a setting you can adjust under the SYSTEM > ADVANCED menu for maximum table entries.

nasheayahu

@bmeeks said in There were error(s) loading the rules: /tmp/rules.debug:35:

This is referring to special reserved memory for pf firewall table entries. There is a setting you can adjust under the SYSTEM > ADVANCED menu for maximum table entries.

Awh yes, its been a while since I adjusted that from another build. Thanks!...

SteveITS

@nasheayahu If it helps (you or others) I have a note from several years ago to, when installing pfBlocker, double the default Firewall Maximum Table Entries (with a minimum of 2 million).

Note however there is (or was, don't have 22.05 yet) a bug where the sentence "On this system the default size is" shows the current setting, whatever it's set to.

This post is deleted!