-
Notifications
You must be signed in to change notification settings - Fork 80
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
Block 23057 WARN, Error occured on chain sync with Peer, Data not found on disk: load data #48
Comments
I took the db from my docker linux environment and continued on a windows machine and it got past this block. After 200 blocks I stopped the windows daemon, copied back the db and it started working in docker from where windows daemon left off. So issue was only in docker linux environment on this block. |
It happened again on block 26504. It is getting stuck on block 26503 and the same error from all peers. |
Have you found a solution to the problem? I am also facing the same issue as you. |
Can you try using dev branch ? Resync from 0, delete mainnet folder and start the daemon and keep me updated |
No, but I did a workaround. I moved the db to a windows client and ran with command --allow-boost-sync |
Where can I find a prebuilt docker image from dev branch? I have downloaded the docker image prebuilt. I don’t know how to build the docker image. |
Some other with the same problem ? |
Yes 173990 stuck block is due to a DAG reorg that made a valid proof into invalid, this will be fixed shortly today. I found the cause and will release the v1.12. If you cant wait, join the discord server and download the backup in support channel. |
Obviously problem is not yet solved. I'm still stucked on block 173990 |
@Slixe I have installed v1.12, the problem persists, I'm still stucked on then block 173990. |
do |
Done but now stucked on block 174007 with the same error (i'm on V1.12) |
try to repeat pop_blocks 10 again. It worked for me |
unfortunately not :/ locked again on block 173990 |
same issue here, locked again on block 173990 after a few pop_blocks (i'm on V1.12) |
Solved it by pop_blocks 20 then exit deamon, start deamon with boost sync, 2 x pop_blocks 20 and sync again ... |
Same issue here, apply the solution above but does not work, still stuck in block 173356 |
delete mainnet folder and do a full resync |
It´s working now, i did the following:
|
How can I do that? I'm on windows so, command line? --> xelis_daemon.exe --pop_blocks 10? it did not work, this command does not exist. Anybody can help me with that? Edit: I figured it out, you do that on the xelis_daemon.exe console when the program is running, you can type pop_blocks 10 in the last line. |
I have tried to sync the blockchain twice now but get stuck on block 23056 and all peers generates the same error:
[2024-04-27] (17:39:57.300) [WARN ] [xelis_daemon::p2p] | Error occured on chain sync with Peer[connection: Connection[peer: ???.???.???.???:2125, read: 130 KiB, sent: 1.9 KiB, key rotation (in/out): (1/1), connected since: 5s, closed: false], id: 1580593161845417619, topoheight: 39745, top hash: 549fd194009b930ea003819240bc8d403f12e68ea2d81f4c2ee67f890270ea29, height: 37760, pruned: No, priority: true, tag: None, version: 1.9.4-6a4e306, fail count: 0, out: true, peers: 0]: Data not found on disk: load data
The text was updated successfully, but these errors were encountered: