zec stoped on 100%,what’s problem?
my friends have same one
it’s been 2 hours …
What version of ZecWallet is this?
ZecWallet ：0.9.13.0
It looks like it is stalled after the latest upgrade. This seems like a zcashd issue. It seems you have the latest version, so I would try the following:
- Restart Zecwallet and see if it helps.
- Are there any clues in the debug.log (On windows, it is in %APPDATA%/Zcash/debug.log).
- Try starting zcashd manually from the command line, and see if there are any errors.
1 Like
Bear with me, trying to reproduce (to see whether this affects all ZecWallet installations or is specific to your installation).
My ZecWallet worked fine through the upgrade
2 Likes
Me as well though Im away from it right now and cant check, It always seems to run more smoothly for me if its run as admin
This is the error the user is getting:
2020-07-16 16:21:50 UpdateTip: new best=00000000006e4d348d0addad1b43ae09744f9c76a0724be4a3f5e08bdb1121ac height=903001 bits=469928528 log2_work=57.824666 tx=6692823 date=2020-07-16 10:57:29 progress=0.999613 cache=195.0MiB(22517tx)
2020-07-16 16:21:50 ERROR: ConnectBlock(): block's hashLightClientRoot is incorrect (should be history tree root)
2020-07-16 16:21:50 Misbehaving: 47.254.69.198:8233 (0 -> 100) BAN THRESHOLD EXCEEDED
2020-07-16 16:21:50 InvalidChainFound: invalid block=00000000023d6d39c951569067798e7df7cf162654bf570f86a323e3f60a3892 height=903002 log2_work=57.824668 date=2020-07-16 10:57:34
2020-07-16 16:21:50 InvalidChainFound: current best=00000000006e4d348d0addad1b43ae09744f9c76a0724be4a3f5e08bdb1121ac height=903001 log2_work=57.824666 date=2020-07-16 10:57:29
Does anyone know what’s happening here? @daira
These lines mean that the node is seeing a block from a peer that didn’t upgrade, and has (correctly) banned that peer. I don’t know whether that’s causing the problem; it shouldn’t.
Is it possible that the user has connections only to nodes that have not upgraded, and so can’t get the next block (because it has no connections to upgraded nodes)?
In that case, maybe we should ask the user to delete peers.dat, so that it refetches the seeds and connections?
3 Likes
I have this problem as well; but run 2 nodes. The default node with no special options worked fine while my node with options like experimentalfeatures, txindex, insightexplorer, and paymentdisclosure stopped working. I tried disabling tor and connecting to my other local node that was updating with no success. As a test, I have created a new system to re-download and verify the entire chain with those options to see if it hangs again - looks like it will take until the morning. Will let you all know if there is any success.
I should have reviewed the logs first…
2020-07-16 12:29:11 UpdateTip: new
best=00000000006e4d348d0addad1b43ae09744f9c76a0724be4a3f5e08bdb1121ac height=903001 bits=469928528 log2_work=57.824666 tx=6692823 date=2020-07-16 10:57:29 progress=0.999891 cache=127.6MiB(14603tx)
2020-07-16 12:29:11 ERROR: ConnectBlock(): block's hashLightClientRoot is incorrect (should be history tree root)
2020-07-16 12:29:11 InvalidChainFound: invalid block=00000000023d6d39c951569067798e7df7cf162654bf570f86a323e3f60a3892 height=903002 log2_work=57.824668 date=2020-07-16 10:57:34
2020-07-16 12:29:11 InvalidChainFound: current best=00000000006e4d348d0addad1b43ae09744f9c76a0724be4a3f5e08bdb1121ac height=903001 log2_work=57.824666 date=2020-07-16 10:57:29
2020-07-16 12:29:11 ERROR: ConnectTip(): ConnectBlock 00000000023d6d39c951569067798e7df7cf162654bf570f86a323e3f60a3892 failed
2020-07-16 12:29:11 InvalidChainFound: invalid block=00000000023d6d39c951569067798e7df7cf162654bf570f86a323e3f60a3892 height=903002 log2_work=57.824668 date=2020-07-16 10:57:34
2020-07-16 12:29:11 InvalidChainFound: current best=00000000006e4d348d0addad1b43ae09744f9c76a0724be4a3f5e08bdb1121ac height=903001 log2_work=57.824666 date=2020-07-16 10:57:29
2020-07-16 12:29:12 ERROR: AcceptBlockHeader: block is marked invalid
2020-07-16 12:29:12 ERROR: invalid header received
Based on these entries, it looks like the issue has already been found… See
and
Which indicate a problem with the previously validated data or a code problem in the embedded zcashd. A reindex may be needed (or possibly disabling some options, thus requiring a reindex).
I deleted the file peers.dat
Disconnected the connection via TOR
It didn’t help.
ERROR: ConnectBlock(): block’s hashLightClientRoot is incorrect (should be history tree root)
Re-indexing with the same options and/or re-downloading the entire chain did not work. I am now testing disabling options 1 by 1 to narrow the problem down. Of course it requires a re-index so this may take some time.
00000000023d6d39c951569067798e7df7cf162654bf570f86a323e3f60a3892 is the correct hash for block 903002 on the consensus chain. So the problem is definitely due to your node’s rejection of this block. We haven’t been able to reproduce this so far.
I can now reproduce this issue 100% of the time on Windows. Issue here: zcashd on Windows (x86_64-w64-mingw32) doesn't sync past 903001 · Issue #4620 · zcash/zcash · GitHub
zcashd.exe doesn’t sync past block 903001
cc @daira
2 Likes
I also have the full copy of the zcash folder where this happens, if it will be helpful for debugging.
good afternoon everyone ran into the same problemma. at the moment that coins were being transferred to me. translation is frozen. I wanted to put a light version of the wallet and insert the key. but it doesn’t work out. please help
Confirmed as well. ZecWallet Full Node 0.9.3 - Windows 10 x64 2004 - July Updates. Haswell-E CPU.
Complete blockchain re-download with no special options (all defaults used) results in the same reported problem. Was going to try building 3.1.0-rc2 win32 source but it looks like adityapk00 already tried. Will bring up other discoveries at zcashd on Windows (x86_64-w64-mingw32) doesn't sync past 903001 · Issue #4620 · zcash/zcash · GitHub if applicable.
1 Like