23.05.1 shows update available, but already the latest
-
On my recently rebuilt Netgate 1537 running PFSense+ 23.05.1, the primary dashboard says update is available, but of course, when I click the update button, it then goes to the update section of PFsense but then shows that the system is up to date.
This appliance had been giving me issues recently so it has recently been wiped and rebuilt with the official PFSense+ image and then restored the config from backup.
Any ideas as to why the dashboard keeps thinking an update should be available?
-
Any update to this? I'm seeing the same problem on my SG-3100.
-
Check the installed pkg versions. One has probably been downgraded (or failed to upgrade).
At the command line run:pkg-static info -x pfsense -
pfSense-23.05
pfSense-Status_Monitoring-php82-1.8_3
pfSense-base-23.05.1
pfSense-boot-23.05.1
pfSense-default-config-serial-23.05.1
pfSense-kernel-pfSense-3100-23.05.1
pfSense-pkg-Service_Watchdog-1.8.7_1
pfSense-pkg-Shellcmd-1.0.5_3
pfSense-pkg-Status_Traffic_Totals-2.3.2_3
pfSense-pkg-System_Patches-2.2.4
pfSense-pkg-WireGuard-0.2.0_2
pfSense-pkg-acme-0.7.5
pfSense-pkg-apcupsd-0.3.92_1
pfSense-pkg-mtr-nox11-0.85.6_3
pfSense-pkg-openvpn-client-export-1.9_1
pfSense-pkg-pfBlockerNG-3.2.0_6
pfSense-rc-23.05.1
pfSense-repo-23.05
pfSense-repoc-20230605
pfSense-u-boot-3100-20210930_1
pfSense-u-boot-env-20230123
pfSense-upgrade-1.0_68
php82-pfSense-module-0.95 -
Ok, so you still have some 23.05 pkgs there including the main pfSense meta pkg.
You can manually upgrade those pkgs. Make sure the update branch is set to 23.05.1 (latest stable), then run at the command line (not via the gui command prompt):pkg-static upgradeIt should offer you the 23.05.1 upgrades for at least the pfSense and pfSense-repo pkgs.
Once those are upgraded the system will show as up to date.
Steve
-
@stephenw10 Worked like a charm, thanks for the help.
-
@stephenw10 said in 23.05.1 shows update available, but already the latest:
pkg-static info -x pfsense
Hi,
This hasn't worked for my I am afraid.
[23.05.1-RELEASE][admin@firewall]/root: pkg-static upgrade
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.
Checking for upgrades (1 candidates): 100% 1 B 0.0kB/s 00:01
Processing candidates (1 candidates): 100% 1 B 0.0kB/s 00:01
Checking integrity... done (0 conflicting)
Your packages are up to date.[23.05.1-RELEASE][admin@firewall]/root: pkg-static info -x pfsense
pfSense-23.05.1
pfSense-Status_Monitoring-php82-1.8_3
pfSense-base-23.05.1
pfSense-boot-23.05.1
pfSense-default-config-serial-23.05.1
pfSense-kernel-pfSense-23.05.1
pfSense-rc-23.05.1
pfSense-repo-23.05.1
pfSense-repoc-20230605
pfSense-upgrade-1.0_68
php82-pfSense-module-0.95All packages seem to be up-to-date but the dashboard still shows that updates are needed.
Hope you can help.
-
@joe_schmoe_54545 What's the output of the command that Steve posted for OP?
pkg-static info -x pfsense -
@rcoleman-netgate thanks I sorted it out; tried to post that but was told that it was SPAM lol.
Thanks for the help all. Was an update of package manager which is likely due to my having accidents switched to development branch then back to stable without actually updating the firewall.
Hope this helps someone else in the same boat.
-
@joe_schmoe_54545 Try again. A minimum reputation is needed to post attachments.
-
-
@rcoleman-netgate I wasn’t adding an attachment at all. Simply the same text I just added above. Thanks :)
-
Try pkg clean
pkg update
pkg upgradeReboot and see if the issue resolved
-
Scrap this - the following command worked for me:
pkg-static upgrade -fy pkg
