Unable to update repository pfsense error updating repositories

Troubleshooting Upgrades¶

This document describes methods of troubleshooting problems firewalls may encounter when attempting to run a pfSenseВ® software upgrade.

Cosmetic Problems Post-Upgrade¶

If cosmetic problems occur after performing an upgrade, this is nearly always due to stale browser cache entries for CSS, JavaScript, or other files where the browser does not pull the updated version. Force a refresh of the page in the browser (e.g. Shift+Reload or Ctrl+F5) or clear the browser cache to resolve the issues.

Upgrade Log¶

pfSense-upgrade keeps a log of the last update attempt, which may contain additional useful information. This log is located at /conf/upgrade_log.latest.txt . Please include the contents of this log with any post or support request when requesting assistance with upgrade problems.

Upgrade not Offered / Library Errors¶

If the update system does not offer an upgrade to the most recent version, the upgrade will not proceed, or the upgrade process encounters errors with shared libraries, take the following steps:

Navigate to System > Updates

Set Branch to Previous stable version

Wait a few moments for the upgrade check to complete

Optional: Confirm that the latest version of pfSense-upgrade is present using pkg-static info -x pfSense-upgrade .

If the correct version is not present, wait a bit longer and check again as that package may be updating in the background.

Set Branch to Latest stable version

Wait a few moments for the upgrade check to complete

If the upgrade is still not offered, refresh the repository configuration and upgrade script by running the following commands from the console or shell:

If that procedure results in an error, or the upgrade is still not offered, then attempt to update to an intermediate version. For example, to get from Plus 2.4.5-p1 to Plus 21.05 or later, upgrade to Plus 21.02.x before proceeding to later versions if a direct upgrade does not succeed. In these cases, the appropriate version will be visible as a branch to select.

If pkg is unable to update and complains about the repository metadata version, the pkg utility may need to be updated manually to version 1.13.x or later.

Example metadata version error:

To correct the problem, manually bootstrap pkg from an ssh or console shell:

Do not run the above command from Diagnostics > Command as it requires interactive input. If ssh and console shells are unavailable, use this variation instead:

Rewrite Repository Information¶

In some cases the repository information may need to be rewritten:

Navigate to System > Updates

Set the Branch to Latest Development Snapshots

Wait for the page to refresh

Set the Branch to Latest stable version

If the update still does not appear, run the commands above from the console or shell.

CLI Troubleshooting¶

If the GUI update is not functioning as expected, there are a handful of shell commands that can help gather information or resolve problems.

Force pkg Metadata Update¶

Often times DNS or connectivity problems will prevent the firewall from finding updates. A quick way to verify this is to force a pkg metadata update:

This command forces an update and will print errors if problems are found, a few potential errors include:

No address record

The firewall cannot resolve the update server hostname. This could be a problem with DNS from the firewall itself, or connectivity from the firewall to the Internet in general, such as a missing or incorrect default route.

No route to host

The firewall cannot reach the update server because it cannot find a route there. Most likely, the firewall is missing its default route or the WAN with the default route is down.

Operation timed out

The firewall was unable to download a file in a timely manner. This is most likely due to degraded connectivity between the firewall and the update servers. It could also be a routing issue, or a problem with IPv6 on the firewall (See IPv6 Connectivity Problems ).

There is a proxy between the firewall and the update servers and it requires authentication. Move the firewall so it is not behind a proxy, or configure the proxy under System > Advanced, Miscellaneous tab.

No trusted public keys found

The firewall is attempting to update from the wrong repository. Ensure the correct branch is selected as mentioned in Rewrite Repository Information . May require a reinstall to resolve. For CE installations, try the following command:

Manual Update Check¶

To run a manual update check from the CLI:

When run successfully, this command will print a line stating that a new version is available, and the version number of the available update. Errors displayed during that process are likely to be the same as those covered in Force pkg Metadata Update .

pkg does not use A/AAAA records. It uses service (SRV) records. The update server meta names such as packages.netgate.com are not meant to be accessed directly using a browser.

To find the actual update servers, lookup the SRV record for the host:

Accessing the hosts using their direct hostnames will work with a browser:

IPv6 Connectivity Problems¶

If IPv6 is configured on the firewall, the pfSense software will prefer to use it when performing an update. There are cases when a firewall may have broken IPv6 connectivity, however, that contribute to problems updating. This could manifest as a timeout or routing error when upgrading.

Typically the operating system will attempt to fall back to IPv4, but the extra time this takes could also lead to a timeout.

The firewall can be configured to prefer IPv4 to eliminate this as a potential cause. See Controlling IPv6 Preference for traffic from the firewall itself for details.

Alternately, from ssh or a console shell, force the upgrade to use IPv4 manually:

