BUG: unbound/ PfblockerNG when enabling RAM disk
Mr_JinX last edited by
There seems to be a bug, possibly. When i enable RAM disk for /var & /tmp i get the below error message after reload;
There were error(s) loading the rules: /tmp/rules.debug:29: cannot load "/var/db/aliastables/pfB_Asia_v4.txt": No such file or directory - The line in question reads : table <pfB_Asia_v4> persist file "/var/db/aliastables/pfB_Asia_v4.txt"
@ 2017-07-02 09:45:54
When i looked in the /var/unbound the "pfb_dnsbl.conf" file was missing (i assume this would have been moved to the RAM disk)
System PC Engines APU2
BIOS Vendor: coreboot
Release Date: 03/07/2016
Version 2.3.4-RELEASE (amd64)
built on Wed May 03 15:13:29 CDT 2017
All packages store data in /var. So when you reboot you will lose the all data stored in those folders.
php /usr/local/www/pfblockerng/pfblockerng.php dc
Then follow that with a Force reload.
brandonb last edited by
I had the same issue until I increased my RAM disk size. I think what happens is the file tries to write to the RAM disk but fails since it's out of space with the default size. The setting is found under System/Advanced/Miscellaneous. I increased mine to 512 MB's. Since I have 8 or 16 gigs of RAM and have plenty to spare.