Unable to check for updates, pkg-static: wrong architecture
-
@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.
-
P Patch referenced this topic on
-
P Patch referenced this topic on
-
@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 Patch referenced this topic on
-
P Patch referenced this topic on
-
P Patch referenced this topic on
-
P Patch referenced this topic on
-
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. -
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
-
@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!
-
Had you switched the update branch back to 2.6?
What 2.7 snapshot is that running?
-
@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
-
@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 -
@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
-
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
-
@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... ;)
-
@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... -
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
