WalletWasabi: Wasabi wallet not loading - P2pBlockProvider (290)
General Description
After performing some coinjoins and closing Wasabi, i can’t open my wallet anymore.
I’ve restore this wallet, but the restored wallet still with the same problem.
Other wallets opens fine.
How To Reproduce?
- Start ./wassabee with default configuration
- Try to open my Wallet
Screenshots
Operating System
Manjaro 20.0
Logs
2020-05-16 08:00:46 INFO Program (43) Wasabi GUI started (47e541y7-72bc-4b3f-97ec-34345a4c718x).
2020-05-16 08:00:53 INFO Global (396) AddressManager did not exist at /home/zeno/.walletwasabi/client/AddressManager/AddressManagerMain.dat. Initializing new one.
2020-05-16 08:00:53 INFO TransactionStore (29) MempoolStore.InitializeAsync finished in 174 milliseconds.
2020-05-16 08:00:53 INFO TransactionStore (29) ConfirmedStore.InitializeAsync finished in 147 milliseconds.
2020-05-16 08:00:53 INFO TorProcessManager (251) Starting Tor monitor…
2020-05-16 08:00:53 INFO Global (168) TorProcessManager is initialized.
2020-05-16 08:00:53 INFO AllTransactionStore (28) InitializeAsync finished in 236 milliseconds.
2020-05-16 08:00:53 INFO TorProcessManager (75) Tor is already running.
2020-05-16 08:01:18 INFO IndexStore (45) InitializeAsync finished in 25 seconds.
2020-05-16 08:01:18 INFO BitcoinStore (39) InitializeAsync finished in 25 seconds.
2020-05-16 08:01:18 INFO HostedServices (51) Started Software Update Checker.
2020-05-16 08:01:19 INFO Global (290) Start connecting to nodes…
2020-05-16 08:01:19 INFO Global (314) Start synchronizing filters…
2020-05-16 08:01:39 INFO ClientState (470) Round (21239) added.
2020-05-16 08:01:39 INFO ClientState (470) Round (21240) added.
2020-05-16 08:01:39 INFO WalletManager (192) Starting Wallet…
2020-05-16 08:01:39 INFO CoinJoinClient (133) CoinJoinClient is successfully initialized.
2020-05-16 08:01:47 INFO P2pBlockProvider (290) Disconnected node: fd87:d87e:eb43:e47:27c5:3f4x:87d2:f6b4, because block download failed: Not loaded! Use LoadAsync() first!.
2020-05-16 08:01:55 INFO P2pBlockProvider (290) Disconnected node: fd87:d87e:eb43:790a:dcc9:73:5a5x:11d1, because block download failed: Not loaded! Use LoadAsync() first!.
2020-05-16 08:02:06 INFO P2pBlockProvider (290) Disconnected node: fd87:d87e:eb43:9d2c:9fa6:9c9x:bbbe:75e6, because block download failed: Not loaded! Use LoadAsync() first!.
2020-05-16 08:02:10 INFO P2pBlockProvider (290) Disconnected node: fd87:d87e:eb43:9d2c:9fa6:9c9x:bbbe:75e6, because block download failed: Not loaded! Use LoadAsync() first!.
2020-05-16 08:02:13 WARNING Global (145) Process was signaled for killing.
Wasabi Version
2020-05-17 09:07:05 INFO WalletManager (30) .ctor finished in 1 seconds. 2020-05-17 09:07:05 INFO Global (79) .ctor finished in 3 seconds. Wasabi Client Version: 1.1.11.1 Compatible Coordinator Version: 3 Compatible Bitcoin Core and Bitcoin Knots Versions: 0.19.1 Compatible Hardware Wallet Interface Version: 1.1.0
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 16 (3 by maintainers)
This following error message suggests that your
~/.walletwasabi/client/RuntimeParams.jsonis corrupted.Please delete the file and try again.
Nailed it! Problem solved!
Thank you so much @lontivero, @MaxHillebrand and @yahiheb!
You mean when you load that specific wallet the number of peers drops to 0? If you are using v1.1.11.1 this shouldn’t happen.
This is odd… in https://github.com/zkSNACKs/WalletWasabi/pull/3573, @lontivero implemented that there are a minimum of two peers left, and that these two are not disconnected even if block download fails. AFAIK, this made it in the v1.1.11.1 release which you are running…
And since tor is running / the error persists when tor is turned off, then this is no tor issue neither…
Could you please try to build the source code and see if it is fixed?