Bug #12706
closed
pfBlockerNG and unbound does not work after switching /var to RAM disk
0%
Description
How to reproduce:
1) Install pfBlockerNG-devel, and configure DNSBL in python mode
2) Enable RAM disk for /var
3) After reboot, all files associated with pfblockerng are deleted:
/var/unbound/pfb_unbound.py
/var/unbound/pfb_unbound_include.inc
/var/unbound/pfb_py_hsts.txt
4) ...and unbound doesn't start:
unbound[30865]: [30865:0] notice: init module 0: python unbound[30865]: [30865:0] error: pythonmod: can't open file pfb_unbound.py for reading unbound[30865]: [30865:0] error: module init for module python failed unbound[30865]: [30865:0] fatal error: failed to setup modules
Workaround - reinstall pfBlockerNG-devel
Updated by Viktor Gurov almost 3 years ago
Updated by Loh Phat over 2 years ago
This bug causes a delay in boot processing when the ramdisk option is enabled. If the option is disabled, no delay in startup. Interestingly this bug still causes the delay even if pfB-devel is disabled.
See: https://forum.netgate.com/topic/170308/long-boots-after-22-01-update-on-sg-3100-with-pfblockerng
Updated by Viktor Gurov over 2 years ago
- Status changed from New to Feedback
- Assignee set to Viktor Gurov
Updated by Jordan G over 2 years ago
unable to recreate in the current dev build 22.09.a.20220722.0600
Updated by Danilo Zrenjanin over 2 years ago
- Status changed from Feedback to Resolved
Tested:
2.7.0-DEVELOPMENT (amd64) built on Fri Jul 29 06:15:24 UTC 2022 FreeBSD 12.3-STABLE
pfBlockerNG-devel
3.1.0_4
The mentioned files were in the /var/unbound after reboot. And Unbound started successfully.
I am marking this ticket resolved.