I've been running monerod, and it has been working well for several months. Today I noticed that it had fallen about 10,000 blocks behind. I killed it and restarted it, and called status every few minutes to see what was going on. It was syncing, but it would go for about 100 blocks and then get stuck. I killed it again and restarted it a few times, calling status. Sometimes status would report that it was 100% synced to current blockheight (even though it is not), sometimes it would correctly report that it was behind, but would make little progress. I tried --db-sync-mode fastest:async: (not sure what that does since it's not really documented, but seemed worth a try), but didn't see a difference.

I can't figure out why it would be behaving differently than before, and I don't see a way to fix it. Is there some kind of denial of service attack going on right now? If not, how do I get it caught up again?

  • Sounds like slow/poor peers. You could try, stopping, deleting your /.bitmonero/p2pstate.bin file, starting again. That will forget current peers. If you're not syncing to a spinning disk, shouldn't take long to sync those last blocks. – jtgrassie Aug 26 at 22:30
  • Deleted p2pstate.bin, see no change in behavior. Interestingly, it didn't recreate the p2pstate.bin file. The file remains missing from the ~/.bitmonero directory. Is that significant? – puzzler Aug 26 at 23:19
  • Edit: p2pstate.bin did appear when I exited monerod gracefully rather than killing the process. Each time I restart, it advances a few blocks and then gets stuck. – puzzler Aug 26 at 23:26
  • Deleting --block-sync-size 10 from my command flags seems to be helping. – puzzler Aug 27 at 0:15
  • Well that's new information. Anything other settings you're using? – jtgrassie Aug 27 at 0:57

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.