"Version 2.8.0 is available." but then "up to date"
-
@patient0 said in "Version 2.8.0 is available." but then "up to date":
@nobanzai did you work through Netgate docu: Troubleshooting Upgrades?
Yes, as I wrote:
"I tried every hint from the upgrade docu page, but the problem remains."
I meant the Troubleshooting docu.Is your installation on bare metal or a VM (if yes, what hypervisor)?
It is bare metal.
-
@nobanzai can you please post the command line commands and their output. With the output we may see if or where it fails.
Does 2.7.2 work as expected? Are you using ISC DHCP or KEA? DNS resolver or forwarder? Static/PPPoE/DHCP WAN?
-
@patient0 said in "Version 2.8.0 is available." but then "up to date":
@nobanzai can you please post the command line commands and their output. With the output we may see if or where it fails.
pkg-static info -x pfSense-upgrade pfSense-upgrade-1.2.1 pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade The following package files will be deleted: /var/cache/pkg/pfSense-repo-2.7.2~3aa9dedf41.pkg /var/cache/pkg/pkg-1.20.8_3~48cca6e983.pkg /var/cache/pkg/pfSense-repo-2.7.2.pkg /var/cache/pkg/pkg-1.20.8_3.pkg /var/cache/pkg/pfSense-upgrade-1.2.1~7f3940b016.pkg /var/cache/pkg/pfSense-upgrade-1.2.1.pkg The cleanup will free 11 MiB Deleting files: 100% All done Updating pfSense-core repository catalogue... Fetching meta.conf: 0% Fetching packagesite.pkg: 0% pfSense-core repository is up to date. Updating pfSense repository catalogue... Fetching meta.conf: 0% Fetching packagesite.pkg: 0% pfSense repository is up to date. All repositories are up to date. The following 3 package(s) will be affected (of 0 checked): Installed packages to be REINSTALLED: pfSense-repo-2.7.2 [pfSense] pfSense-upgrade-1.2.1 [pfSense] pkg-1.20.8_3 [pfSense] Number of packages to be reinstalled: 3 11 MiB to be downloaded. [1/3] Fetching pfSense-repo-2.7.2.pkg: 100% 6 KiB 5.9kB/s 00:01 [2/3] Fetching pkg-1.20.8_3.pkg: 100% 10 MiB 1.6MB/s 00:07 [3/3] Fetching pfSense-upgrade-1.2.1.pkg: 100% 20 KiB 20.2kB/s 00:01 Checking integrity... done (0 conflicting) [1/3] Reinstalling pfSense-repo-2.7.2... [1/3] Extracting pfSense-repo-2.7.2: 100% [2/3] Reinstalling pkg-1.20.8_3... [2/3] Extracting pkg-1.20.8_3: 100% Scanning /usr/share/certs/untrusted for certificates... Scanning /usr/share/certs/trusted for certificates... Skipping untrusted certificate /usr/share/certs/trusted/Cybertrust_Global_Root.pem (/etc/ssl/untrusted/76cb8f92.0) Skipping untrusted certificate /usr/share/certs/trusted/DST_Root_CA_X3.pem (/etc/ssl/untrusted/2e5ac55d.0) Skipping untrusted certificate /usr/share/certs/trusted/GlobalSign_Root_CA_-_R2.pem (/etc/ssl/untrusted/4a6481c9.0) Skipping untrusted certificate /usr/share/certs/trusted/Hellenic_Academic_and_Research_Institutions_RootCA_2011.pem (/etc/ssl/untrusted/1636090b.0) Skipping untrusted certificate /usr/share/certs/trusted/Network_Solutions_Certificate_Authority.pem (/etc/ssl/untrusted/4304c5e5.0) Skipping untrusted certificate /usr/share/certs/trusted/Staat_der_Nederlanden_EV_Root_CA.pem (/etc/ssl/untrusted/03179a64.0) Skipping untrusted certificate /usr/share/certs/trusted/TrustCor_ECA-1.pem (/etc/ssl/untrusted/7aaf71c0.0) Skipping untrusted certificate /usr/share/certs/trusted/TrustCor_RootCert_CA-1.pem (/etc/ssl/untrusted/5d3033c5.0) Skipping untrusted certificate /usr/share/certs/trusted/TrustCor_RootCert_CA-2.pem (/etc/ssl/untrusted/3e44d2f7.0) Scanning /usr/local/share/certs for certificates... [3/3] Reinstalling pfSense-upgrade-1.2.1... [3/3] Extracting pfSense-upgrade-1.2.1: 100% You may need to manually remove /usr/local/etc/pkg.conf if it is no longer needed. pkg-static update -f Updating pfSense-core repository catalogue... Fetching meta.conf: 100% 163 B 0.2kB/s 00:01 Fetching packagesite.pkg: 100% 1 KiB 1.5kB/s 00:01 Processing entries: 100% pfSense-core repository update completed. 4 packages processed. Updating pfSense repository catalogue... Fetching meta.conf: 100% 179 B 0.2kB/s 00:01 Fetching packagesite.pkg: 100% 192 KiB 196.2kB/s 00:01 Processing entries: 100% pfSense repository update completed. 550 packages processed. All repositories are up to date.Does 2.7.2 work as expected? Are you using ISC DHCP or KEA? DNS resolver or forwarder? Static/PPPoE/DHCP WAN?
I had the same problem yesterday, when updating 2.7.0 to 2.7.2, but in this case "certutil rehash" solved it. As far as I can see up to today, 2.7.2 works as expected.
At the moment I still use ISC DHCPD.
I use DNS resolver.
This is a HA cluster with more than one internet providers. The pfSense routers are connected to two Fritz!Box routers in a failover scenario. One Fritz!Box connects a cable provider, the other one a VDSL provider. -
@nobanzai try
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#manual-update-check -
@SteveITS said in "Version 2.8.0 is available." but then "up to date":
@nobanzai try
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#manual-update-checkalready tried that to no avail:
pfSense-upgrade -d -c >>> Updating repositories metadata... Updating pfSense-core repository catalogue... Fetching meta.conf: Fetching packagesite.pkg: pfSense-core repository is up to date. Updating pfSense repository catalogue... Fetching meta.conf: Fetching packagesite.pkg: pfSense repository is up to date. All repositories are up to date. Your system is up to date -
@nobanzai Did you by any means select 2.7.2 as update path? That's normal behavior then, as the update will be shown on the dashboard, but when the old stable is the selected update path, no update will be available via console.
What does the "System / Upgrade" dropdown show as currently selected?Just wanted to check as we had that with multiple customers that switched back so they could update a specific package while not doing a full upgrade yet after it came out.
Cheers
-
@JeGr said in "Version 2.8.0 is available." but then "up to date":
@nobanzai Did you by any means select 2.7.2 as update path? That's normal behavior then, as the update will be shown on the dashboard, but when the old stable is the selected update path, no update will be available via console.
What does the "System / Upgrade" dropdown show as currently selected?Yes, I selected 2.7.2 as update path, because "Please select the branch from which to update" seems to make that the correct choice. Probably my English isn't good enough to get the correct meaning.
The dropdown list shows 2.8.0, 2.7.2 and 2.8.1Just wanted to check as we had that with multiple customers that switched back so they could update a specific package while not doing a full upgrade yet after it came out.
That wasn't the reason here, but see above.
So I have to choose 2.8.0?
But when I do that, I get "Unable to check for updates"?!?Cheers
Thx.
-
said in "Version 2.8.0 is available." but then "up to date":
So I have to choose 2.8.0?
But when I do that, I get "Unable to check for updates"?!?Ok, I chose 2.8.0, got "Unable to check for updates", reloaded the page, got "pfSense-repoc: no package 'name' pfSense-repoc: no pfSense packages installed ", executed
pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgradeand are able now to update.
Whow, that really wasn't obvious.Thx a lot for your help!
-
So, unfortunately the upgrade failed:
Updating boot code... /usr/local/sbin/../libexec/install-boot.sh -b auto -f ufs -s gpt -u ada0 No freebsd-boot partition found...skipping. ESP /dev/ada0p1 mounted on /tmp/stand-test.JXO3mb Only 636KB space remaining: removing old FreeBSD boot1.efi file /efi/boot/bootx64.efi rmdir: /tmp/stand-test.JXO3mb/efi/boot: Directory not empty Failed to update the EFI System Partition /dev/ada0p1 Insufficient space remaining for /boot/loader.efi Run e.g "mount -t msdosfs /dev/ada0p1 /mnt" to inspect it for files that can be removed. Unable to update boot code on /dev/ada0 FailedSo the EFI partition is too small - and it does contain STARTUP.NSH only, so nothing to delete.
Does that mean, I have to reinstall the system with a larger EFI parttion or is the message misleading? "Directory not empty" shouldn't happen, because this is not a file, I created. -
branch from which to update
I can see that confusion. Historically it was the branch e.g. “current” or “previous” and the version changed over time. They probably still consider “2.8.0” the branch, so you’d pick 2.8 then update to the latest in 2.8. The goal was to prevent people from updating packages from current/2.8 when they were running 2.7. (
Per my sigeh, forgot I updated it)Re EFI, there have been a handful of threads about that error. Old installation? If you reinstall you’ll get ZFS. Or a thread may have commands that work if you can find one.
-
@SteveITS said in "Version 2.8.0 is available." but then "up to date":
Re EFI, there have been a handful of threads about that error. Old installation? If you reinstall you’ll get ZFS. Or a thread may have commands that work if you can find one.
I found commands to enlarge the EFI partitions, but on /dev/ada0p1 only one single file remained - STARTUP.NSH. So I can't backup the EFI files any more. I'll try to copy them from the second pfSense.
-
Mmm, the 'from' there refers to the remote repo branch you are pulling updates from. But, yes, I can see how it could be confusing.
-
said in "Version 2.8.0 is available." but then "up to date":
@SteveITS said in "Version 2.8.0 is available." but then "up to date":
Re EFI, there have been a handful of threads about that error. Old installation? If you reinstall you’ll get ZFS. Or a thread may have commands that work if you can find one.
I found commands to enlarge the EFI partitions, but on /dev/ada0p1 only one single file remained - STARTUP.NSH. So I can't backup the EFI files any more. I'll try to copy them from the second pfSense.
Ok, I enlarged the efi partition on both pfSense.
Restarting the update on the secondary worked, now I'll run it on the primary. -
said in "Version 2.8.0 is available." but then "up to date":
Ok, I enlarged the efi partition on both pfSense.
Restarting the update on the secondary worked, now I'll run it on the primary.All updates have passed without errors, both pfSense are back to normal, data flow seems to be ok.
Thx@all.
Thread closed.
cu.
