Skip to main content

Timeline for Daemon stopped syncing

Current License: CC BY-SA 4.0

10 events
when toggle format what by license comment
Mar 25, 2019 at 16:36 vote accept Gian Marco Toso
Mar 25, 2019 at 13:04 answer added jtgrassie timeline score: 2
Mar 25, 2019 at 12:54 comment added jtgrassie Glad it's sorted.
Mar 25, 2019 at 9:13 comment added Gian Marco Toso Hey, it works! I don't know if it was the block-sync-size (I don't think so?) or me banning a couple of slow peers, but it's now syncing correctly. Answer the question with the ban suggestion (which I haven't seen so far as a solution to this kind of problem) so I can mark this as solved!
Mar 25, 2019 at 9:00 comment added Gian Marco Toso Thank you, I'll try and report back. My connection is ~50Mbps and is working otherwise fine (I get around 6MB/s with just about everything else), so I'll start banning peers and see what happens!
Mar 25, 2019 at 0:15 comment added jtgrassie Couple of things: 1) remove --block-sync-size=10, the daemon will use a sane default, 2) ensure there is nothing harming your internet connection speed, 3) you can always check for slow peers by first using the command print_cn and then using ban for any slow ones.
Mar 24, 2019 at 22:27 comment added Gian Marco Toso I believe so, yes. I have done that many times over, unfortunately it does not change much, but it's actually syncing at a very slow pace. I'm now on block 1789410 (after 3 hours). I'm probably having bad luck finding other nodes to sync with, but this has been going on for at least one week and I've been able to resync up to 99.5% without issues.
Mar 24, 2019 at 21:49 comment added jtgrassie Do you still have this problem? What you're describing is usually fixed by killing the daemon, deleting the p2pstate file and relaunching.
Mar 24, 2019 at 18:40 review First posts
Mar 26, 2019 at 17:48
Mar 24, 2019 at 18:37 history asked Gian Marco Toso CC BY-SA 4.0