Closed TARS-bot closed 6 years ago
This was on git master f3440f5a20bee6c64f738ffc32010e94ad8c6dab.
It only happened once; so far EDIT: ok, multiple times now.
In log1,
[testnet.qtornado.com] requesting chunk 624
[SPV] merkle verification failed for
verify_chunk failed prev hash mismatch
Why is the client still requesting several chunks backwards? This generally leads to ElectrumX cutting the client off. I was told this was fixed about 9 months ago...
@kyuupichan the 3.1 client will request chunks in random order. I think you should remove this cutting feature from electrumx
@ecdsa OK; it was put in because Electrum would request chunks back to 0 when confused about the chain it was on. This led to huge bandwidth consumption for some servers. If you've fixed the part where it requests them all when confused, and/or spreads the load across all 8 connections, I'm happy to do so, I wasn't a fan of the "feature" in the first place
@ecdsa OK I've removed it. It only was applied to old clients (pre 2.9) anyway, so is now largely ineffective anyway I guess
thanks. if you are concerned about client misbehavior, you could still measure bandwidth consumption and cut if a threshold is reached.
Sometimes it doesn't trigger the assert but not all transactions will get SPV verified when the sync finishes. EDIT: Ok, it's even missing transactions sometimes. (e.g. found 140 instead of 171) It gets resolved after app restart on the follow-up sync...
Such logs:
Note the verify_chunk failed prev hash mismatch
here too; and then it disconnects from the server and connects again.
@SomberNight could that be related to the other issue, of mixing of testnet and mainnet servers?
@ecdsa No, I doubt it. All these are from clean datadirs. And as the first line of logs show, I deliberately specify the server to connect to all the time.
I'll start a new set of logs here because I've reached the comment length limit :D
note lines
[Blockchain] write. truncating to offset 100477440, which is around chunk 623
[testnet.qtornado.com] received chunk 636
[Blockchain] verify_chunk failed. index 636, i 0 / num 2016
Crash Report
This crash report was reported through the automatic crash reporting system 🤖
Traceback
Reporter
This issue was reported by 4 user(s):
Additional Information