-
Notifications
You must be signed in to change notification settings - Fork 200
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
ar_header_sync_block_tx_root_mismatch #382
Comments
Hi, I think, you've run into a bug fixed here - could you try this branch? |
So i compiled the fix and let it run for 10 hours.. high cpu and ram usage as usual... but i can not see any difference.. maybe these logs are new.. but probably not related:
|
Could make these requests to your node?
It will force it to validate the index for these chunks (will return 404 if invalid), remove the invalid onces, and subsequently re-sync them. |
Thank you for the feedback! They all worked for me and nothing changed..
|
Ah, my bad, I forgot about the block
Which errors do you still see? |
Ah so maybe this is not related to the problem that you think of. no problem with your mentioned chunks. it is not just three blocks. i see a different block every second..
|
Update on this: The error was fixed after restoring a backup ( no old backup, just one day back ). In Principle not much has changed. But maybe there was a problem with restoring some files, as i see in the last twelve hours thousands of the following messages - and i see that the value of "v2_index_data_size" is slightly shrinking.
But the good news is that the missing blocks could be downloaded. no more ar_header_sync_block_tx_root_mismatch, i could reach 100% blocks. |
Interesting, thank you for the update @ThomasBlock! |
…e 2.7.2 hardfork (#382) When calculating the estimated v2 price, don't start considering the PoA1 difficulty multiple until 21,600 blocks after 2.7.2 activation. Also add a fixed lower bound. Upper bound: 340 Winston per GiB/Minute (or ~0.714 AR per GiB upload) Lower bound: 170 Winston
On one of my nodes the following warning is issued 10 times per second on repeat ( for different blocks ). The node has synced 99,5% of the block headers and new headers are added without problem. But the difference between arweave_storage_blocks_stored and arweave_block_height is always 5057.
2022-08-16T15:29:08.613402+02:00 [warning] /root/arweave/apps/arweave/src/ar_header_sync.erl:484 event: ar_header_sync_block_tx_root_mismatch, block: <<"y0vlt5dHDXB22pf_nqlHlDJfZcAhwadeuFOHTdl_XDeloQTj7h7mGuj76eRCGRvD">> 2022-08-16T15:29:08.847703+02:00 [warning] /root/arweave/apps/arweave/src/ar_header_sync.erl:484 event: ar_header_sync_block_tx_root_mismatch, block: <<"ZicWdamH_9Ii6OmQEoHNo2ygFjTpE1xnlMjzGoBmEMIhQaMWc3DOgwZg82pvr9YZ">> 2022-08-16T15:29:08.966679+02:00 [warning] /root/arweave/apps/arweave/src/ar_header_sync.erl:484 event: ar_header_sync_block_tx_root_mismatch, block: <<"WURgtmYEshWP6fzIgI8_a8oQaAgr7cNPeYQlqaOqzFFSb4w1sOcGqVo6jmN7U3zq">> 2022-08-16T15:29:09.021672+02:00 [warning] /root/arweave/apps/arweave/src/ar_header_sync.erl:484 event: ar_header_sync_block_tx_root_mismatch, block: <<"LfJoAWmGcXh9eY4qBsmramtmqmWWP-3JOU46gyacMrumM742wAbXEY-Ce3WQp3yl">>
So there seems to be a problem with the old headers?.. I have enough storage, bandwidth and peers. I tried to change parameters ( "header_sync_jobs":1 and also "header_sync_jobs":10. i tried "sync_jobs":0 ) but even after 48 hours this does not change a little bit.
I probably could delete the data folder and resync the weave. but is there a way to repair it? rocksdb is still a mystery for me.. could i delete files or edit the db somehow?
The text was updated successfully, but these errors were encountered: