UPGRADE is STUCK!!!

[BigCat58]

The last 20 minutes!

[BigCat58]

Never mind! I did a reboot and it came back up 16.5.2! SO MUCH for the scary screen!

[gravenscroft]

If that happens again, try Ctrl + F5 to refresh your browser window without cached contents. Browser caching is almost always the cause when you're 'stuck' on that upgrade log screen.

[sky-knight]

Yeah, this is one of those things. Those of us that have been around forget about it too.

But the TLDR is upgrades are browser cache corruption causing monsters. The code tells the browser to not cache this stuff... but they do anyway.

So I've learned that before I do ANYTHING involving a freak out regarding Untangle during an upgrade, I swap to a different browser or crack open a private window. Ctrl + F5 is often simply not enough, though digging into your browser's configuration and clearing the cache will.

[Loudog2]

Since my upgrade my 2nd wan has been offline. I’m trying to figure out what got changed. Unfortunately I just had shoulder replacement surgery so I can’t get back behind everything to directly connect into the metronet modem to check all the addresses and overrides to see if something changed that didn’t update. Anyone else ever have this happen?

I should’ve stated. Everything shows connected green and full duplex. It’s just not connecting to the Failover.

[sky-knight]

Double check your test for that WAN.

But no, upgrades haven't broken basic network connectivity in years. So you're down to testing that link itself, which you should be able to do remotely. Just ping the gateway, the next hop past, etc.

[johndball]

So I have two clients with the same "issue" (is it really an issue?). Did the whole private browser song and dance... how long before I should reboot? We're at 40 minutes now for each client. Network traffic is flowing, only hiccup is VPN is not working at the moment for one of the clients.

Dashboard shows 16.5.2 for one client, other client still shows disconnected from the Control Center dashboard and is running version "16.5" which it was running 16.5.1 prior to upgrade.

[jcoffin]

I would ssh to the boxes and look at the /var/log/uvm/upgrade.log to see if the upgrade is done.

[johndball]

I let it soak for 48 hours, same message, rebooted, and was greeted by this warning. The one appliance is back in the ETM dashboard, VPN works, and apps are reporting.

The other appliance is going on 49 hours and won't be rebooted until later this week (that client is more critical in nature).

[gravenscroft]

I let it soak for 48 hours, same message, rebooted, and was greeted by this warning.

DM me your UID and I'll take a look.

[johndball]

I ended up going on site myself. Just in case you're wondering, around the 56 hour mark it just stopped processing all traffic. I reset the device and it came back up with 16.5.2. I'll DM you the two appliance's UIDs and see if we can get that error message to go away on both.

[gravenscroft]

I'll DM you the two appliance's UIDs and see if we can get that error message to go away on both.

Thanks for that! They're all set now.

[fvnet]

Hello, I have the same issue with johndball. Device updated but stuck to that window, left it there for more than an hour, did various browser refresh (FF & Chrome) but no joy. I eventually forced it reboot and it seems the upgrade was done ( 16.5.2.20220810T133847.795eba8fc3-1buster ) but I have that notification triangle that "upgrade process has been interrupt".
That happened 18 days ago, Device is working just fine, that notification won't go away.
Could you also help me out?

[fvnet]

Sorry for bringing this up again. what can we do to have this notification triangle that "upgrade process has been interrupt" go away?

[jcoffin]

Even when the device seems to work correctly, the upgrade might not be complete. If you have support, open a ticket so support can check the upgrade log to see what the issue is.