[SOLVED] Upgrade to 16.1.13 stalled

[davidolrik]

When upgrading to 16.1.13 the upgrade appeared to stop just after "Updating /etc/shells".

On the console in the browser there were a single error:

Code: [Select]

https://my-opnsense.tld/api/core/firmware/upgradestatus Failed to load resource: the server responded with a status of 404 (Not Found)
Looking at processes on the box itself showed no "upgrade" processes, indicating it was finished.

Hitting https://yoda.grepmasters.net/api/core/firmware/upgradestatus manually works and the status in the json is "done".

I'm guessing the api was offline for a split second where my browser requested the upgradestatus.

[franco]

Hi there,

Uh, sweet, you caught the error in the console. We can fix this now. 

This was a glitch that very rarely happened and the polling in the browser stopped. Thankfully the backend is detached so it keeps running until it's done. We've only ever had a handful of reports for this over the last year.

I've added a ticket, should be fixed in 16.1.14 next week:

https://github.com/opnsense/core/issues/927


Cheers,
Franco

[davidolrik]

Awesome!

Quick question:

If the backend is detached, why is there a warning about "don't navigate away from this page when the upgrade is running" ?

[franco]

The main reason being that you cannot go back to the status polling page while the update is running. It's a limitation of the firmware GUI that should be fixed eventually, but is low on priority as we have bigger additions to firmware coming up soon.

The other (minor) reason is that you would likely encounter service disruption as GUI files are being replaced one after another. That's how the package manager does it and since the HTTP Server is required to keep running it'll sometimes not find this or that file and produce a spurious crash report. That's especially apparent when you leave the dashboard open in another tab/window (or even another machine) as it polls the pages quite frequently and will hit the upgrade window for sure.

As far as these crash reports go we would rather not hide them in case a real problem surfaces there that needs to be addresses so they are visible to cause a slight inconvenience with the user.


Cheers,
Franco

[franco]

This has been solved, will likely be part of the 16.1.15 release in a few weeks.