21.02-RELEASE - unable to force unbound upgrade to 1.13.1
-
Hey folks, it looks like the package manager for pf+ hasn't been modified to unbound 1.13.1 but the CE has.
Wondering if there's any process that's currently in place to get it in or not. Right now, it's crashing about once per minute and we're having to restart it with watchdog.
pkg upgrade -f unbound
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):Installed packages to be REINSTALLED:
unbound-1.13.0_2 [pfSense]Related Reddit: https://www.reddit.com/r/PFSENSE/comments/lpzq14/since_upgrading_to_pfsense_v25_unbound_has/
-
That's known at the moment, we'll have it up soon.
-
Looks like you can force the upgrade now.
pkg upgrade -f unbound Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: unbound: 1.13.0_2 -> 1.13.1 [pfSense] Number of packages to be upgraded: 1 1 MiB to be downloaded. Proceed with this action? [y/N]: y [1/1] Fetching unbound-1.13.1.txz: 100% 1 MiB 513.1kB/s 00:02 Checking integrity... done (0 conflicting) [1/1] Upgrading unbound from 1.13.0_2 to 1.13.1... ===> Creating groups. Using existing group 'unbound'. ===> Creating users Using existing user 'unbound'. [1/1] Extracting unbound-1.13.1: 100% -
@defunct78 confirmed!
The 21.02_1 patch contains 1.13.1 as well.
-
If I manually update unbound, what will happen later when there is an official pfSense patch that contains further updates to unbound? Will I somehow need to tell the system to revert to the original track or will that happen by itself?
-
@astronaut If you manually apply the unbound update, it will reach out to the repository and grab the update package for unbound but nothing else. At this time, the repo has been updated to 21.02-RELEASE-p1, which includes the unbound update. I'd recommend simply running the normal update process to ensure you're on all the latest packages.
-
@astronaut said in 21.02-RELEASE - unable to force unbound upgrade to 1.13.1:
If I manually update unbound, what will happen later when there is an official pfSense patch that contains further updates to unbound?
If there is another update for unbound it would have a higher version number and be seen as an update.
Will I somehow need to tell the system to revert to the original track or will that happen by itself?
No need to do anything special.
@smokeyrd said in 21.02-RELEASE - unable to force unbound upgrade to 1.13.1:
@astronaut If you manually apply the unbound update, it will reach out to the repository and grab the update package for unbound but nothing else. At this time, the repo has been updated to 21.02-RELEASE-p1, which includes the unbound update. I'd recommend simply running the normal update process to ensure you're on all the latest packages.
21.02-p1 did not include the newer version of unbound, but it was put into the repository just after the release. If you install from a 21.02-p1 image it won't have the newer unbound, but if you were to upgrade, you'd pick it up along the way since it's in the package repository.
-
Yeah I got 1.13.1 via just doing pkg upgrade from cmd prompt after they put it in the 21.02 repository..
[21.02-RELEASE][admin@sg4860.local.lan]/root: unbound-control -c /var/unbound/unbound.conf status version: 1.13.1 verbosity: 1 threads: 4 modules: 2 [ validator iterator ] uptime: 87420 seconds options: control(ssl) unbound (pid 7616) is running... [21.02-RELEASE][admin@sg4860.local.lan]/root: -
@jimp This is why we love you. Thanks for your insight and guidance!