When I ran upgrade packages I never got a pop-up saying the download was complete or to reboot. I waited about 15 minutes and rebooted. eisy-ui was upgraded to 0.9.0

2 minutes ago, Techman said:

When I ran upgrade packages I never got a pop-up saying the download was complete or to reboot. I waited about 15 minutes and rebooted. eisy-ui was upgraded to 0.9.0

It's best to update from eisy-ui if you are upgrading from a recent enough version.

I can confirm that the update status on eisy-ui changes to "A reboot is required" (or something to that effect) when the update is complete.

-Tom

@bmercier What I don't understand is on the eisy-ui it has an "upgrade to" column, but it never reflects that something is available to update. If you hadn't posted that .9 was available would the system have ever told me in the web ui?

After the update I get this confirmation showing a reboot is required:

So I click "Reboot eisy" and about a minute later get this error:

I then logout of the system and log back in and get a 404 error. I refresh the browser window (Chrome Version 143.0.7499.171) and the system comes up.

During this time UD Mobile was giving notifications it typically gave about PG3 stopping then starting. I waited until the "starting" notification before trying to log in again.

I would suggest that part of the "reboot eisy" process that it log you out of the web ui so errors like this might be avoided. Unless it should be able to maintain access to the ui following the reboot. It didn't appear to since no other links/sections worked until I logged out and logged back in.

1 hour ago, Geddy said:

@bmercier What I don't understand is on the eisy-ui it has an "upgrade to" column, but it never reflects that something is available to update. If you hadn't posted that .9 was available would the system have ever told me in the web ui?

After the update I get this confirmation showing a reboot is required:

So I click "Reboot eisy" and about a minute later get this error:

I then logout of the system and log back in and get a 404 error. I refresh the browser window (Chrome Version 143.0.7499.171) and the system comes up.

During this time UD Mobile was giving notifications it typically gave about PG3 stopping then starting. I waited until the "starting" notification before trying to log in again.

I would suggest that part of the "reboot eisy" process that it log you out of the web ui so errors like this might be avoided. Unless it should be able to maintain access to the ui following the reboot. It didn't appear to since no other links/sections worked until I logged out and logged back in.

Hi Geddy,

Yes, the Upgrade To would have been updated eventually. The Upgrade To shows the equivalent of "pkg search". Let me share some of the internals: When you updated manually, you would do a sudo pkg update, then sudo pkg upgrade. The "update" part refreshes a local database of pkg available. The "Upgrade To" shows that. It won't do a "pkg update" by itselk. This is done on schedule, I believe daily. So you would have seen it eventually.

The reboot error you saw has been corrected in 0.9.0. So on the next update, it should not show and an error anymore.

After the reboot, the browser showed a 404 because the UI url for the upgrade has changed. The upgrade used to be under Settings, and it is now under system. That should not happen anymore.

Benoit