It’s hard to understand what happened on your node.
Nodes are “desynchronised” several times a day (for a short time) and are resynchronised a few minutes later, automatically.
Around 2020-02-12 14:07:10.541 UTC, your node forged the block 114 721, but it broadcasted it to the “chain” (all other nodes) too slowly.
At the same time, we can indeed see on another node (UTC time):
[2020-02-12 14:07:21.325] DEBUG: Delegate 38025c9fce2ad334d0aa39e7ee6ca4dc166143910533b6dabf187b6a056e90c9 (020f472925e7b07d7dc67ae146cc5342272313918cbd2da92cbf57c95f4a66a85c) just missed a block.
38025c9fce2ad334d0aa39e7ee6ca4dc166143910533b6dabf187b6a056e90c9 is the one running on your node.
Then, it was living on it’s own chain.
At 2020-02-12 16:02:41.442 UTC, it finally discovered it was alone on its own chain and decided to start the fork recovery process (
[2020-02-12 16:02:41.442] INFO : Starting fork recovery). It succeeded.
Then the node synchronized and was SYNC at 2020-02-12 16:02:46 UTC.
It was back to the chain with the others.
- do you have other processes running on this VPS?
- can you monitor the CPU/memory load on your VPS? (systat?)