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

Unable to check for updates, pkg-static: wrong architecture

Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
24 Posts 7 Posters 9.2k Views
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.
  • H
    Honest_Matt
    last edited by Honest_Matt Oct 25, 2022, 8:20 AM Oct 25, 2022, 8:19 AM

    I had a similar issue yesterday on CE 2.6.0. I switched the update branch from Current to Devel, then back to Current (nothing installed, just changed the dropdown to devel and back). After which I couldn't then check for updates on any branch other than Devel.

    Updating through the console also gives this error message:

    pkg-static: wrong architecture: FreeBSD:12:amd64 instead of FreeBSD:14:amd64
    pkg-static: repository pfSense contains packages with wrong ABI: FreeBSD:12:amd64
    

    After a bit of digging, it appears that the file:

    /usr/local/share/pfSense/pkg/repos/pfSense-repo.abi
    

    Has switched from FreeBSD:12:amd64 to FreeBSD:14:amd64, when I selected the Devel branch, but not switched back when I select the Current branch.

    My solution was to manually edit the file and change it back to FreeBSD:12:amd64 (after backing up the file of course :) )

    Seems reproduceable on my system by changing the branch to devel again, and being unable to check for updates until re-editing the abi file.

    Hope this helps.

    S V 2 Replies Last reply Oct 25, 2022, 2:18 PM Reply Quote 5
    • S
      SteveITS Galactic Empire @Honest_Matt
      last edited by Oct 25, 2022, 2:18 PM

      @honest_matt Interesting. Just the other day I had done that (as directed in posts by Netgate) on a 3100 to clear an upgrade check error. Maybe an issue only in 2.6? Or new in the last few days? I tried on a 2.6 and reproduced it. I opened a Redmine issue. I'll tag @stephenw10 as well.

      Apologies to @Patch, having just done that on the 3100 I knew it was supposed to work.

      Pre-2.7.2/23.09: 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 restart, or more depending on packages and device speed.
      Upvote 👍 helpful posts!

      1 Reply Last reply Reply Quote 1
      • P Patch referenced this topic on Nov 1, 2022, 9:51 PM
      • P Patch referenced this topic on Nov 1, 2022, 9:51 PM
      • V
        Vortexmind @Honest_Matt
        last edited by Nov 6, 2022, 5:10 PM

        @honest_matt said in Unable to check for updates, pkg-static: wrong architecture:

        My solution was to manually edit the file and change it back to FreeBSD:12:amd64 (after backing up the file of course :) )

        Thanks! Had the same issue and this worked perfectly!

        P 1 Reply Last reply Nov 11, 2022, 6:59 AM Reply Quote 1
        • P Patch referenced this topic on Nov 10, 2022, 9:39 PM
        • P Patch referenced this topic on Nov 10, 2022, 9:39 PM
        • P Patch referenced this topic on Nov 10, 2022, 9:40 PM
        • P Patch referenced this topic on Nov 10, 2022, 9:40 PM
        • P
          Patch @Vortexmind
          last edited by Nov 11, 2022, 6:59 AM

          It is working now for me, which I assume is due to updates in the repro as reported in redmine
          I did have to change the branch and save it a couple of times before it started working again. I'm not really sure exactly what was critical however it works now.

          1 Reply Last reply Reply Quote 0
          • S
            stephenw10 Netgate Administrator
            last edited by Nov 11, 2022, 6:57 PM

            Yes, that issue is fixed in CE and Plus now.

            If you had already hit it then switching to Dev again and then bakc to stable should correct it.
            The system logs should show it pulling the updated repo pkg and then downgrading back to the 2.6/22.05 pkg.

            Steve

            S 1 Reply Last reply Jan 29, 2023, 11:40 AM Reply Quote 0
            • S
              Sergei_Shablovsky @stephenw10
              last edited by Sergei_Shablovsky Jan 29, 2023, 12:24 PM Jan 29, 2023, 11:40 AM

              @stephenw10 said in Unable to check for updates, pkg-static: wrong architecture:

              Yes, that issue is fixed in CE and Plus now.

              If you had already hit it then switching to Dev again and then bakc to stable should correct it.
              The system logs should show it pulling the updated repo pkg and then downgrading back to the 2.6/22.05 pkg.

              Steve

              Recently I have the same issue on one of FW (Dev 2.7.0) after trying to update by 13) Update from console item from menu:

              73E4A4E1-A68B-4778-BB85-54867D09A4A4.jpeg

              Also when I choose Branch: “Development ...” version in System / Update menus in WebGUI, there are “Unable to check updates” in Retrieving.

              Please help to resolve... Tnx!

              —
              CLOSE SKY FOR UKRAINE https://youtu.be/_tU1i8VAdCo !
              Help Ukraine to resist, save civilians people’s lives !
              (Take an active part in public protests, push on Your country’s politics, congressmans, mass media, leaders of opinion.)

              1 Reply Last reply Reply Quote 0
              • S
                stephenw10 Netgate Administrator
                last edited by Jan 29, 2023, 3:46 PM

                Had you switched the update branch back to 2.6?

                What 2.7 snapshot is that running?

                S 2 Replies Last reply Jan 31, 2023, 11:29 AM Reply Quote 0
                • S
                  Sergei_Shablovsky @stephenw10
                  last edited by Jan 31, 2023, 11:29 AM

                  @stephenw10 said in Unable to check for updates, pkg-static: wrong architecture:

                  Had you switched the update branch back to 2.6?

                  No, just stay on 2.7.0-DEVELOPMENT

                  —
                  CLOSE SKY FOR UKRAINE https://youtu.be/_tU1i8VAdCo !
                  Help Ukraine to resist, save civilians people’s lives !
                  (Take an active part in public protests, push on Your country’s politics, congressmans, mass media, leaders of opinion.)

                  1 Reply Last reply Reply Quote 0
                  • S
                    Sergei_Shablovsky @stephenw10
                    last edited by Jan 31, 2023, 11:34 AM

                    @stephenw10 said in Unable to check for updates, pkg-static: wrong architecture:

                    What 2.7 snapshot is that running?

                    2.7.0-DEVELOPMENT (amd64)
                    built on Fri Aug 12 00:02:48 UTC 2022
                    FreeBSD 12.3-STABLE

                    —
                    CLOSE SKY FOR UKRAINE https://youtu.be/_tU1i8VAdCo !
                    Help Ukraine to resist, save civilians people’s lives !
                    (Take an active part in public protests, push on Your country’s politics, congressmans, mass media, leaders of opinion.)

                    S 1 Reply Last reply Jan 31, 2023, 1:18 PM Reply Quote 0
                    • S
                      SteveITS Galactic Empire @Sergei_Shablovsky
                      last edited by Jan 31, 2023, 1:18 PM

                      @sergei_shablovsky FreeBSD 12 is before they changed to 14. Have a read through https://www.netgate.com/blog/ce-snapshots-on-php-8.1-and-freebsd-main

                      Pre-2.7.2/23.09: 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 restart, or more depending on packages and device speed.
                      Upvote 👍 helpful posts!

                      1 Reply Last reply Reply Quote 1
                      • S
                        stephenw10 Netgate Administrator
                        last edited by Jan 31, 2023, 1:33 PM

                        Yup, that^

                        You will need to run those commands to come from a FreeBSD 12 based snapshot. Though that snap is so old I would probably just reinstall it and restore the config.

                        Steve

                        S 2 Replies Last reply Jan 31, 2023, 2:10 PM Reply Quote 1
                        • S
                          Sergei_Shablovsky @stephenw10
                          last edited by Jan 31, 2023, 2:10 PM

                          @stephenw10 said in Unable to check for updates, pkg-static: wrong architecture:

                          Yup, that^

                          You will need to run those commands to come from a FreeBSD 12 based snapshot. Though that snap is so old I would probably just reinstall it and restore the config.

                          Thank You. Must be this is a fastest way... ;)

                          —
                          CLOSE SKY FOR UKRAINE https://youtu.be/_tU1i8VAdCo !
                          Help Ukraine to resist, save civilians people’s lives !
                          (Take an active part in public protests, push on Your country’s politics, congressmans, mass media, leaders of opinion.)

                          1 Reply Last reply Reply Quote 0
                          • S
                            Sergei_Shablovsky @stephenw10
                            last edited by Feb 1, 2023, 2:05 AM

                            @stephenw10 said in Unable to check for updates, pkg-static: wrong architecture:

                            Yup, that^

                            You will need to run those commands to come from a FreeBSD 12 based snapshot. Though that snap is so old I would probably just reinstall it and restore the config.

                            Steve

                            When installing this new pfSense from scratch on this particular device I found strange behavior:

                            • some NICs detected incorrectly (I mean name when entering to 2) Interface assigning in main menu);
                            • MACs of some NICs (not of all, but for 2 cards from totally 8, let’s note all cards are absolutely identical);

                            So totally missunderstanding why 6 NICs cards MACs are recognized correctly and even the same “igb” interface naming done by FreeBSD for that cards, and I see the same pair “igbN - MAC”.
                            But 2(two) - MACs CHANGED ! (I have a screenshot and a spreadsheet of previous FreeBSD13 based installation, and SURE that MACs was differ!)

                            Your opinion on that ?

                            P.S.
                            No any BIOS changes, nothing! The same server, same cards, all hardware untouched...

                            —
                            CLOSE SKY FOR UKRAINE https://youtu.be/_tU1i8VAdCo !
                            Help Ukraine to resist, save civilians people’s lives !
                            (Take an active part in public protests, push on Your country’s politics, congressmans, mass media, leaders of opinion.)

                            1 Reply Last reply Reply Quote 0
                            • S
                              stephenw10 Netgate Administrator
                              last edited by Feb 1, 2023, 1:05 PM

                              Is it a random MAC shown? Some drivers will generate one if they cannot read the NIC for whatever reason. That's mostly on USB NICs though I've never seen it on igb.

                              Steve

                              1 Reply Last reply Reply Quote 0
                              • First post
                                Last post
                              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                                This community forum collects and processes your personal information.
                                consent.not_received