Updating to 2.3.1a release fails and breaks ability to update in the future?

Tantamount

Updating repositories metadata…
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
All repositories are up-to-date.
Upgrading pfSense-repo... done.
Updating repositories metadata...
Updating pfSense-core repository catalogue...
Repository pfSense-core has a wrong packagesite, need to re-create database
Fetching meta.txz: . done
pkg: No trusted public keys found
repository pfSense-core has no meta file, using default settings
Fetching packagesite.txz: . done
pkg: No trusted public keys found
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
Repository pfSense has a wrong packagesite, need to re-create database
Fetching meta.txz: . done
pkg: No trusted public keys found
repository pfSense has no meta file, using default settings
Fetching packagesite.txz: .......... done
pkg: No trusted public keys found
Unable to update repository pfSense
Failed

System / Update / System Update now shows this:

The following input errors were detected:
ERROR: Error trying to get packages list. Aborting...
pkg: No trusted public keys found pkg: No trusted public keys found pkg: No trusted public keys found pkg: No trusted public keys found pkg: Repository pfSense-core cannot be opened. 'pkg update' required pkg: Repository pfSense cannot be opened. 'pkg update' required
ERROR: Error trying to get packages list. Aborting...
pkg: No trusted public keys found pkg: No trusted public keys found pkg: No trusted public keys found pkg: No trusted public keys found pkg: Repository pfSense-core cannot be opened. 'pkg update' required pkg: Repository pfSense cannot be opened. 'pkg update' required

maverick_slo

Where did you see -RELEASE?

jimp

https://forum.pfsense.org/index.php?topic=109690.0

aeroliteflyer

I am getting same error. Got automatic update notification on dashboard and when I clicked it the update failed and now shows that message.

opitrice

Same here…

Keyser Soze

I had to do this to fix it:

https://forum.pfsense.org/index.php?topic=109690.0


fetch -qo /usr/local/share/pfSense/keys/pkg/trusted/ https://raw.githubusercontent.com/pfsense/pfsense/RELENG_2_3_0/src/usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406

Abhishek

Thank you , worked for me after running the above command
.

tgharold

I had to fight with this error ( repository pfSense-core has no meta file ) today.

This particular pfSense server uses a DNS Resolver that does not use forwarding, and it broke during the upgrade from 2.2 to 2.3. Because the DNS resolver was broken, the pkg command could not talk to the pfSense package server, which is why it couldn't get meta data for the repository.

If you Ctrl-C to the command line (Ctrl-C, then [Enter] for /bin/sh), you can start to do some troubleshooting that will indicate whether you have DNS resolution issues.

1. Verify that you can ping 4.4.4.4 or 8.8.8.8 or some other public IP address
2. Attempt to ping a name site to test DNS resolution.
3. "pkg update -f" and "pkg upgrade -f" won't work either.

If DNS resolution fails, look at /etc/resolv.conf and you'll probably see that you're using a localhost DNS resolver of 127.0.0.1. You can fix the issue temporarily via:

echo "nameserver 8.8.8.8" >> /etc/resolv.conf

This is also the eventual fix for getting the upgrade to complete. If your 2.3 upgrade has gotten to the point where you can access the Web UI, you can fix it. If you, like I did, get an issue where the web portal complains about a crash error and none of the menus work, opening up the crash error report will allow the menus to work.

Either way, the goal is to get to Diagnostics -> Command Prompt.

1. Use "cat /etc/resolv.conf" to find out what DNS servers are being used
2. Use the echo command above, to add another DNS server (4.4.4.4 or 8.8.8.8) to the file.

If you're watching the console, you should see the pkg updates start to work properly now that they can resolve the repository hostname.

tgharold

Another possible root cause for upgrade failure is if the old configuration XML file had multiple VLANs (or multiple LANs on separate interfaces) and the <ipaddrv6>block has FE80 as the link local address for multiple VLANs. That seems to confuse pfSense 2.3.

The workaround is to change those <ipaddrv6>FE80</ipaddrv6> to just <ipaddrv6>without the FE80 portion and then restore the configuration file.</ipaddrv6></ipaddrv6>

phil.davis

@tgharold:

Another possible root cause for upgrade failure is if the old configuration XML file had multiple VLANs (or multiple LANs on separate interfaces) and the <ipaddrv6>block has FE80 as the link local address for multiple VLANs. That seems to confuse pfSense 2.3.

The workaround is to change those <ipaddrv6>FE80</ipaddrv6> to just <ipaddrv6>without the FE80 portion and then restore the configuration file.</ipaddrv6></ipaddrv6>

I added a Redmine issue so this gets investigated:
https://redmine.pfsense.org/issues/6343

cmb

@tgharold:

The workaround is to change those <ipaddrv6>FE80</ipaddrv6> to just <ipaddrv6>without the FE80 portion and then restore the configuration file.</ipaddrv6>

only way that happened is if you manually edited that into the config to begin with. That's not a valid IPv6 address, and the GUI's input validation won't accept that.