New version of unbound; can’t update with “pkg upgrade”
-
I use the script pkg_check.php by @luckman212 to notify me via email of any updates to pfSense, patches, etc. Recently I have been getting these notifications:
Notifications in this message: 1 ================================ 07:00:35 Some packages are part of the base system and will not show up in Package Manager. If any such updates are listed below, run `pkg upgrade` from the shell to install them: unbound: 1.23.0 -> 1.24.1 [pfSense]The problem is that when I try to run
pkg upgradefrom the shell, I get this error:[25.07.1-RELEASE][admin@********]/root: pkg upgrade ld-elf.so.1: Shared object "libutil.so.10" not found, required by "pkg"How can I fix this?
-
@DominikHoffmann said in New version of unbound; can’t update with “pkg upgrade”:
Shared object "libutil.so.10" not found, required by "pkg"
see this thread
https://forum.netgate.com/topic/198803/pkg-broken-in-25.07.1
-
@johnpoz said in New version of unbound; can’t update with “pkg upgrade”:
https://forum.netgate.com/topic/198803/pkg-broken-in-25.07.1
I am running the
pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgradecommand now. I am getting a lot of errors like this:
certctl: Skipping untrusted certificate 03179a64 (/etc/ssl/untrusted/03179a64.0) certctl: Skipping untrusted certificate 3e44d2f7 (/etc/ssl/untrusted/3e44d2f7.0) certctl: Skipping untrusted certificate 08063a00 (/etc/ssl/untrusted/08063a00.0)Is that of concern?
-
Okay! It got worse:
[25.07.1-RELEASE][admin@********]/root: pkg upgrade Updating pfSense-core repository catalogue... pkg: An error occured while fetching package pkg: An error occured while fetching package repository pfSense-core has no meta file, using default settings pkg: An error occured while fetching package pkg: An error occured while fetching package pkg: An error occured while fetching package pkg: An error occured while fetching package Unable to update repository pfSense-core Updating pfSense repository catalogue... pkg: An error occured while fetching package pkg: An error occured while fetching package repository pfSense has no meta file, using default settings pkg: An error occured while fetching package pkg: An error occured while fetching package pkg: An error occured while fetching package pkg: An error occured while fetching package Unable to update repository pfSense Error updating repositories! -
@DominikHoffmann said in New version of unbound; can’t update with “pkg upgrade”:
Is that of concern?
None.
For some reason it enumerates the certificats in the "untrusted" folder, and found them untrusted.
I saw the same thing a couple of days. It took a minute or so.@DominikHoffmann said in New version of unbound; can’t update with “pkg upgrade”:
pkg upgrade
....
Error updating repositories!I just got the same mail, as I'm using the same pkg_check.php script.
"pkg upgrade" worked just fine for me.
I restarted unbound in the GUI, and saw :
A temporary glitch ?
-
@Gertjan: My unbound did not get updated:
Nov 4 12:16:25 unbound 7563 [7563:0] info: start of service (unbound 1.23.0).That's the output of Status → System Logs → System → DNS Resolver. How did you generate the output that shows which version you’re running?
-
@Gertjan said in New version of unbound; can’t update with “pkg upgrade”:
I restarted unbound in the GUI, and saw :
5601816a-3a54-4fbe-a956-b7d7da092ac7-image.png
@DominikHoffmann said in New version of unbound; can’t update with “pkg upgrade”:
My unbound did not get updated:
Nov 4 12:16:25 unbound 7563 [7563:0] info: start of service (unbound 1.23.0).
That's the output of Status → System Logs → System → DNS Resolver. How did you generate the output that shows which version you’re running?
For the record, and on a CE box, I needed to fully reboot the system for Unbound to come up reporting the new version.
-
@tinfoilmatt said in New version of unbound; can’t update with “pkg upgrade”:
For the record, and on a CE box, I needed to fully reboot the system for Unbound to come up reporting the new version.
After a reboot, I was still running unbound 1.23.0, as evidenced by the unbound log file. However, this time
pkg upgradeworked flawlessly:[25.07.1-RELEASE][admin@********]/root: pkg upgrade 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. Checking for upgrades (2 candidates): 100% Processing candidates (2 candidates): 100% The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: unbound: 1.23.0 -> 1.24.1 [pfSense] Number of packages to be upgraded: 1 3 MiB to be downloaded. Proceed with this action? [y/N]: y [1/1] Fetching unbound-1.24.1.pkg: 100% 3 MiB 3.5MB/s 00:01 Checking integrity... done (0 conflicting) [1/1] Upgrading unbound from 1.23.0 to 1.24.1... ===> Creating groups Using existing group 'unbound' ===> Creating users Using existing user 'unbound' [1/1] Extracting unbound-1.24.1: 100%After a restart of unbound on the Status → Services page I see that I am running Version 1.24.1.
-
@DominikHoffmann No software, no matter how rock solid, will ever be fully immune from the good ol', tried-and-true 'have you rebooted', eh?

-
I mean.... you really shouldn't have to but...

-
@stephenw10 I was disappointed, too.