Segmentation Fault in pkg¶

Certain cryptographic hardware can have a software-induced race condition which leads to a problematic state. In this state, pkg will crash with a segmentation fault:

In this case, the device must be powered off and back on to recover. A warm reboot is not sufficient to reset the hardware.

Navigate to Diagnostics > Halt System

Click Halt

Wait for the device to shut down. Monitor the console to ensure that the shutdown completes.

Unplug the power adapter

Plug the power adapter back in

Forced pkg Reinstall¶

Forcing a reinstallation of all packages may resolve problems that otherwise may require a full reinstall. This is not ideal, as a clean install is more likely to have a positive result, but that is not always an option in every situation (e.g. remote install with no console access).

To forcefully reinstall all packages, take the following steps:

Clean the repository and forcefully reinstall pkg, repo data, and the upgrade script:

Force a reinstall of everything:

Review the list of changes and enter y to proceed

Manually reboot the firewall

Last Resort¶

If nothing else works then a reinstall will eliminate any possibility of problems related to the upgrade itself.

Источник

Name already in use

docs / source / install / upgrade-troubleshooting.rst

• Go to file T
• Go to line L
• Copy path
• Copy permalink

Copy raw contents

Copy raw contents

This document describes methods of troubleshooting problems firewalls may encounter when attempting to run a pfSense® upgrade.

pfSense-upgrade keeps a log of the last update attempt, which may contain additional useful information. This log is located at /conf/upgrade_log.latest.txt . Please include the contents of this log with any post or support request when requesting assistance with upgrade problems.

Upgrade not Offered / Library Errors

If the update system does not offer an upgrade to the most recent version, the upgrade will not proceed, or the upgrade process encounters errors with shared libraries, take the following steps:

Navigate to System > Updates

Set Branch to Previous stable version

Wait a few moments for the upgrade check to complete

Optional: Confirm that the latest version of pfSense-upgrade is present using pkg-static info -x pfSense-upgrade . For example, it should be at version >= 0.70 for pfSense 2.4.5-p1.

If the correct version is not present, wait a bit longer and check again as that package may be updating in the background.

Set Branch to Latest stable version

Wait a few moments for the upgrade check to complete

If the upgrade is still not offered, refresh the repository configuration and upgrade script by running the following commands from the console or shell:

Repository Metadata Version Errors

If pkg is unable to update and complains about the repository metadata version, the pkg utility may need to be updated manually to version 1.13.x or later.

Example metadata version error:

To correct the problem, manually bootstrap pkg from an ssh or console shell:

Do not run the above command from Diagnostics > Command as it requires interactive input. If ssh and console shells are unavailable, use this variation instead:

Rewrite Repository Information

In some cases the repository information may need to be rewritten:

• Navigate to System > Updates
• Set the Branch to Latest Development Snapshots
• Wait for the page to refresh
• Set the Branch to Latest stable version

If the update still does not appear, run the commands above from the console or shell.

If the GUI update is not functioning as expected, there are a handful of shell commands that can help gather information or resolve problems.

Force pkg Metadata Update

Often times DNS or connectivity problems will prevent the firewall from finding updates. A quick way to verify this is to force a pkg metadata update:

This command forces an update and will print errors if problems are found, a few potential errors include:

Manual Update Check

To run a manual update check from the CLI:

When run successfully, this command will print a line stating that a new version is available, and the version number of the available update. Errors displayed during that process are likely to be the same as those covered in :ref:`upgrade-troubleshooting-metadata` .

pkg.pfsense.org Has no A/AAAA Record

pkg does not use A/AAAA records. It uses service (SRV) records. The update server meta names such as pkg.pfsense.org are not meant to be accessed directly using a browser.

To find the actual update servers, lookup the SRV record for the host:

Accessing the hosts using their real hostnames will work with a browser:

IPv6 Connectivity Problems

If IPv6 is configured on the firewall, the pfSense software will prefer to use it when performing an update. There are cases when a firewall may have broken IPv6 connectivity, however, that contribute to problems updating. This could manifest as a timeout or routing error when upgrading.

Typically the operating system will attempt to fall back to IPv4, but the extra time this takes could also lead to a timeout.

The firewall can be configured to prefer IPv4 to eliminate this as a potential cause. See :doc:`../interfaces/controlling-ipv6-or-ipv4-preference` for details.

Alternately, from ssh or a console shell, force the upgrade to use IPv4 manually:

Forced pkg Reinstall

Forcing a reinstallation of all packages may resolve problems that otherwise may require a full reinstall. This is not ideal, as a clean install is more likely to have a positive result, but that is not always an option in every situation (e.g. remote install with no console access).

