Skip to content
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

Open
mrhedstrom opened this issue Apr 27, 2024 · 24 comments

Comments

@mrhedstrom
Copy link

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

@mrhedstrom
Copy link
Author

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.
I'm running docker version v1.9.3

@mrhedstrom
Copy link
Author

It happened again on block 26504. It is getting stuck on block 26503 and the same error from all peers.

@Catjrrey
Copy link

Have you found a solution to the problem? I am also facing the same issue as you.

@Slixe
Copy link
Member

Slixe commented Apr 28, 2024

Can you try using dev branch ? Resync from 0, delete mainnet folder and start the daemon and keep me updated

@mrhedstrom
Copy link
Author

No, but I did a workaround. I moved the db to a windows client and ran with command --allow-boost-sync
When the whole blockchain was synced I moved the db back to the data mount of my docker and started the daemon.

@mrhedstrom
Copy link
Author

Can you try using dev branch ? Resync from 0, delete mainnet folder and start the daemon and keep me updated

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.

@Neomail2
Copy link

Neomail2 commented May 21, 2024

Hello, same problem for me on windows daemon
image
i already deleted the directory "mainnet" but every time it download all the blockchain it stop with that error on that same block 173 990 (i did already 3 times)

Any idea ?

@Airlineben
Copy link

Hello, same problem for me on windows daemon image i already deleted the directory "mainnet" but every time it download all the blockchain it stop with that error on that same block 173 990 (i did already 3 times)

Any idea ?

I am the same. Glad to know I am not the only one.

@Neomail2
Copy link

Some other with the same problem ?

@CEOuysal
Copy link

Xelis error

same problem !

@solopool
Copy link

@Neomail2 @Catjrrey same problem on height: 163451 and topoheight: 173990 with --allow-boost-sync and without it.

xel

@Slixe
Copy link
Member

Slixe commented May 23, 2024

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.

@SammyBoySLO
Copy link

Obviously problem is not yet solved. I'm still stucked on block 173990

@KarelVydra
Copy link

@Slixe I have installed v1.12, the problem persists, I'm still stucked on then block 173990.

@Slixe
Copy link
Member

Slixe commented May 25, 2024

do pop_blocks 10 then let it sync again

@Neomail2
Copy link

Neomail2 commented May 25, 2024

Done but now stucked on block 174007 with the same error (i'm on V1.12)

@KarelVydra
Copy link

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

@Neomail2
Copy link

unfortunately not :/ locked again on block 173990

@TRam-7
Copy link

TRam-7 commented May 26, 2024

same issue here, locked again on block 173990 after a few pop_blocks (i'm on V1.12)

@TRam-7
Copy link

TRam-7 commented May 26, 2024

Solved it by pop_blocks 20 then exit deamon, start deamon with boost sync, 2 x pop_blocks 20 and sync again ...

@JRodb
Copy link

JRodb commented May 26, 2024

Same issue here, apply the solution above but does not work, still stuck in block 173356

@Slixe
Copy link
Member

Slixe commented May 26, 2024

delete mainnet folder and do a full resync

@JRodb
Copy link

JRodb commented May 26, 2024

It´s working now, i did the following:

  • Download the latest version as mentioned above
  • Delete the mainnet folder
  • Start the daemon as full-sync
  • When get stuck in the block, pop_blocks 20 twice

@7runks
Copy link

7runks commented May 28, 2024

do pop_blocks 10 then let it sync again

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests