-
Notifications
You must be signed in to change notification settings - Fork 132
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
wallet crashing #236
Comments
Full resync? Do you mean reindex? rescan? Deleting blocks and doing a full new block download? Please provide more specifics. |
same problem here. 2019-10-06 05:09:24 UpdateTip: new best=0000000c5eca6ed4c988cef18da8a702b9784600f3822ad1fd3652814d288b23 height=606789 log2_work=49.791435 tx=56488394 date=2019-09-28 09:36:47 progress=0.998712 cache=10.7MiB(10072tx) |
Reindexing and Rescanning are two way different things. As with the previous post going to need more details.
Also, Please provide a paste of more of the debug.log file, preferably with the debug flag ( debug=1 ) on in the config file so it provides more output. |
I mean downloaded blockchain from scratch by peers |
How long has this node been running prior to issues? Is this node mining or used in a mining pool? Is this node used as an explorer or other backend service node? or just for a local wallet? Have you manually tried to reindex? if so what were the results? Have you manually tried to rescan? if so what were the results? |
How long has this node been running prior to issues? Is this node mining or used in a mining pool? Is this node used as an explorer or other backend service node? or just for a local wallet? Have you manually tried to reindex? if so what were the results? Have you manually tried to rescan? if so what were the results? debug.log: 2019-10-08 00:02:30 UpdateTip: new best=0000000b6d3cfda3d4b79065491076eb31eb052185ebb5b77cd2b71e5586935b height=606791 log2_work=49.791435 tx=56488399 date=2019-09-28 09:40:15 progress=0.998418 cache=18.5MiB(12367tx) |
any update? |
Had the same issue. Made an ugly hack that seems to have worked - it turned out that every time the wallet crashed, it did so after connecting to a node with a fork that was way ahead of us, and then it backpedaled 100 blocks (which is the usual reorg limit for bitcoin-based cryptocurrencies), and then crashed. And every time it did this, the node with the longer fork had the same IP address, 46.101.126.142 (albeit different ports). So I added the line This is only a rapport about what seems to have worked for me, not a recommendation towards how the problem should be permanently solved, and so on and so forth. Do make your own research into which IP addresses the nodes that make you crash have, et cetera. I assume no legal liability for providing this information. :-P |
even after full resync getting
btcpd: wallet/wallet.cpp:803: void CWallet::DecrementNoteWitnesses(const CBlockIndex*): Assertion
nWitnessCacheSize > 0' failed.`
The text was updated successfully, but these errors were encountered: