Upgrade 2.15 to 2.2 and Unbound custom options
-
Hello,
I did the upgrade on my Alix board yesterday. Everything went fine except for one package : unbound.I had indeed Unbound already installed as a standalone package, with custom options. Under pfsense 2.1.5, Unbound custom options had to be separated by semi-colons.
This is not the case anymore with 2.2 (well I guess this is only an Unbound related problem), as each options has to be on a newline.And it seems that the automatic upgrade didn't take care of this very well, so Unbound refused to start after the upgrade. As soon as you put the options in the correct format, everything is fine.
HTH.
Nicolas -
There is code that attempts to convert the old Unbound package advanced options on upgrade.
Can you post what was in advanced options before upgrade?
That will help the devs replicate the upgrade conversion problem - then it could be fixed for others upgrading in future. -
Yes, here are the options I was using:
num-threads: 2
msg-cache-slabs: 2
rrset-cache-slabs: 2
infra-cache-slabs: 2
key-cache-slabs: 2
outgoing-range: 450Nicolas
-
Did each of those option lines have a semi-colon at the end?
Do you know if there was any whitespace before or after the semi-colon?
Or any other unusual formatting that might need to be parsed out during an upgrade conversion? -
I'm not 100% sure, but so far I remember the options were setup like this:
num-threads: 2; msg-cache-slabs: 2; rrset-cache-slabs: 2; infra-cache-slabs: 2; key-cache-slabs: 2; outgoing-range: 450
Nicolas
-
From my limited experience with playing with custom options with 2.2 and the integrated unbound you have to add
server:
option
optionto get them to work, or unbound fails to start without that server: at first line.
