How to update Chia Gui?

I believe thats incorrect, your syncing the v1 db, its not going to magically convert to v2, you need to run the command.

You could have just synced the v2, but how to do that is beyond me.

Your a fringe case as i think most others updated for the hard fork , so probably very few if any jumped as many versions as you.

Id let the v1 finish syncing, copy it somewhere, uninstall .5.0 , install .3.3 copy the v1 db to the correct place, then run the db upgrade command again.

.3.3 is working fine and your fine to stay on it.

Or you can close the gui, and do as described above, and run the db upgrade with what you already synced so far , before letting it sync, then sync it, both should work in theory.

I thought I was rebuilding the database file (v2) from scratch (because I started from 0/2,468,972) according to the status in the full node tab of the Chia Gui v1.5.0. just by letting the chia gui run and have it fully synced, is this not possible and wouldn’t it work without the need for the v1 database?

I do copied my database file (v1) in a backup location before doing all of this and it was fully synced, so I can do what you suggest:

Id let the v1 finish syncing, copy it somewhere, uninstall .5.0 , install .3.3 copy the v1 db to the correct place, then run the db upgrade command again.

I’ll be downgrading back to 1.3.3 if that’s the case.

1 Like

That should be your fastest solution.

I converted my db on 3.3 and it worked flawlessly.

2 Likes

Thanks anyhow.
But I guess I’ll take the slow route first since I’m already at .5.0, and see if there are any issues. I’m willing to wait. I’m already at 236,244/2,468,972 in just 2 hrs.

If I do bump into an issue, I’ll do your suggestion

1 Like

If you have a up to date copy of v1 your wasting your time, but do as you like.

Id quit, uninstall, install .3.3 copy your v1 over then run the upgrade , its that or waste a day, syncing slows as the chain gets higher due to more data being on the chain.

1 Like

You can tell by the fact your current v1 is bigger than v2, your syncing v1, of which you already have an up to date copy.
Kinda pointless imho.

Yep.
But I feel like version hopping from .3.3 to .5.0 might give me problems too. I just got too apprehensive back last year when I read people having a ton of problems when updating.
I just feel comfortable at 0.5.0 already or there might be major improvements in 0.5.0 compared to 0.3.3 (sorry haven’t fully read the changelog).
My chia install is on a SSD at least.

But your syncing the v1, and .5.0 wont let you upgrade it.

The compression is no where near the figures you listed, im sure your syncing v1!

Keep an eye on the size if your v1, if it keeps growing, your wasting time for no reason, but do as you wish.

Keep an eye on the size if your v1, if it keeps growing, your wasting time for no reason, but do as you wish.

My v1 is still the same. 146 GB
My v2 is now 1.49 GB, it increased.

So I really am syncing my v2 :slight_smile:
I believe this is reflected also in config.yaml, I have made sure that both the full node and the wallet points to the v2 db, and not v1. It was already v2 in config.yaml by the time I installed Chia version 0.5.0

Maybe just a side hunch. The reason why chia upgrade db didn’t work for me was because config.yaml was pointing to v2 and not v1. But at this point I feel tired testing, I better rest.

Ok, well do ss you please and possibly your correct, but i dont get why your v1 is there at all if its not syncing.

Also the db upgrade is superfast vs downloading the whole chain.

1 Like

I have the same problem. It usually pops up after I try using that computer for viewing movies (Prime, Netflix, etc.). I had the problem prior to 1.5.0, and it didn’t change much after the upgrade.

1 Like