Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    New version of unbound; can’t update with “pkg upgrade”

    Scheduled Pinned Locked Moved General pfSense Questions
    11 Posts 5 Posters 153 Views 6 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • johnpozJ Offline
      johnpoz LAYER 8 Global Moderator @DominikHoffmann
      last edited by

      @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

      An intelligent man is sometimes forced to be drunk to spend time with his fools
      If you get confused: Listen to the Music Play
      Please don't Chat/PM me for help, unless mod related
      SG-4860 25.07.1 | Lab VMs 2.8.1, 25.07.1

      D 1 Reply Last reply Reply Quote 1
      • D Offline
        DominikHoffmann @johnpoz
        last edited by

        @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-upgrade

        command 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?

        GertjanG 1 Reply Last reply Reply Quote 0
        • D Offline
          DominikHoffmann
          last edited by

          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!
          1 Reply Last reply Reply Quote 0
          • GertjanG Offline
            Gertjan @DominikHoffmann
            last edited by

            @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 :

            5601816a-3a54-4fbe-a956-b7d7da092ac7-image.png

            A temporary glitch ?

            No "help me" PM's please. Use the forum, the community will thank you.
            Edit : and where are the logs ??

            D tinfoilmattT 2 Replies Last reply Reply Quote 0
            • D Offline
              DominikHoffmann @Gertjan
              last edited by

              @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?

              1 Reply Last reply Reply Quote 0
              • tinfoilmattT Offline
                tinfoilmatt @Gertjan
                last edited by

                @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.

                D 1 Reply Last reply Reply Quote 0
                • D Offline
                  DominikHoffmann @tinfoilmatt
                  last edited by

                  @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 upgrade worked 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.

                  tinfoilmattT 1 Reply Last reply Reply Quote 2
                  • tinfoilmattT Offline
                    tinfoilmatt @DominikHoffmann
                    last edited by

                    @DominikHoffmann No software, no matter how rock solid, will ever be fully immune from the good ol', tried-and-true 'have you rebooted', eh? 😂

                    1 Reply Last reply Reply Quote 0
                    • stephenw10S Online
                      stephenw10 Netgate Administrator
                      last edited by

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

                      tinfoilmattT 1 Reply Last reply Reply Quote 0
                      • tinfoilmattT Offline
                        tinfoilmatt @stephenw10
                        last edited by

                        @stephenw10 I was disappointed, too.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.