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

    RESOLVED : "sudo pkg upgrade" error "libutil.so.10"

    Scheduled Pinned Locked Moved General pfSense Questions
    13 Posts 3 Posters 67 Views 2 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.
    • S Offline
      SwissSteph
      last edited by SwissSteph

      Hello everyone,

      Since upgrading to version 25xxx, I can no longer run the following command in SSH:

      sudo pkg upgrade

      Then I get this message:

      ld-elf.so.1: Shared object "libutil.so.10" not found, required by "pkg"

      How can I fix this problem? I didn't touch anything on my end when executing commands in SSH. I don't understand how it broke ‘all by itself’.

      Thank you for your he

      I started with two "no-name" pfsense, one for use at home and the other as a backup in case of problems (which can happen when you're new to pfsense).
      ... And now I'm living with a Netgate 8200
      ... And sorry for my bad English...

      patient0P 1 Reply Last reply Reply Quote 0
      • patient0P Online
        patient0 @SwissSteph
        last edited by

        @SwissSteph you'll find help in the pfSense Troubleshooting section of the documentation "Upgrade not Offered / Library Errors":

        https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#upgrade-not-offered-library-errors

        1 Reply Last reply Reply Quote 0
        • S Offline
          SwissSteph
          last edited by

          Patient0,

          Thank you for your reply. My English isn't great, and I'm afraid of messing everything up :-(

          Is this the order I need to place?

          pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade

          I started with two "no-name" pfsense, one for use at home and the other as a backup in case of problems (which can happen when you're new to pfsense).
          ... And now I'm living with a Netgate 8200
          ... And sorry for my bad English...

          S 1 Reply Last reply Reply Quote 0
          • S Offline
            SwissSteph @SwissSteph
            last edited by SwissSteph

            I issued this command

            sudo pkg-static clean -ay ; pkg-static install -fy pkg pfSense-repo pfSense-upgrade

            and

            sudo pkg-static install -fy pkg pfSense-repo pfSense-upgrade

            now :

            sudo pkg upgrade

            I have these errors

            [25.07.1-RELEASE][xxxxxx@pfsense.home.arpa]/home/xxxxxx: sudo 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!

            What do I need to do to fix everything?

            EDIT :

            sudo pkg-static upgrade

            same error

            I started with two "no-name" pfsense, one for use at home and the other as a backup in case of problems (which can happen when you're new to pfsense).
            ... And now I'm living with a Netgate 8200
            ... And sorry for my bad English...

            S 1 Reply Last reply Reply Quote 0
            • S Offline
              SwissSteph @SwissSteph
              last edited by

              After a complete restart, the command

              sudo pkg upgrade

              has finally returned to normal

              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 (1 candidates): 100%
Processing candidates (1 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.

              I started with two "no-name" pfsense, one for use at home and the other as a backup in case of problems (which can happen when you're new to pfsense).
              ... And now I'm living with a Netgate 8200
              ... And sorry for my bad English...

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

                You see that if at any time pfSense has seen a different repo branch and pulled in the version of pkg from that. But that isn't actually an issue because all the pkg functions in pfSense use pkg-static to avoid that.

                You could have simply run pkg-static upgrade initially.

                However seeing that implies the repo branch may be set incorrectly so you should always check that.

                S 1 Reply Last reply Reply Quote 0
                • S Offline
                  SwissSteph @stephenw10
                  last edited by

                  @stephenw10
                  Thank you for your message. I panicked for a moment, but luckily the commands I entered didn't break anything.

                  I remember once restarting my pfsense and it ‘found’ a beta version. But I never test betas, nor did I choose that type of branch. I think it was because of this ‘bug’ that the (bad) ‘pkg’ was installed. I hadn't noticed anything until today.

                  I think there may be a bug when pfsense, during boot, offers ‘alpha’ or ‘beta’ items even though I never selected that option...

                  Thanks again!

                  I started with two "no-name" pfsense, one for use at home and the other as a backup in case of problems (which can happen when you're new to pfsense).
                  ... And now I'm living with a Netgate 8200
                  ... And sorry for my bad English...

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

                    There was a backend error a few weeks ago that some users saw. You may have been one of them.

                    S 1 Reply Last reply Reply Quote 0
                    • S Offline
                      SwissSteph @stephenw10
                      last edited by

                      @stephenw10
                      Thank you for this information. So I'm not ‘crazy’ and my explanation makes logical sense.

                      It was really unlucky for me to have restarted my pfsense at that precise moment...

                      I started with two "no-name" pfsense, one for use at home and the other as a backup in case of problems (which can happen when you're new to pfsense).
                      ... And now I'm living with a Netgate 8200
                      ... And sorry for my bad English...

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

                        It wasn't the restarting it was just that at some point it saw the repo and pulled the updated pkg version.

                        I'm not sure in what context you are running pkg upgrade there but you should be using pkg-static to avoid exactly this issue.

                        S 1 Reply Last reply Reply Quote 0
                        • S Offline
                          SwissSteph @stephenw10
                          last edited by SwissSteph

                          @stephenw10

                          OK, thank you for explaining that it's not because of the restart.

                          For this script bad link sorry !

                          EDIT
                          The link I put in my document (Word document) is no longer valid. I don't understand!

                          EDIT 2
                          https://forum.netgate.com/topic/179402/pfblockerng-3-2-0_4/11
                          post from "Gertjan at 13 avr.2023 14:34

                          I started with two "no-name" pfsense, one for use at home and the other as a backup in case of problems (which can happen when you're new to pfsense).
                          ... And now I'm living with a Netgate 8200
                          ... And sorry for my bad English...

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

                            Ah OK. Yup that should use pkg-static. But I think that's Luke's script: https://forum.netgate.com/topic/137707/auto-update-check-checks-for-updates-to-base-system-packages-and-sends-email-alerts?_=1763568842688

                            And it looks like you're using an old version because the current version does use pkg-static.

                            S 1 Reply Last reply Reply Quote 0
                            • S Offline
                              SwissSteph @stephenw10
                              last edited by

                              @stephenw10
                              Oh, great! Thank you for that correction (I didn't know that). I'll replace my script with the one you gave me. Thank you so much!

                              I started with two "no-name" pfsense, one for use at home and the other as a backup in case of problems (which can happen when you're new to pfsense).
                              ... And now I'm living with a Netgate 8200
                              ... And sorry for my bad English...

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