RB
Added by Anonymous over 9 years ago. Updated over 9 years ago.
100%
Description
Upgrade shows Failure notice after although it completes successfully.
Investigation has shown the upgrade script PID file is disappearing which leads the GUI to assume the upgrade is finished.
Files
| SG1000.jpeg (95.1 KB) SG1000.jpeg | Greg Siemon, 03/10/2017 11:50 PM |
Updated by Anonymous over 9 years ago
Actions
#1
We experienced the same issue today on an APU board. Looks like GUI stopped tracking pfSense-upgrade json and considered upgrade has failed but it kept running in background as expected
Updated by Anonymous over 9 years ago
Actions
#3
Fixed on pfSense-upgrade 0.18
Updated by Anonymous over 9 years ago
Actions
#5
I still see a failure on update as the PID file is deleted, but it now happens later in the update process.
>>> Updating repositories metadata... 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. >>> Unlocking package pfSense-kernel-pfSense-uFW... done. >>> Unlocking package pfSense-u-boot-ufw... 2.4.0.b.20170302.1426 version of pfSense is available done. >>> Downloading upgrade packages... Updating pfSense-core repository catalogue... pfSense-core repository is up-to-date. Updating pfSense repository catalogue... == Failure message displayed ==
Renato Botelho wrote:
Fixed on pfSense-upgrade 0.18
I'm still seeing 'failures' part way through the script. Screenshot attached...
The upgrade continues and the SG-1000 reboots with the latest update installed but there is no way to see what is going on except peering at the System Activity under Diagnostics.
BTW The Updates page on the SG-1000 doesn't show the update progress bar (red bar that fills up as each update package is downloaded) like I see on my VM installation. Not sure if this is another bug or by design on the SG-1000.
Updated by Anonymous over 9 years ago
Actions
#7
The progress bar issue is another matter. We are waiting for a fix from upstream.
pfSense-upgrade 0.22 should fix it
Fix confirmed
Also available in: Atom
