There were error(s) loading the rules: /tmp/rules.debug:25: cannot define table
-
I've been using pfSense for about two months, and I encountered an error when trying to whitelist an IP address using pfBlocker.
The error message is as follows: "There were error(s) loading the rules: /tmp/rules.debug:25: cannot define table pfB_Asia_v4: Cannot allocate memory - The line in question reads [25]: table <pfB_Asia_v4> persist file "/var/db/aliastables/pfB_Asia_v4.txt" @ 2023-07-02 23:54:44."
I believe I have sufficient memory with 8GB, so I'm unsure of the cause. How can I resolve this issue?
-
@Yet_learningPFSense said in There were error(s) loading the rules: /tmp/rules.debug:25: cannot define table:
The error message is as follows: "There were error(s) loading the rules: /tmp/rules.debug:25: cannot define table pfB_Asia_v4: Cannot allocate memory - The line in question reads [25]: table <pfB_Asia_v4> persist file "/var/db/aliastables/pfB_Asia_v4.txt" @ 2023-07-02 23:54:44."
-
@rcoleman-netgate Thank you. Despite increasing the maximum values of the firewall states and restarting, the situation did not change. However, upon checking the package manager, it was discovered that upgrades were available. Accordingly, I upgraded the PFSense package, and after upgrading the package, the initial error no longer occurred. I was still unable to establish an OpenVPN connection at first, but with this method, I was able to successfully connect.
-
@Yet_learningPFSense Yes, running current and updated release is a smart move.
Same with your Firmware -- if there was an update for pfB there is probably also one for pfSense. What release are you running?
-
@rcoleman-netgate It was about two months ago that I set up PFSense myself, using version 2.6.0 of PFSense and installing pfBlocker about a month ago (I didn't note down the version). There might have been some issues due to the version mismatch.
-
@Yet_learningPFSense said in There were error(s) loading the rules: /tmp/rules.debug:25: cannot define table:
@rcoleman-netgate It was about two months ago that I set up PFSense myself, using version 2.6.0 of PFSense and installing pfBlocker about a month ago (I didn't note down the version). There might have been some issues due to the version mismatch.
I am currently using the latest version of PFSense, which is 2.7.0.