Bug #8355
closed
Upgrades and packages unavailable after upgrade from 2.3.3_1 to 2.3.4_1
0%
Description
I was running PFSense 2.3.2 and via the Dashboard, opted to upgrade to the release presented: 2.3.3_1. It wound up upgrading to 2.3.4_1. When it rebooted and I signed on again it showed that it could be updated further - 2.4.4, I think, so I clicked the link. But when it got to the page System / Update, it said "Unable to check for updates". The Package Manager also gets the message "Unable to retrieve package information." I've tried various tweaks to the DNS resolver configuration as is suggested in some threads.
Attempting an update via console option 13 repeatedly gets these results below. There seems to be an issue with the architecture...
Enter an option: 13>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
pkg-static: Repository pfSense-core 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-core contains packages with wrong ABI: FreeBSD:11:amd64
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!While I would like to update to the current release, it's more important that I get the few packages re-installed. But I can do neither at this point.
Files
Updated by Tim Jones almost 7 years ago
2018-03-22@17:11:25 (Thu) Have encountered exactly the same problem :-(
Updated by Jim Pingle over 6 years ago
- Status changed from New to Not a Bug
This message only appears if you have enabled a non-standard/third-party unofficial pkg repository, which is unsupported. Disable and remove anything added by that repository, and fix your pkg repository configuration in /usr/local/etc/pkg/repos/
Updated by Tom Meier over 6 years ago
i have the same bug and have no "non-standard/third-party unofficial pkg repository" i only have:
[2.3.5-RELEASE][root@pfSense.localdomain]/usr/local/etc/pkg/repos: cat pfSense.conf
FreeBSD: { enabled: no }
pfSense-core: {
url: "pkg+https://pkg.pfsense.org/pfSense_v2_4_3_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_4_3_amd64-pfSense_v2_4_3",
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/local/share/pfSense/keys/pkg",
enabled: yes
}
update status is Up to date:
and dashboard:
and just to be clear when try update over SSH:
Enter an option: 13 >>> Updating repositories metadata... Updating pfSense-core repository catalogue... pkg-static: Repository pfSense-core 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-core contains packages with wrong ABI: FreeBSD:11:amd64 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! pfSense - Netgate Device ID: c6e8200e3a7b130c6d9b *** Welcome to pfSense 2.3.5-RELEASE-p2 (amd64 full-install) on pfSense ***
Updated by David Tr about 4 years ago
Same here, no 3rd party plugins, just openvpn client builder.
After upgrade to 2.3.4-RELEASE-p1 (amd64) from 2.3.3 getting error.
Error on checking for installed packages: Unable to retrieve package information.
Found a reddit about this error which pointed me to NanoBSD no longer being supported which lead me to:
https://docs.netgate.com/pfsense/en/latest/install/upgrade-before-2.3.html?highlight=nanobsd
So apparently NanoBSD is deprecated. Of course the stupid update wizard doesn't warn you about that, just lets you upgrade and then borks the package system leaving you up shit creek without a paddle. I guess if I'd known this BEFORE clicking "update" I'd have know to remove all packages which included officially support OpenVPN client builder so the update wouldn't have borked the package system...and then would I even still be able to convert from a NanoBSD to full install?
On a: Netgate APU which is Netgate's official hardware this is a pretty crappy user experience.
I guess I'm just going to switch out and move to more reliable Mikrotik hardware #SoLongNetgate