Unbound can't start after snapshot update (new thread!)
-
Hrmm odd if i add a v6 override, for example:
v6 google.com 2800:3f0:XXX:XXX::1014
And restart unbound it is fine.
Do me a favour please, log in via ssh and execute a unbound-checkconf - it should return "unbound-checkconf: no errors in /usr/local/etc/unbound/unbound.conf" -
Unbound gives me a no errors reply, just as you said it should. I'll try and enable my testing v6 forwards one by one to see if there is a specific scenario which causes unbound to stop working. Thanks for your help so far!
-
Unbound gives me a no errors reply, just as you said it should. I'll try and enable my testing v6 forwards one by one to see if there is a specific scenario which causes unbound to stop working. Thanks for your help so far!
Have you managed to test the v6 forwards?
-
Hello Wagonza,
Unbound still gives me errors in the log but works with the forwards.
Adding the forwards one by one and reloading unbound in the ssh-console has helped unbound start properly.Thanks for all your help!
-
Hello Wagonza,
Unbound still gives me errors in the log but works with the forwards.
Adding the forwards one by one and reloading unbound in the ssh-console has helped unbound start properly.Thanks for all your help!
What error did you see in the logs, the same timeout one? Can you do me a favour please and pm me the xml of the unbound section of your config.xml?
Thanks
-
The very same. I will send you the unbound section(s) of my config.xml.
Edit: Sent.
-
Thanks, got it - will go through it a little later and let you know.
-
Problem sorted with host over rides that have empty host values. So just reinstall the package. Otherwise any other problems, please open up a new thread.
-
Having set some v6 forwards yesterday, I can confirm that the new fixes work as expected.
Thanks a lot wagonza! -
wicked! Only v6 ACLs now left…
-
Sweet!! ipv6 ACLs are NEXT ;)
-
Finally committed support for IPv6 acls :P I have also updated the package to latest Unbound version 1.4.13. So give it a couple of hours while the package builder is building the new port.
-
Sweet! Can remove them from my custom options section, which is how I have been adding them now.
See it listed already, installing now
Looks like you forgot a _ in the allow_snoop
php: /unbound_acls.php: The command '/usr/local/sbin/unbound-control start' returned exit code '1', the output was '/usr/local/etc/unbound/unbound.conf:67: error: unknown keyword 'snoop' /usr/local/etc/unbound/unbound.conf:68: error: unknown keyword 'snoop' /usr/local/etc/unbound/unbound.conf:69: error: unknown keyword 'snoop' /usr/local/etc/unbound/unbound.conf:70: error: unknown keyword 'snoop' read /usr/local/etc/unbound/unbound.conf failed: 4 errors in configuration file [1317328224] unbound[30144:0] fatal error: Could not read config file: /usr/local/etc/unbound/unbound.conf'
So I have an ACL that allows snoop, but in the .conf file its put in as "allow snoop" which killed my unbound now it can not start. Trying to manually edit the ubound.conf now so I can get unbound to start.
-
Cool let me know if you get any problems.
-
just edited my last post – looks like a problem ;)
-
bah! and i did test that specifically. hang 5.
-
ok changed to allow vs allow snoop and looks good
from conf file
#allow
access-control: 192.168.1.0/24 allow
access-control: 10.0.200.0/24 allow
access-control: 127.0.0.0/8 allow
access-control: 2001:470:1f11:b85:0:0:0:0/64 allowchanged it to allow snoop in dropdown and get this.
access-control: 192.168.1.0/24 allow snoop
access-control: 10.0.200.0/24 allow snoop
access-control: 127.0.0.0/8 allow snoop
access-control: 2001:470:1f11:b85:0:0:0:0/64 allow snoopmissing the _ looks like to me.
-
Yeah 100% correct - fixed. So just update.
-
Sweet thanks!! Looks like same build number, just reinstall or will you be pushing say 1.4.13_01
-
Nah same build number - I didnt increase the version number for this change.
