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

Gertjan

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

.... but succeeds when set to "DEVEL version (devel)"

That's the part where went down hill.
( It succeeded, so you upgraded some packages ? (from the 22.11 or 2.7.0 devel tree ?)
As pfSense has now loaded the file that points to the access to 'devel' or 22.11 (upcoming 2.7.0) it thinks it 2.6.0 .... or 2.7.0.

What does
/usr/local/share/pfSense/pkg/repos/pfSense-repo.conf

FreeBSD: { enabled: no }

pfSense-core: {
  url: "pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-core",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/local/share/pfSense/keys/pkg",
  enabled: yes
}

pfSense: {
  url: "pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-pfSense_plus_v22_05",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/local/share/pfSense/keys/pkg",
  enabled: yes
}

contain ?

Btw : mine points to a 22.05 pkg files.
You should be able to recognize the "2.6.0" version.
Probably something like :
"pkg+https://firmware.netgate.com/pkg/pfSense_2_6_0_amd64-core"
and
"pkg+https://firmware.netgate.com/pkg/pfSense_2_6_0_amd64-pfSense_2_6_0"

/usr/local/etc/pkg/repos/pfSense.conf (ln) is a pointer to this file.

Patch

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

That's the part where went down hill.
( It succeeded, so you upgraded some packages ? (from the 22.11 or 2.7.0 devel tree ?)

No. I had

System -> Update set to "Latest stable (v2.6.0)"
Then I updated: System -> Package manager -> updated pfBlockerNG-dev v3.1.0_4 to v3.1.0_6 and System_Patches v2.0_6 to v2.0_7
After which check for update fails when branch is set to " Latest stable version (v2.6.0)"

As part of the debug process I then tried

System -> Update set "PREVIOUS version (v2.5.2)" which also gave the error "Unable to check for updates", as it did when I reset it to "Latest stable (v2.6.0)" but succeeds when set to "DEVEL version (devel)"
Other debug steps as listed in the prior posts.

My interpretation is pfBlockerNG-dev v3.1.0_6 or System_Patches v2.0_7 is part of pfsense v2.7 and is incompatible with pfsense v2.6. Then uninstalling these packages did not reverse the changes made when updating the package.

In which case the error is the package upgrade should not have been offered in pfsense v2.6

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

/usr/local/etc/pkg/repos/pfSense.conf

That file contains

FreeBSD: { enabled: no }

pfSense-core: {
  url: "pkg+https://pkg.pfsense.org/pfSense_v2_6_0_amd64-core",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/local/share/pfSense/keys/pkg",
  enabled: yes
}

pfSense: {
  url: "pkg+https://pkg.pfsense.org/pfSense_v2_6_0_amd64-pfSense_v2_6_0",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/local/share/pfSense/keys/pkg",
  enabled: yes
}

SteveITS

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

My interpretation is pfBlockerNG-dev v3.1.0_6 or System_Patches v2.0_7 is part of pfsense v2.7 and is incompatible with pfsense v2.6

The packages offered are tied to the update branch that is set. So for instance if someone:

has branch set to the default of Current
a new version of pfSense is released
installs or updates packages

or

has branch set to Devel
did not upgrade pfSense to Devel
installs or updates packages

Then the installed code is for the not-yet-installed pfSense. That can cause problems for instance if the package is marked as needing a newer PHP as a dependency, it will try to upgrade PHP.

However if pfSense is the current version and that branch is selected, packages won't break pfSense.

I don't have a great answer for you but the shortest path to "working" might be to reinstall pfSense and restore the config from backup.

Patch

I assume the issue is pfBlockerNG-dev v3.1.0_6 has been updated to be compatible with pfsense v2.7 in particular freebsd v14, making it not compatible with pfsense v2.6 and freebsd v12

Reinstalling pfsense would enable update checking in pfsense but still not allow installing pfBlockerNG-dev as the wrong version would install.

SteveITS

@patch That's actually not how it works. It's only a problem if someone installs a package not for their version. So, one of the two scenarios I posted, where there is a mismatch between what is selected and what is installed. I wish there was a warning about that but not yet.

https://redmine.pfsense.org/issues/10464 - background, not saying that will help your situation.

Patch

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

That's actually not how it works.

I agree that is not how it is supposed to work.

I run two systems, the second system I have not updated the packages. Looking at the system I have not update

Update setting.jpg

Yet the package Manager still offers pfBlockerNG-dev v3.1.0_6
Packages v2.6.jpg

I'm not sure if @BBcan177 is aware of this and if it is considered a bug or expected behaviour.

SteveITS

@patch That version was just released. It’s expected to see it offered. Whatever happened to your install is something else.

Honest_Matt

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.

SteveITS

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

Vortexmind

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

Patch

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.

stephenw10

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

Sergei_Shablovsky

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

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!

stephenw10

Had you switched the update branch back to 2.6?

What 2.7 snapshot is that running?

Sergei_Shablovsky

@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

Sergei_Shablovsky

@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

SteveITS

@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

stephenw10

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

Sergei_Shablovsky

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

Sergei_Shablovsky

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