Project

General

Profile

Actions

Bug #7455

closed

Unbound DNS Resolver failed with pfBlockerNG after reboot with /var mounted on ramfs

Added by giskard rt over 7 years ago. Updated about 4 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
pfBlockerNG
Target version:
-
Start date:
04/07/2017
Due date:
% Done:

0%

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

Description

I'd like to say, the var on ramfs is very useful, but the way to handle it is not well considered to back up the var on shutdown or reboot.

The problem I came across is that the DNS Resolver stops working and refuse to restart for pfBlockerNG's appended configuration file (/var/unbound/pfb_dnsbl.conf) is missing. This happens as I have pfBlockerNG configured with some ad-block seeds, after updated I have a reboot, the /var directory is mounted on ram but the related configuration file is not backed up. so once reboot, these files are missing. I have first to update pfblockerNG to generate the needed file and then restart dns resolver, or just change the dns resolver configuration not to include the missing file.

For this problem, I sugguest:
1, add an option for DNS resolver to ignore the unnecessary missing file so that it have some kind fault-tolerance.
2, reconsider the backup policy for /var directory when it's mounted on ram, and set a rule for the add-ons itself to consider this problem.

Actions #1

Updated by Kill Bill over 7 years ago

Duplicate of Bug #6603

Actions #2

Updated by Jim Pingle over 7 years ago

  • Status changed from New to Duplicate
Actions #3

Updated by Marc Dorando about 4 years ago

Similar issue over here, 2.4.5-RELEASE-p1 having LAN, VLAN and WAN1, WAN2 (LoadBalancing&Failover) and IPv4, IPv6 and pfb_dnsbl (stable) and snort (stable). Unbound was starting before 2.4.5 without any issues.

Actions

Also available in: Atom PDF