Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uncaught exception: Error: unit not found: on startup #599

Open
backenders-game opened this issue Mar 1, 2021 · 10 comments
Open

Uncaught exception: Error: unit not found: on startup #599

backenders-game opened this issue Mar 1, 2021 · 10 comments

Comments

@backenders-game
Copy link

I am getting error
Uncaught exception: Error: unit not found: eq6x0xRr+iIXwCn5sSyKagt9/mJNWJefHvRd2NzxEPE=

then wallet closes
Full wallet, latest release

@backenders-game
Copy link
Author

hello @tarmo888 @tonyofbyteball

@tarmo888
Copy link
Member

This is most likely because corrupt database, which most likely happened because loss of power to full node.

Solution: restore earlier backup or restart syncing from scratch by deleting the database.

@backenders-game
Copy link
Author

Thanks for response. I am trying to download full DAG data again

On the other side this is very bad user experience. Now i should download 4 days and 70gb. There should be a way to download missing or faulty chunks .

And it is not clear what to delete and what not from your response

@tarmo888
Copy link
Member

You could also restore the seed words, but I think deleting rocksdb folder and sqlite files should work too.
This is not normal experience, it only happens when you machine stops unexpectedly, normally closing the app would not do that.
For best user experience, GUI wallet makes most sense as light node because it can store private data, which is easier to backup with light node.

If you want a full DAG database then I would suggest running https://github.com/byteball/obyte-relay, which is just a copy of DAG without any keys. If you wish, you can even use it as full node you can relay transactions from GUI wallet. That too is vulnerable to sudden loss of power, but it's easier to keep backups.

@backenders-game
Copy link
Author

I don't really want full DAG, i want to keep my blackbytes from backup. It is possible only with full node, right?

@tarmo888
Copy link
Member

you do not need full DAG for blackbytes, blackbytes are not even stored on DAG. you just need proper backup, not just seed words.

@github4366
Copy link

you just need proper backup, not just seed words.

Hello! How can i get a "proper backup"? To me available only seed or full backup. Full backup backuping all dag (wich i have only 10gb). Because of that when i restore from full backup, wallet starts synching to 50+ gb, wich is lasts too long.
How can i restore from full backup (i have 10 gb) if i want use blackbytes, but without download full dag?

@tarmo888
Copy link
Member

tarmo888 commented Apr 23, 2021

@github4366 if you don't have any other private data (smart-contracts, multisig, attestation profiles) in the wallet other than blackbytes, then you could:

  • restore the 10 GB backup file and then send blackbytes via message (this will create a blackbytes textcoin).
  • delete the app data folder.
  • start the wallet app and pick light node.
  • restore with seed words.
  • open the blackbytes textcoin to retrive the blackbytes from textcoin.
  • make a new backup file (this time it would be a backup of light node).

If you have any other private data then you can't convert full node to light node like this because you seed words only restore public data.

@SY-MEDIA
Copy link

@supernova2033 maybe you're confusing a full-backup of your wallet with full-backup instance of the whole DAG?

@tarmo888
Copy link
Member

That could be because older versions of the wallet app called both (light and full node) backup files as full backups. Latest wallets call it "Backup all wallet data". Obviously, when making a backups, the latest wallet version should be used because there has been fixes to that process too, not just renaming.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants