Bug #10303
closed
pfSense-upgrade is not upgrading itself
0%
Description
pfSense-upgrade was being registered as a dependency of pfSense-repo pkg. Because of that, when pfSense-repo package was upgraded to latest version, it was upgraded together and the code used to detect a new version of pfSense-upgrade was not being triggered.
Updated by Peter Pain almost 5 years ago
I got a
/bin/sh: cannot open /usr/local/sbin/pfSense-upgrade: No such file or directory
after updating to 2.4.5.r.20200228.1200 when trying to update on the console with option "13".
Workaround:
"pkg update && pkg upgrade -y" to update to 2.4.5.r.20200228.1500 then installed "pfSense-upgrade: 0.78" automatically:
-r-xr-xr-x 1 root wheel 2253 Feb 28 21:00 /usr/local/sbin/pfSense-upgrade
(TZ is Europe/Berlin)
No idea if that breaks update from the gui for people not using the console to update.
Updated by Chris Palmer almost 5 years ago
Peter Pain wrote:
I got a
/bin/sh: cannot open /usr/local/sbin/pfSense-upgrade: No such file or directory
after updating to 2.4.5.r.20200228.1200
I tried updating from the GUI and ended up with the same issue. Executing "pkg update && pkg upgrade -y" from Peters workaround above worked.
Updated by Grimson Gretzleburg almost 5 years ago
Yes there is currently something going wrong here. I updated to 2.4.5.r.20200229.0900 a moment ago, using the WebUI:
The first part of the update went normal, pfSense downloaded the packages and updated "pfSense-rc" and "pfSense-kernel" followed by the normal reboot.
During the bootup it complained that it couldn't find /usr/local/sbin/pfSense-upgrade, so the "pfSense-base", "pfSense-default-config" and "pfSense" packages where not upgraded.
Checking via "pkg info | grep pfSense" the "pfSense-upgrade" packaged was simply not installed. After installing it using "pkg install pfSense-upgrade" and rebooting a second time the remaining pfSense packages got upgraded normally during bootup.
Updated by Chris Palmer almost 5 years ago
https://forum.netgate.com/topic/150931/update
Looks like a bug or two still.
Follow Peters fix above if this got you.
Updated by Renato Botelho almost 5 years ago
Due to change of pfSense-upgrade dependency to pfSense meta package, before upgrade cycle it was not registered as a dependency and was removed by `pkg autoremove`
I've added some code to set it as vital to prevent it happening again.
If it happens on a system, the fix is just to run `pkg install pfSense-upgrade`
Fixed on 0.79 / 0.67
Updated by Jim Pingle almost 5 years ago
- Status changed from Feedback to Resolved
I've been upgrading VMs here with success on 2.5.0 and 2.4.5 around these times and it's been OK. Even some older VMs I powered on and upgraded have been alright.
Can revisit if needed, perhaps adding a note about that condition to the upgrade guide/blog post is warranted. I'll take care of that,
Updated by Jim Pingle almost 5 years ago
I added a note to the 2.4.5 release notes and to the blog post, so there shouldn't be anything else left to do here.