DERO blockchain sync problem


#1

Blockchain sync has been fixed in updates, pls update your software before trying following steps.
Sources https://github.com/deroproject/dero
Binary https://github.com/deroproject/dero/releases

After 8 March 2018 you should not be reading this thread for fork issues but just for history.

Incase still DERO blockchain data not syncing.
1] Stop daemon and delete p2pstate.bin file in dero blockchain data folder and restart daemon.
2] Use status command to check daemon.
3] If still not syncing delete dero blockchain data folder and restart daemon.
Windows users can find dero-chain-data folder in their user folder or C:\ProgramData\dero\lmdb. Linux users search for .dero in home folder.

Else for faster sync and if nothing works above due to like low power cpu, net problems:
Stop daemon first, download chain data from http://seeds.dero.io/data.mdb and restart daemon:
Replace data.mdb in .dero/lmdb/ folder Or corresponding folder in windows user.

PLS NOTE : For Pool operators and big solo miners:
Start daemon with following option to add priority seeds to get sync faster with low latency network:
Windows:
derod.exe --add-exclusive-node 89.38.96.169:18090 --add-exclusive-node 89.38.97.110:18090 --add-exclusive-node 212.8.242.60:18090

Linux:
./derod --add-exclusive-node 89.38.96.169:18090 --add-exclusive-node 89.38.97.110:18090 --add-exclusive-node 212.8.242.60:18090


Blockchain synchronization quick fix Mar.4/2018 **Updated**
#2

I tried delete the chaindata file on my pc but still got issue with synchronizing data. Sync issue also happened with options adding several priority nodes . It stop at block 16988 or so every method I tried.
Any reason for that?

Thank you.


#3

Blockchain sync issues have been fixed in new updates.

Download and update latest release:
https://github.com/deroproject/dero


#4

i foolow all of this, include remove db from program data, when i put db from your page, daemon wont start. I try few times, with and without admin rights, the daemon is always few hundreds block behind…

I download the last 0.11.2, try on few computers, and the thing is same…

018-01-17 09:14:58.766 [P2P7] WARN net.dns src/common/dns_utils.cpp:487 WARNING: no two valid DeroPulse DNS checkpoint records were received
2018-01-17 09:15:09.150 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [69.23.133.71:46332 INC] Sync data returned a new top block candidate: 20256 -> 20629 [Your node is 373 blocks (0 days) behind]
SYNCHRONIZATION started

and the wallet is always show 0.000000 balance, please help :wink:


#5

Stop daemon and delete p2pstate.bin file in dero blockchain data folder and restart daemon.
For balance update see : DERO wallet balance update


#6

The same thing…xcept the p2pstate.bin not create in dero folder…

The daemon says…

