print_block 1546123
timestamp: 1523107696
previous hash: d08c3ec178339cdd923183e6fff0dcf52b5b9178bf66d26569e8fd714755fbba
.
.
.
Looks like you're on the right chain. You're either connected to a bad peer (i.e. a peer that is on the wrong (alternative) chain) or a peer that's syncing off of you.
I rolled back using monero-blockchain-import --pop_blocks 18000 then resynchronized. Still a couple of problems. Monerod stopped synchronized several times during the process and I had to exit and restart. I've seen that before but never so often.
It's a known issue unfortunately, see:
https://github.com/monero-project/monero/issues/3656https://github.com/monero-project/monero/issues/3713When I finally got synchronized all seemed fine but now I suddenly have a new top block candidate several hundred blocks in the future to which I am slowly catching up (1 block/2 minutes as expected). Any ideas? Do I have a bad peer? How do I fix that? Thanks in advance.
That's because your daemon is connected to a bad peer (i.e. a peer that is on the wrong (alternative) chain). The daemon should eventually ban this peer though. Alternatively, you can ban it manually by typing "ban <ip-address>" (without quotation marks) into monerod. In addition, a restart may fix this kind of issue.