Project

General

Profile

Actions

Bug #8355

closed

Upgrades and packages unavailable after upgrade from 2.3.3_1 to 2.3.4_1

Added by Brian Davidson about 6 years ago. Updated over 3 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
03/04/2018
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:

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

Actions

Also available in: Atom PDF