Mines getting close! Similarly mine crashed around 1.7ish M but the terminal had vanished this Wayland now on 22 I suppose maybe. So a normal restart and picked up where it left off, now almost 98%.
Ah-Ha!
Mines getting close! Similarly mine crashed around 1.7ish M but the terminal had vanished this Wayland now on 22 I suppose maybe. So a normal restart and picked up where it left off, now almost 98%.
Ah-Ha!
Iām having a very similar error v5.2.0. Iām running on arch linux, with:
(
experimentalfeatures=1
txindex=1
insightexplorer=1
)
Iām not aware of the lightwalletd
config option, it doesnāt show up when I run zcash -help
.
When I reindex, it finishes the reindex, and then starts redownloading the chain from the beginning. When I sync most of the chain, shut down, and attempt to reboot without reindexing, I get the assertion failure, and it hangs until I kill -9
it.
The line number has changed, but I suspect itās the same error.
wallet/wallet.cpp:4717: int CWallet::ScanForWalletTransactions(CBlockIndex *, bool, bool): Assertion `uResultHeight == rewindHeight' failed.
LightwalletD is a separate program, The conf slso requires the RPC password and username fields
The example conf mdroid posted about contains that flag, which is why I mentioned it:
experimentalfeatures=1
lightwalletd=1
txindex=1
insightexplorer=1
I do have the rpc password/username fields in my conf, I just didnāt paste them here, theyāre next to a bunch of commented out regtest parameter stuff and I didnāt think theyād effect sync/wallet operations.
Notably, I donāt get this error on testnet (or regtest), and Iāve been able to connect a lightwalletd to it fine on non-mainnet chains.
The current Master branch (to my understanding) contains fixes to zcashd that may be actionable here if youāre still on the original 5.2.0 release.
Great, Iāll give latest a try and see if it fixes it!
Any luck ?
Not exactly! Latest master fails to build for me, an error @dannasessha found a couple months ago. I hadnāt tried to build anything more recent than 5.2.0, so I managed to avoid hitting this before now.