Problems with upgrade 2.7.0.a.20220520.0600 -> 2.7.0.a.20220527.0600 (or anything)
-
For the last 3 days I've been trying to update the build.
This is what I see in the logs.
>>> Updating repositories metadata... Updating pfSense-core repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: . done Processing entries: . done pfSense-core repository update completed. 7 packages processed. Updating pfSense repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: .......... done Processing entries: .......... done pfSense repository update completed. 514 packages processed. All repositories are up to date. >>> Removing vital flag from php74... done. >>> Downloading upgrade packages... 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. Checking for upgrades (5 candidates): ..... done Processing candidates (5 candidates): ..... done The following 5 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pfSense: 2.7.0.a.20220520.0600 -> 2.7.0.a.20220527.0600 [pfSense] pfSense-base: 2.7.0.a.20220520.0600 -> 2.7.0.a.20220527.0600 [pfSense-core] pfSense-default-config: 2.7.0.a.20220520.0600 -> 2.7.0.a.20220527.0600 [pfSense-core] pfSense-kernel-pfSense: 2.7.0.a.20220520.0600 -> 2.7.0.a.20220527.0600 [pfSense-core] pfSense-rc: 2.7.0.a.20220520.0600 -> 2.7.0.a.20220527.0600 [pfSense-core] Number of packages to be upgraded: 5 108 MiB to be downloaded. [1/5] Fetching pfSense-rc-2.7.0.a.20220527.0600.pkg: .. done [2/5] Fetching pfSense-kernel-pfSense-2.7.0.a.20220527.0600.pkg: .......... done [3/5] Fetching pfSense-default-config-2.7.0.a.20220527.0600.pkg: . done [4/5] Fetching pfSense-base-2.7.0.a.20220527.0600.pkg: .......... done [5/5] Fetching pfSense-2.7.0.a.20220527.0600.pkg: . done Checking integrity... done (0 conflicting) >>> Downloading pkg... No packages are required to be fetched. Integrity check was successful. >>> Upgrading pfSense-rc... Checking integrity... done (0 conflicting) The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pfSense-rc: 2.7.0.a.20220520.0600 -> 2.7.0.a.20220527.0600 [pfSense-core] Number of packages to be upgraded: 1 [1/1] Upgrading pfSense-rc from 2.7.0.a.20220520.0600 to 2.7.0.a.20220527.0600... ===> Setting net.pf.request_maxcount=400000 [1/1] Extracting pfSense-rc-2.7.0.a.20220527.0600: ...... done >>> Upgrading pfSense kernel... Checking integrity... done (0 conflicting) The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pfSense-kernel-pfSense: 2.7.0.a.20220520.0600 -> 2.7.0.a.20220527.0600 [pfSense-core] Number of packages to be upgraded: 1 [1/1] Upgrading pfSense-kernel-pfSense from 2.7.0.a.20220520.0600 to 2.7.0.a.20220527.0600... [1/1] Extracting pfSense-kernel-pfSense-2.7.0.a.20220527.0600: .......... done ===> Keeping a copy of current kernel in /boot/kernel.old >>> Removing unnecessary packages... done. System is going to be upgraded. Rebooting in 10 seconds. SuccessAfter that and a reboot I come back to this:
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. Checking for upgrades (6 candidates): ...... done Processing candidates (6 candidates): ...... done The following 6 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pfSense: 2.7.0.a.20220520.0600 -> 2.7.0.a.20220527.0600 [pfSense] pfSense-base: 2.7.0.a.20220520.0600 -> 2.7.0.a.20220527.0600 [pfSense-core] pfSense-default-config: 2.7.0.a.20220520.0600 -> 2.7.0.a.20220527.0600 [pfSense-core] pfSense-kernel-pfSense: 2.7.0.a.20220520.0600 -> 2.7.0.a.20220527.0600 [pfSense-core] pfSense-rc: 2.7.0.a.20220520.0600 -> 2.7.0.a.20220527.0600 [pfSense-core] pfSense-upgrade: 1.0_23 -> 1.0_24 [pfSense] Number of packages to be upgraded: 6 108 MiB to be downloaded.Telling me the update didnt apply. Any ideas?
-
Are you using RAM disks for
/tmpand/var? If so, try disabling them. There were some issues a few snapshots back, they should be solved now so it's safe to enable them again after upgrading. -
This post is deleted! -
@jimp After this I am now getting random crashes.
https://pastebin.com/pXEp6mdp
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.