To forcefully reinstall all packages, take the following steps:

• Make a backup
• Clean the repository and forcefully reinstall pkg, repo data, and the upgrade script:

• Force a reinstall of everything:

• Review the list of changes and enter y to proceed
• Manually reboot the firewall

If nothing else works then a reinstall will eliminate any possibility of problems related to the upgrade itself.

Источник

Unable to update repository pfsense error updating repositories

Hi everyone! I have been looking for a solution about this problem on the web but I can’t find a decent solution that will make this work.. Basically, I was looking at the PFsense WebUI when I noticed that the firewall seems to not connect to remote update server.

On the command prompts, it shows me this:

This is a recurrence of this problem and I didn’t clearly remember how I have fixed it last time, plus it was just a lucky moment.

Plus, I noticed that the backup doesn’t work, Snort signature download doesn’t work and also PFblocker list update doesn’t work, but my network can connect to the internet with no problem. Just that I noticed that the PFSense itself can’t connect to the update servers. I have set DNS to 8.8.8.8 on General Setup.

Any answer or response to this post is very much appreciated. Thank you.

Network is unreachable means it has no route to get anywhere. Either your WAN is down or pfSense doesn’t have it set as the default gateway. Check Diagnostics > Routes and see if you have a line marked default pointing to your expected WAN gateway. Then go to System > Routing and check what the default is set to there.

Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

Do not Chat/PM for help!

@jimp I’m sure that the WAN is up. I have 3 WAN interface setup 1 main & 2 as a back-up. All WAN are up during the process but still fails. Any solutions other than this?

Well, I solved it by changing the default gateway to automatic. Anyway. Thanks for the feedback.

It doesn’t matter how many you have, one should be set to default. Either directly or by using a gateway group as the default. There is an open bug report about a gateway group as default not working for everyone, though, perhaps your setup is one of the affected ones.

As long as you have a default route showing under Diagnostics > Routes you should be fine.

Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

Источник

open

>>> Updating repositories metadata... 
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pkg-static: Repository pfSense has a wrong packagesite, need to re-create database
Fetching meta.conf: . done
Fetching packagesite.txz: .......... done
Processing entries: 
pkg-static: Newer FreeBSD version for package pfSense-pkg-softflowd:
To ignore this error set IGNORE_OSVERSION=yes
- package: 1202504
- running kernel: 1102000

pkg-static: repository pfSense contains packages for wrong OS version: FreeBSD:12:amd64
Processing entries... done
Unable to update repository pfSense
Error updating repositories!
>>> Locking package pkg... done.
ERROR: Unable to compare version of pfSense-repo

>>> Updating repositories metadata... 
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pkg-static: Repository pfSense has a wrong packagesite, need to re-create database
Fetching meta.conf: . done
Fetching packagesite.txz: .......... done
Processing entries: 
pkg-static: Newer FreeBSD version for package minicron:
To ignore this error set IGNORE_OSVERSION=yes
- package: 1103504
- running kernel: 1003000

pkg-static: repository pfSense contains packages for wrong OS version: FreeBSD:11:amd64
Processing entries... done
Unable to update repository pfSense
Error updating repositories!
>>> Locking package pkg... done.
ERROR: Unable to compare version of pfSense-repo

[2.4.4-RELEASE][admin@host]/root: pfSense-upgrade 
>>> Updating repositories metadata... 
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.txz: .......... done
Processing entries: 
pkg-static: Newer FreeBSD version for package pfSense-pkg-lldpd:
To ignore this error set IGNORE_OSVERSION=yes
- package: 1202504
- running kernel: 1102000

pkg-static: repository pfSense contains packages for wrong OS version: FreeBSD:12:amd64
Processing entries... done
Unable to update repository pfSense
Error updating repositories!

2.4.4-RELEASE-p3 (amd64)
built on Wed May 15 18:53:44 EDT 2019
FreeBSD 11.2-RELEASE-p10

The system is on the latest version.

[2.4.4-RELEASE][root@x.x.x.x]/root: pkg install -y pfSense-upgrade
pkg: Warning: Major OS version upgrade detected.  Running "pkg bootstrap -f" recommended
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
Fetching meta.conf: 100%    163 B   0.2kB/s    00:01
Fetching packagesite.txz: 100%  140 KiB 143.9kB/s    00:01
Processing entries:   0%
pkg: Newer FreeBSD version for package pfSense-pkg-lldpd:
To ignore this error set IGNORE_OSVERSION=yes
- package: 1202504
- running kernel: 1102000

pkg: repository pfSense contains packages for wrong OS version: FreeBSD:12:amd64
Processing entries: 100%
Unable to update repository pfSense
Error updating repositories!

Also available in: Atom
PDF