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

    pkg broken in 25.07.1?

    Scheduled Pinned Locked Moved General pfSense Questions
    16 Posts 4 Posters 6.4k Views 7 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.
    • dennypageD Offline
      dennypage @SteveITS
      last edited by

      @SteveITS said in pkg broken in 25.07.1?:

      May have been pulled yesterday by https://forum.netgate.com/topic/198787/what-is-it-25.11.a.20250916.0600/6 as that was logged on the router I used. I haven't tried running pkg though.

      Sure enough:

      <13>1 2025-09-16T10:23:23.770794-07:00 fw pkg-static 66477 - - pkg upgraded: 1.21.3_5 -> 2.2.2_2

      I didn't take any action to initiate that which makes me rather uncomfortable.

      S 1 Reply Last reply Reply Quote 0
      • S Offline
        SteveITS Galactic Empire @dennypage
        last edited by

        @dennypage You logged in ~1 minute before that. :) I think it's part of the dashboard update check.

        Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
        When upgrading, allow 10-15 minutes to reboot, or more depending on packages, CPU, and/or disk speed.
        Upvote 👍 helpful posts!

        dennypageD 1 Reply Last reply Reply Quote 0
        • dennypageD Offline
          dennypage @SteveITS
          last edited by

          @SteveITS said in pkg broken in 25.07.1?:

          You logged in ~1 minute before that. :) I think it's part of the dashboard update check.

          LOL, yes.

          However, any package / firmware changes need to require an explicit action to be taken by an administrator. Simply logging in definitely should never constitute such an action.

          S 1 Reply Last reply Reply Quote 0
          • S Offline
            SteveITS Galactic Empire @dennypage
            last edited by SteveITS

            @dennypage That's a valid question. In general, in the past the "current" branch would change versions over time and presumably the update was tied to checking the new version. So it's not new behavior AFAIK but I wonder if it's still necessary.

            FWIW this is also (seems) related to the "another instance is running" warning when logging in and immediately trying to update. On slower/ARM devices it can take a few minutes to update pkg and after that log entry appears the "other instance" is no longer running, in my experience.

            That said though, I checked my home router and it was 29 hours after the login so seems unrelated:

            Sep 15 11:28:06 	php-fpm 	23574 	/index.php: Successful login for user 'admin' from: _____ (Local Database) 
Sep 16 16:31:44 	pkg-static 	7428 	pkg upgraded: 1.21.3_5 -> 2.2.2_2

            I checked a 2100 where the last login was Sept 11 and it doesn't have pkg upgrading at all, until I logged in just now. Here's the delay for pkg there. Note the different version:

            Sep 17 15:51:51 	php-fpm 	93201 	/index.php: Successful login for user 'admin' from: _______ (Local Database) 
Sep 17 15:59:32 	pkg-static 	69005 	pkg upgraded: 1.21.3_4 -> 1.21.3_5

            Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
            When upgrading, allow 10-15 minutes to reboot, or more depending on packages, CPU, and/or disk speed.
            Upvote 👍 helpful posts!

            S 1 Reply Last reply Reply Quote 0
            • S Offline
              SteveITS Galactic Empire @SteveITS
              last edited by

              I made a redmine for the pkg update delay.

              Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
              When upgrading, allow 10-15 minutes to reboot, or more depending on packages, CPU, and/or disk speed.
              Upvote 👍 helpful posts!

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

                Hmm, yes pkg is upgraded by pfSense-upgrade during the check to be sure it can check for pkgs! 😉 But it can result in that ugly error. pkg-static should always work though as you found.

                1 Reply Last reply Reply Quote 0
                • S Offline
                  SteveITS Galactic Empire @SteveITS
                  last edited by

                  said in pkg broken in 25.07.1?:

                  I made a redmine for the pkg update delay.

                  Jim replied to it already, short version, it's already solved. "...in Plus 25.11 and CE 2.9.0 the certutil program has been rewritten in C upstream and now completes in <1 second even on 1100."

                  Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                  When upgrading, allow 10-15 minutes to reboot, or more depending on packages, CPU, and/or disk speed.
                  Upvote 👍 helpful posts!

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

                    Yup, it's waaaay faster!

                    1 Reply Last reply Reply Quote 0
                    • B barnettd referenced this topic on
                    • T Offline
                      tman222
                      last edited by

                      Sorry to bring up and older thread, but I ran into this issue (error) today as well as I was trying to update Unbound to 1.24.1:

                      https://redmine.pfsense.org/issues/16503

                      Following the instructions in the documentation linked to originally by @SteveITS fixed things by downgrading pkg back to 1.x:

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

                      I assume once 25.11 is released the upgrade check will upgrade pkg to 2.x again?

                      Thanks in advance.

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

                        You should always be able to run pkg commands by using pkg-static even if it gets updated. Was that not the case?

                        1 Reply Last reply Reply Quote 0
                        • johnpozJ johnpoz referenced this topic
                        • D DominikHoffmann referenced this topic
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.