2.1-BETA0 -> 2.1-BETA1 unbound won't install

[ktims]

Upgraded to the latest snapshot last night (2012-02-13 i386) and my DNS broke; apparently the unbound package isn't compatible with this version and didn't install after the upgrade, nor does it show in the available package listing. I assume due to '<maximum_version>2.1</maximum_version>'?

I'm not sure how to force it to install for testing, but I don't see why it shouldn't work like it did in the previous snapshot. Is this intentional?

[wagonza]

Try now. I have backed Unbound out from 2.1 and removed the maximum version restriction. So you should be good to go.

[mromero]

As an Unbound devotee from the old pfSense 2.01 days I immediately installed the package on latest pfSense 2.1 Snapshot 64 and could not get it to start. Reinstalled Squid 3 and still no luck.

:(

Anyone has it up and running?

[athurdent]

I upgraded to the lastest NanoBSD snapshot (Thu Feb 14 16:27:42 EST 2013) to install Unbound. The Unbound package installs fine, but it does not seem to be installing any binaries, so unbound cannot work.

[2.1-BETA1][root@pfsense-alix.local-lan]/root(4): find / | grep unbound_control
[2.1-BETA1][root@pfsense-alix.local-lan]/root(5):

Edit: If I get this right, it looks at http://files.pfsense.org/packages/8/All/ for unbound-1.4.19.tbz which is not there. But I don't get any error saying that it can't be found…

[jimp]

2.1 doesn't use .tbz packages, it uses .pbi packages.

Either way, the new version is uploaded now (tbz's for 2.0.x and pbi for 2.1)

[athurdent]

Thanks, now the binaries are there. It still won't work, though. It runs with

unbound -c /usr/pbi/unbound-i386/etc/unbound/unbound.conf

but the actual config seems to reside here

/usr/local/etc/unbound/unbound.conf

That config would not work either, I guess:

# unbound-checkconf /usr/local/etc/unbound/unbound.conf
/usr/local/etc/unbound/unbound_server.key: No such file or directory
[1360946053] unbound-checkconf[26439:0] fatal error: server-key-file: "/usr/local/etc/unbound/unbound_server.key" does not exist

which is here:

/usr/pbi/unbound-i386/etc/unbound/unbound_server.key

[jimp]

Added a note to http://redmine.pfsense.org/issues/2817 for that. Will need fixes/changes to account for that by the maintainer.

[mromero]

Is the Unbound package fixed now so we can go in and try and install on 2.1 PfSense 64?

[jimp]

I haven't seen any commits to it, and the ticket hasn't been updated, so I'd say probably not.

[mromero]

It says 100% done.

Does this mean Unbound on 2.1 is fixed?

[jimp]

That was referring to moving it to a package (out of the GUI)

The package part still needs fixed. The maintainer knows, he'll get to it when he has time.

[A Former User]

We have been using unbound for Quite some time. (pretty much the day
unbound support started to appear on pfsense)

all of our production pfsense boxes with Beta1 (and beta0) on them work fine PROVIDED
your willing to use google and unbounds website to figure out the errors and
how to fix them UNTIL the maintainer can fix it.

been doing it for quite some time now and know my way around unbound and pfsense.
(FreeBSD runs all of our Production Servers)

i do the mods in the lab first and do my testing before rolling out changes to ALL of our
pfsense boxes and thats after 30 days of testing hard in the lab.

[jcyr]

Do you actually fix the unbound source code, or do you just move files around so that unbound can actually find them?

[mromero]

SunCatalyst

Can you share the instructions on how to fix Unbound to work on pfSense 2.1 Beta 64?

Is there a patched package you can upload somewhere?

[A Former User]

i dont have any packages to share to fix things NOR would i want to step on the maintainers Toes. (wagonza)
im sure he will get to it Soon.

things like the key missing or a file missing , you have to be able to poke around to see what the
fix is. sometimes its as simple as symbolic linking  a file thats in the wrong place to the correct place
or grabbing unbound from FreeBSD's server itself and pull it apart to find the files you need.

ive spent Numerous hours reading and figuring out unbound.

Good Luck.

[jcyr]

On a i386 system the following seems to get unbound working after the package install:

At the console:

ln -s /usr/pbi/unbound-i386/etc/unbound/unbound.conf /usr/local/etc/unbound/unbound.conf
ln -s /usr/pbi/unbound-i386/etc/unbound/unbound_server.key /usr/local/etc/unbound/unbound_server.key
ln -s /usr/pbi/unbound-i386/etc/unbound/unbound_server.pem /usr/local/etc/unbound/unbound_server.pem
ln -s /usr/pbi/unbound-i386/etc/unbound/unbound_control.key /usr/local/etc/unbound/unbound_control.key
ln -s /usr/pbi/unbound-i386/etc/unbound/unbound_control.pem /usr/local/etc/unbound/unbound_control.pem
Something similar should do for the x64 version.

[survive]

Hi guys,

I got unbound installed and it works great…...for about an hour.

This is the same thing it was doing the last time I tried it about a year ago.

-Will

[n1ko]

@survive:

Hi guys,

I got unbound installed and it works great…...for about an hour.

This is the same thing it was doing the last time I tried it about a year ago.

-Will

Could you be anymore vague about so that we couldn't help you at all?

But anyways, I'm running Unbound just fine on the 18.3 snapshot, x64 etc. Of course had to do the links by hand but otherwise works as it should.

[survive]

Hi n1ko,

I'd be less vague if I could. About all I can tell you is that unbound seems to work just great for about an hour and then all my DNS resolution stops working. Disable unbound, re-enable the dns forwarder & I'm back in business.

I would expect that it's related to this:

http://forum.pfsense.org/index.php/topic,43044.msg234009.html#msg234009

as this is the exact same behavior I saw in January 2012.

-Will

[mromero]

Unbound package seems to be broken for the past couple months.

Is it abandoned by the developer?

Should it be deleted from the 2.1 pfSense Packages?