`wrong architecture` / `package`, upgrade to 2.3.4_1 failed but can't rerun
-
When upgrading, the following text appeared
Processing entries... done Unable to update repository pfSense-core Updating pfSense repository catalogue... pkg-static: Repository pfSense has a wrong packagesite, need to re-create database Fetching meta.txz: . done Fetching packagesite.txz: .......... done Processing entries: pkg-static: wrong architecture: FreeBSD:11:amd64 instead of freebsd:11:x86:64 pkg-static: repository pfSense contains packages with wrong ABI: FreeBSD:11:amd64 Processing entries... done Unable to update repository pfSense Error updating repositories! >>> Unlocking package pkg... done. Failed
After that system update page shows either
Unable to check for updates
or
Up to date.
And can't fix/rerun.
I am afraid if I reboot, it won't up.
How to fix?
-
2.3.4_1
?
The actual main version is 2.3.5 in that "32 only" branch.Btw : 2.3.5 if you decided to stay on the "dead end path" - forced to stay there because your hardware is 32 bits.
pkg-static: wrong architecture: FreeBSD:11:amd64 instead of freebsd:11:x86:64
Never saw this "x86:64" before. If its a 64 bits system, FreeBSD is using "amd64 " for ages already. These are 64 bits versions, and can not be installed as an upgrade on a 32 bit system.
Where are you upgrading from ?
Chose the other branch ? Visit System => Update => Update Settings and make sure you have the correct one.Another fast solution would be : make a config copy.
Get he latest and greatest from https://www.pfsense.org/download/
Install.
Import config.Go do other things ^^
-
My update picture is following
No any
2.3.5
there. -
Sysinfo is following:
I wouldn't choose 32-bit, if it did, it did it itself.
-
Get he latest and greatest from https://www.pfsense.org/download/
Install.
Import config.Oh no! There are too many glitches in pfSense to reinstall it on each :)
-
Did you add/enable any outside repositories or packages to pfSense?
-
Oh no! There are too many glitches in pfSense to reinstall it on each :)
Maybe I'm lucky every time then, but for the last several years now, pfSense never** let me down after an update.
Btw : when the dashboard shows "Unable to check for updates" it tells you it's not able to visit the Internet as it should be.
That would be a "call Houston right now" error for me. Upgrade and update problems are right ahead - worse is scheduled.
Repair this first (this is a 99 % case of a : "DNS setup is not ok" issue).** and if something did pops up, this forum always knew about it already, and what to do right away to make it work again.
I'm not using pfSense at home - but at my work, a hotel, using the captive portal (and FreeRadius now) so if things go bad, I have a boatload of non-happy clients (and that's NO good for moral and $(€)).
Normally, I upgrade after a week or so, and consulting the forum (and redmine - major github chances, etc). -
pkg-static: wrong architecture: FreeBSD:11:amd64 instead of freebsd:11:x86:64
Those are the same ABI but just named differently. I think your pkg package manager is now out of date and doesn't understand that those ABI strings are the same.
You could try to use the console upgrade option, I think it's option 13) in 2.3.4. If that doesn't help, try this from the console shell:
pkg-static update -f pkg-static upgrade -f pkg pkg-static upgrade
For others trying to help, please don't make too many assumptions about what should work and what not. The pkg package manager has had a bumby road to get where it is now and this snafu is just one of issues in the pkg package manager that occasionally breaks the upgrade path.
-
Several switching of branch back and forth helped…