tryphe

> > Syncing works fine until about 95%, or near block 2450000. > > What exactly happens then? > Does it start to ban other peers? The errors and warnings...

One thing I didn't mention, if I continually restart the daemon, it seems to sync a few chunks of 20 blocks upon start, but it only works for a minute...

> Which log level is the log you posted? > > > It's obvious to me that there are some malicious nodes out there just handing me junk blocks. But...

Thanks for your quick feedback. I use the same VM image for several coin daemons, and only Monero has syncing problems, but it's the only cryptonote coin I run. I...

I did a quick dist-upgrade to Debian 11 without rebuilding Monero and the problem seems to have resolved itself. Really strange. No problems now. Why it happens at 95% synced...

Log level 2 after the problem was resolved by upgrading to Debian 11: https://gist.githubusercontent.com/tryphe/fac92713a0fab5aa6a75c6ae40905573/raw/c3262979e8e0f299b290bde46ac096c48cd6e144/gistfile1.txt Thanks again for your feedback @selsta! I can't spot anything in the log that's different. The...

@selsta yes. Ran dist-upgrade, did nothing else, and it's been synced ever since. I upgraded from Buster (Debian 10) which was up to date via apt, so there's a problem...

It started doing it again today and now the node is behind. Will try and make a new machine. And again, none of my other coin daemons have this problem,...

I was able to reproduce the bug with a new KVM instance with Debian 11 amd64 (vm software is up to date, host is up to date). Host is running...

> Is the blockchain stored inside the VM or on an external network drive? > Could you possibly also have a similar service interfering with your blockchain file? The blockchain...