2.3.8.140 seems stuck in an update loop?

C-7 here, trying to update from 2.3.8.139 to 2.3.8.140. It detects the update is available, downloads it, extracts it, then goes straight to “checking for updates” and won’t break the cycle til the hub is rebooted. But then any attempt to update does the same thing again.

Anyone else seeing this?

I just tried it on both my C8 and C7 and both updated without issues.

In the past I’ve had the occasional update issue that was resolved with a pre-update reboot.

Weird. I’ve never had this issue before, but I’ve rebooted several times and it just keeps doing it.

Oh that’s not good. See if you can roll back to your previous installed version via diagnostics, then upgrade directly to .140

Good suggestion, but I tried that and the rollback to .138 was fine, then .140 does the same thing trying to install again. I think there might be something wacky with the package, even if you didn't have trouble with it.

1 Like

You can use the diagnostic tool to "Download latest version" then use the Restore Previous.... button to install it (yes you can update with that button as well).

This will usually get you updated when the normal method gets stuck for whatever reason.

5 Likes

Oh, interesting. Never tried that, will do it now. Stand by!

OK, that didn't work either. I do download latest version, it says it succeeded in downloading and to use restore previous version as you suggested. But when I look there, I only see 2.3.8.138 and 2.3.7.146

So it seems like the diagnostic tool also can't extract the .140 package ¯_(ツ)_/¯

That is weird -- I just did this last night to get to .140, and it worked as advertised.

Strange. It just worked on mine, don't mind 2.3.9 those are bets test builds.
I did not try switching to it, but it did download and show on my list.

Maybe your download got corrupted somehow and is stuck in a cache.

image

What browser are you using?

I use Edge on Mac, and I was having corruption issues trying to create a local backup file (in prep for this update), but updating Edge fixed that... Maybe make sure your browser is updated and try again?

Good suggestion, but I tried 3 browsers (mobile Safari, always worked in the past), full MacOS Safari, and Arc - all with the same results

Yeah, this is what I'm wondering too. I don't know how to clear that though, it must be in the hub itself. I've tried full power cycles aside from the soft reboots I was doing as well, and that didn't help either.

You could try forcing it to download a bunch of older platforms and maybe that will clear it out. Use this endpoint and the number at the end is the major version, so 2.3.4 is 234 as shown.

/hub/advanced/downloadPlatform/234

1 Like

Are the downloads stored in the DB or in the file system? I’m wondering if the OP might benefit from a DB rebuild as part of a reboot.

I gave this a try but these endpoints always seem to time out without doing anything.

I can give that a shot!

1 Like

Doing a reboot with a DB rebuild and a log purge has changed my results, but not much for the better. Now I see it download, verify, extract, and then give this “download failed” message.

Go into network settings on the hub, and change the Ethernet speed setting. If its on AUto set it to 100. If on 100, set to Auto.

image

Then try again.

Tried that, even with another reboot - no difference. Thanks for the idea though!

1 Like