Project

General

Profile

Actions

Bug #12706

open

pfBlockerNG and unbound does not work after switching /var to RAM disk

Added by Viktor Gurov 4 months ago. Updated about 2 months ago.

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

0%

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

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

see also https://redmine.pfsense.org/issues/12274

Actions #2

Updated by Darin May 3 months 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

Actions #3

Updated by Viktor Gurov about 2 months ago

  • Status changed from New to Feedback
  • Assignee set to Viktor Gurov
Actions

Also available in: Atom PDF