2018-01-18 08:27:40.541 [P2P7] WARN net.dns src/common/dns_utils.cpp:487 WARNING: no two valid DeroPulse DNS checkpoint records were received
2018-01-18 08:27:42.511 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1543 e[1;33m


You are now synchronized with the network. You may now start dero-wallet-cli.

Use the “help” command to see the list of available commands.
**********************************************************************e[0m
status
Height: 20256/20256 (100.0%) on mainnet, not mining, net hash 1.37 MH/s, v6, up to date, 1(out)+0(in) connections, uptime 0d 0h 1m 30s
2018-01-18 08:30:21.692 [P2P4] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [54.37.75.154:18090 OUT] Sync data returned a new top block candidate: 20256 -> 21073 [Your node is 817 blocks (0 days) behind]
SYNCHRONIZATION started
2018-01-18 08:31:10.417 [P2P6] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [84.242.74.251:18090 OUT] Sync data returned a new top block candidate: 20256 -> 21074 [Your node is 818 blocks (0 days) behind]
SYNCHRONIZATION started
2018-01-18 08:31:56.727 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [54.37.75.154:18090 OUT] Sync data returned a new top block candidate: 20256 -> 21074 [Your node is 818 blocks (0 days) behind]
SYNCHRONIZATION started

And the wallet says…

Use “help” command to see the list of available commands.


Starting refresh…
Refresh done, blocks received: 0
Balance: 0.000000000000, unlocked balance: 0.000000000000
Background refresh thread started
[wallet dERoUe]: status
Refreshed 20256/20256, synced, daemon RPC v1.13
[wallet dERoUe]: set refresh-from-block-height 1
Wallet password: ************
[wallet dERoUe]: refresh
Starting refresh…
Refresh done, blocks received: 0
Balance: 0.000000000000, unlocked balance: 0.000000000000
[wallet dERoUe]: rescan_bc
Starting refresh…
Refresh done, blocks received: 20255
Balance: 0.000000000000, unlocked balance: 0.000000000000
[wallet dERoUe]: balance
Balance: 0.000000000000, unlocked balance: 0.000000000000
[wallet dERoUe (out of sync)]:


#7

stop derod.exe daemon and Look for p2pstate.bin in C:\ProgramData\dero\ folder or your user home dir and delete it.
Start derod.exe .


#8

That exactly what i am do…and no sync, maybe on next release…:wink:


#9

Can you pls elaborate your OS, NW, Firewall etc.
OR
Come over to slack for realtime support.


#10

No problem… it is win 10, the block always go to the some number a few hundred blocks from last block. In version before thay stop on 17xxx, the highest block in that case has been 20xxx. I download version 11, and the things is same, after that i delete complete folder dero in Programdata, and run new version and they reach 20256, in that time block was 20578. The new version is back to me that realtime block is increasing but not sync in daemon. I add dero in firewall for tcp and udp in inbound and outbound rules, i manualy stop firewall daemon just to check…same things.

This is log of derodaemon, start when i typing…

You are now synchronized with the network. You may now start dero-wallet-cli.

Use the “help” command to see the list of available commands.
**********************************************************************e[0m
2018-01-18 20:49:55.032 [P2P6] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [54.37.75.154:18090 OUT] Sync data returned a new top block candidate: 20256 -> 21325 [Your node is 1069 blocks (0 days) behind]
SYNCHRONIZATION started
2018-01-18 20:51:36.355 [P2P8] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [54.37.75.154:18090 OUT] Sync data returned a new top block candidate: 20256 -> 21325 [Your node is 1069 blocks (0 days) behind]
SYNCHRONIZATION started
2018-01-18 20:52:34.044 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [79.103.4.83:18090 OUT] Sync data returned a new top block candidate: 20256 -> 21325 [Your node is 1069 blocks (0 days) behind]
SYNCHRONIZATION started
2018-01-18 20:53:56.826 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [114.141.52.20:60707 INC] Sync data returned a new top block candidate: 20256 -> 21325 [Your node is 1069 blocks (0 days) behind]
SYNCHRONIZATION started
2018-01-18 20:54:52.299 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [54.37.75.154:18090 OUT] Sync data returned a new top block candidate: 20256 -> 21325 [Your node is 1069 blocks (0 days) behind]
SYNCHRONIZATION started
2018-01-18 20:55:51.088 [P2P4] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [54.37.75.154:18090 OUT] Sync data returned a new top block candidate: 20256 -> 21325 [Your node is 1069 blocks (0 days) behind]
SYNCHRONIZATION started
2018-01-18 20:58:35.234 [P2P8] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [79.103.4.83:18090 OUT] Sync data returned a new top block candidate: 20256 -> 21325 [Your node is 1069 blocks (0 days) behind]
SYNCHRONIZATION started
2018-01-18 21:02:42.002 [P2P3] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [176.63.179.222:18090 OUT] Sync data returned a new top block candidate: 20256 -> 20340 [Your node is 84 blocks (0 days) behind]
SYNCHRONIZATION started
2018-01-18 21:02:42.328 [P2P3] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [54.37.75.154:18090 OUT] Sync data returned a new top block candidate: 20256 -> 21325 [Your node is 1069 blocks (0 days) behind]
SYNCHRONIZATION started
2018-01-18 21:03:40.444 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [176.63.179.222:18090 OUT] Sync data returned a new top block candidate: 20256 -> 20340 [Your node is 84 blocks (0 days) behind]
SYNCHRONIZATION started
2018-01-18 21:04:00.757 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [54.37.75.154:18090 OUT] Sync data returned a new top block candidate: 20256 -> 21325 [Your node is 1069 blocks (0 days) behind]
SYNCHRONIZATION started
2018-01-18 21:04:58.600 [P2P4] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [176.63.179.222:18090 OUT] Sync data returned a new top block candidate: 20256 -> 20340 [Your node is 84 blocks (0 days) behind]
SYNCHRONIZATION started
2018-01-18 21:05:09.719 [P2P8] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [79.103.4.83:18090 OUT] Sync data returned a new top block candidate: 20256 -> 21325 [Your node is 1069 blocks (0 days) behind]
SYNCHRONIZATION started
2018-01-18 21:06:27.743 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [176.63.179.222:18090 OUT] Sync data returned a new top block candidate: 20256 -> 20340 [Your node is 84 blocks (0 days) behind]
SYNCHRONIZATION started
2018-01-18 21:06:38.770 [P2P2] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [79.103.4.83:18090 OUT] Sync data returned a new top block candidate: 20256 -> 21325 [Your node is 1069 blocks (0 days) behind]
SYNCHRONIZATION started

If you see, thay work for comunication for realtimeblock and get numbers, they tray a sync from 20.49h to 21.06h, nothing has changed.

If you want, pm me i get you access…


#11

Updated. Download latest builds.
https://github.com/deroproject/dero/releases/download/v0.11.3/dero-windows-amd64.zip
https://github.com/deroproject/dero/releases/download/v0.11.3/dero-linux-amd64.tar.gz


#12

This version works…thx :wink:


#13

Hy, im using win 10. I started daemon he sync until some point and now he gives this:

SYNCHRONIZATION started
2018-01-27 12:27:43.235 [P2P7] INFO global src/cryptonote_core/blockchain.cpp:1425 e[1;32m###### REORGANIZE on height: 24250 of 24250 with cum_difficulty 2874402389293
alternative blockchain size: 1 with cum_difficulty 2874446250938e[0m
2018-01-27 12:27:43.442 [P2P7] INFO global src/cryptonote_core/blockchain.cpp:1425 e[1;32m###### REORGANIZE on height: 24250 of 24250 with cum_difficulty 2874402389293
alternative blockchain size: 1 with cum_difficulty 2874446250938e[0m
2018-01-27 12:27:43.490 [P2P7] ERROR blockchain src/cryptonote_core/blockchain.cpp:1406 insertion of new alternative block returned as it already exist
2018-01-27 12:27:43.491 [P2P7] ERROR blockchain src/cryptonote_core/blockchain.cpp:878 Failed to push ex-main chain blocks to alternative chain
2018-01-27 12:27:43.492 [P2P7] WARN blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:2674 WARNING: batch transaction mode already enabled, but asked to enable batch mode
2018-01-27 12:27:43.520 [P2P7] INFO global src/cryptonote_core/blockchain.cpp:893 e[1;32mREORGANIZE SUCCESS! on height: 24250, new blockchain size: 24251e[0m
2018-01-27 12:27:43.520 [P2P7] WARN blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:2674 WARNING: batch transaction mode already enabled, but asked to enable batch mode
2018-01-27 12:27:43.549 [P2P7] INFO global src/cryptonote_core/blockchain.cpp:893 e[1;32mREORGANIZE SUCCESS! on height: 24250, new blockchain size: 24251e[0m


#14

I cant find the dero blockchain data folder…

edit: Ok i found p2pstate deleted and i get the same thing


#15

Windows users can find dero-chain-data folder in their user folder or C:\ProgramData\dero\lmdb. Linux users search for ~/.dero/lmdb/ in home folder.

Also you can search for file data.mdb in your drive, it should be in lmdb folder. Replace it with http://seeds.dero.io/data.mdb


#16

Fixed. I deleted the blockchain folder and re-sync. Thanks !!!


Daemon still stuck at block (even after resyncing, deleting p2pstate.bin and downloading the latest binaries)
Daemon still stuck at block (even after resyncing, deleting p2pstate.bin and downloading the latest binaries)
#18

Pls update your daemon https://github.com/deroproject/dero

Download linux pre-compiled daemon from https://github.com/deroproject/dero/releases/download/v0.11.5/derod_linux_amd64_v5.tar.xz

Run you daemon with following option atm:
derod --add-exclusive-node 89.38.97.110:18090
Windows pre-compiled binary will be updated in next few hrs.

Follow twitter for updates.
https://twitter.com/DeroProject


#19

and for windows? i took the daemon from the “March 3 fix” posted by Serena but the daemon get stuck here :

2018-03-04 10:14:44.709 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [23.240.57.0:18090 OUT] Sync data returned a new top block candidate: 41900 -> 42009 [Your node is 109 blocks (0 days) behind]
SYNCHRONIZATION started
2018-03-04 10:15:37.583 [P2P3] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [23.240.57.0:18090 OUT] Sync data returned a new top block candidate: 41900 -> 42009 [Your node is 109 blocks (0 days) behind]
SYNCHRONIZATION started
2018-03-04 10:18:18.508 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [23.240.57.0:18090 OUT] Sync data returned a new top block candidate: 41900 -> 42009 [Your node is 109 blocks (0 days) behind]
SYNCHRONIZATION started

i delete the p2pstate and data 2x times but still the same. Thank you


#20

Hello Lez,

I’m sorry that the daemon is causing you troubles. The Windows pre-compiled binary will be available very shortly which should help resolve this problem.

If you’re able to hold tight for just a little longer until the Windows version is available it should help clear up some of the errors you’re seeing.

I’ll stick with you until we get this sorted out :slight_smile:

Regards,
Serena


#21

Ok np, im not in a hurry just saying :slight_smile: and thank you for your answer