This is an expected error in case your node received blocks from the network that it can’t verify because they belong to alternative history of the blockchain. When blocks are incorrect node will rightfully complain and reject/ignore them.
The node repeats this message for hours on end. It’s stuck. Can I revert the chain back a couple thousand blocks? If so, how? This node was running fine on the correct chain up until earlier today so I’m surprised this would happen.
If your best block very close to one in explorer then everything works fine and you can just ignore those messages for now.
However I just checked block 188014 and it seems like your node is not on the canonical chain and would require a reset, that explains why when nodes on the network send your node some blocks, node can’t import them.
If what you say is true then this is a huge problem.
Nodes should be able to revert backwards until they find a block they can import correctly and then resume sync from there. Otherwise what you’re saying is that if a node goes off on a fork for whatever reason it’s impossible for it to re-sync back to the correct chain unless it’s completely wiped and restarted from scratch.
There is a “revert” command available on the node. Does this work?
Default instructions are not storing state for blocks deeper than 1024 from the tip of the chain you’re on. In which case it is not possible to switch to a different fork deeper than that. Also we have a process of archiving of the history of the blockchain for blocks at depth of 100 blocks, that essentially also means you can’t revert below that point.
As such we don’t really expect nodes to have deeper forks than 100 blocks, but due to series of circumstances we still have a significant number of nodes on non-canonical chain right now. Good news is that over 50% of nodes are synced on the correct chain and the number of growing, so things are improving quickly.
What should I do? Synchronization has not been restored in the last 12 hours. I updated the version while on block #188014 and I’m still on it. The farmer issued (successfully signed hash of the reward) 6 times during this time, but the reward was not credited after this update.
I had the same issue. I stopped farmer and node. Then I deleted the local “chains” directory and rsynced the “chains” directly from a different node, that I knew was still working local. Then I started node and farmer, and things seems to work.
Idle (40 peers), best: #188014 (0x0014…1da1), finalized #0 (0x9ee8…ccf0), 
4.2MiB/s 
5.5MiB/s
Error importing block 0x6621d6daee09b63e72ee83424b5d648a8c4aad88e6542ae78da72906573bc6c2: consensus error: Import failed: Checking inherents failed: IncorrectRootBlocksList