Unbound resolver error: Can't assign requested address for 127.0.0.1

[Grimson]

What other packages are you using? Bind will conflict with unbound and if you use Service Watchdog make sure it does not monitor unbound.

[RonpfS]

This post is deleted!

[RonpfS]

Well ... I have no more clue why it doesn't reload unbound.
Maybe disable all feeds excepts Ads ?

What does ls -al /var/unbound look like now ?

[themadsalvi]

@RonpfS I placed the result of the rebuilt key and pem files, as well as how /var/unbound looks in my last post(out on lunch and on mobile, sorry)

@Grimson the one thing I find odd is it just started this over the weekend, after a power outage. It has been fine for the last 6 months, without any issue. I do not have bind,and have made sure that unbound is not being monitored by service watchdog. I have the regularly installed packages like pfblockerng-devel, snort, etc.

[Grimson]

@themadsalvi said in Unbound resolver error: Can't assign requested address for 127.0.0.1:

@Grimson the one thing I find odd is it just started this over the weekend, after a power outage.

So did you run fsck on the filesystem? https://docs.netgate.com/pfsense/en/latest/hardware/troubleshooting-disk-check-errors-fsck.html#manually-run-fsck

I have the regularly installed packages like pfblockerng-devel, snort, etc.

There are no regularly installed packages, a regular install comes without additional packages. So always mention the packages you are using when asking for help.

If following the above to check the filesystem doesn't work grab a config backup and do a fresh install to make sure the installation is in a good state.

[themadsalvi]

@Grimson iplaced some screenshots from my mobile in my previouspost. Fsck says that /dev/zroot/ROOT cannot be opened since there is no file or directory present

[Grimson]

@themadsalvi said in Unbound resolver error: Can't assign requested address for 127.0.0.1:

@Grimson iplaced some screenshots from my mobile in my previouspost. Fsck says that /dev/zroot/ROOT cannot be opened since there is no file or directory present

https://www.freebsd.org/doc/handbook/zfs-zpool.html#zfs-zpool-status
https://www.freebsd.org/doc/handbook/zfs-zpool.html#zfs-zpool-scrub

[themadsalvi]

@Grimson

It looks like it found no errors in the pool. I even ran the scrub with no errors found.

[Grimson]

To be honest, from what I can see your installation is a mess. For example you have both snort and suricata installed. Best suggestion is for you to document what you are currently using (and what not). Then start with a fresh clean install, don't restore the config do the setup bit by bit yourself and watch where it breaks.

[themadsalvi]

@Grimson I will have to do that when I get home. I guess I have been lucky in that it has worked flawlessly for the last 6 months(SInce I installed it). It was bound to break eventually. Strangely, I can still surf the internet fine(I am writing from the network that has Pfsense firewall), and use streaming services like netflix.

[RonpfS]

You can always try to remove pfblocker lists by unticking pfBlockerNG & Keep Settings :

Note: To clear all downloaded lists, uncheck these two checkboxes and 'Save'. Re-check both boxes and run a 'Force Update|Reload'

[themadsalvi]

@RonpfS Uninstall, and then installed. This happened

[Gertjan]

Saw this :

[ Windows_hosts_block ]		 Downloading update [ 03/26/19 12:04:08 ] .. 404 Not Found

Possible to remove that feed ?
(or am I to late already ?)

[RonpfS]

@themadsalvi So that is the output of a Force Update after Disabling pfblockerng and Save settings,
Now when you tick both setttings, do a Force Update, then a Force Reload all.

[RonpfS]

@Gertjan said in Unbound resolver error: Can't assign requested address for 127.0.0.1:

Possible to remove that feed ?

Well the feed would be empty and would not prevent rebuilding the pfb_dnsbl.conf

[themadsalvi]

@Gertjan I have started from zero on the pfblocker to try and rule that out.

@RonpfS That is the output of fully removing and re-installing pfblocker, with the keep settings unticked.

[RonpfS]

@themadsalvi said in Unbound resolver error: Can't assign requested address for 127.0.0.1:

@RonpfS That is the output of fully removing and re-installing pfblocker, with the keep settings unticked.

Well let us know what happens when you add a DNSBL table.

[themadsalvi]

@RonpfS If I do a force update and force reload with a list or two it does the following:

UPDATE PROCESS START [ 03/26/19 14:48:53 ]

===[ DNSBL Process ]================================================

[ 1 ] Downloading update .. 200 OK
No Domains Found

[ shalla ] Downloading update [ 03/26/19 14:49:03 ] .. 200 OK.

Orig. Unique # Dups # White # Alexa Final

19567 19567 0 0 0 19567

DNSBL: Flush DNSBL_IP

Assembling database... completed
Validating database... Skipped
Reloading Unbound... Failed to Reload... Restoring previous database.... Not completed.

*** DNSBL update [ 0 ] [ 19567 ] ... OUT OF SYNC ! ***

===[ Continent Process ]============================================

===[ Aliastables / Rules ]==========================================

No changes to Firewall rules, skipping Filter Reload
No Changes to Aliases, Skipping pfctl Update

===[ FINAL Processing ]=====================================

[ Original IP count ] [ 0 ]

===[ DNSBL Domain/IP Counts ] ===================================

19567 /var/db/pfblockerng/dnsbl/shalla.txt

IPv4 alias tables IP count

1

IPv6 alias tables IP count

0

Alias table IP Counts

   1 /var/db/aliastables/pfB_DNSBLIP.txt

pfSense Table Stats

table-entries hard limit 400000
Table Usage Count 109283

UPDATE PROCESS ENDED [ 03/26/19 14:49:07 ]

[themadsalvi]

@RonpfS @Gertjan @Grimson thank you, and everyone for helping out. I ended up having to re-install pfsense again. I was able to find a config backup that worked, and allowed for unbound resolver to reload correctly. Unbound and DNS resolver is working correctly now. Thank you all so much!

[themadsalvi]

@RonpfS @Gertjan @Grimson well, it looks like this issue has popped its ugly head once more. This was after a full re-install and upgrade to the newest version of pfsense and pfblockerng-devel. Same error as the one at the top of this topic.

---

Assembling DNSBL database... completed [ 06/14/19 21:09:52 ]
Reloading Unbound Resolver..
DNSBL enabled FAIL - restoring Unbound conf *** Fix error(s) and a Force Reload required! ***
[1560571794] unbound-control[99463:0] error: connect: Can't assign requested address for 127.0.0.1 port 953.... Not completed. [ 06/14/19 21:09:54 ]

*** DNSBL update [ 0 ] [ 1509069 ] ... OUT OF SYNC ! ***