I have been running several vNodes for several months, but lately I have had 1 that stoped syncing chain and upon further inspection it started to just reboot the docker image continuously. For simplicity, I just deleted the data folder and restarted the vNode and it seemed to sync back up fine.
I have another vNode on the same machine that is starting to do the same thing. I open the log file and saw this set being repeated over and over:
NumCPU 4
2021-01-09 01:31:02.296 incognito.go:95 [INF] Server log: Version 1.19.0-beta
2021-01-09 01:31:03.919 engine.go:173 [INF] Consensus log: CONSENSUS: NewConsensusEngine
encoded libp2p key: XXXX (I removed this key for forums)
2021-01-09 01:31:03.935 host.go:88 [INF] Peerv2 log: selfPeer: XXXX(removed this key for orum) 0.0.0.0 9436
2021-01-09 01:31:06.616 blockchain.go:122 [INF] BlockChain log: Init Beacon View height 936798
2021-01-09 01:31:07.967 blockchain.go:143 [INF] BlockChain log: Init Shard View shardID 0, height 925168
2021-01-09 01:31:09.178 blockchain.go:143 [INF] BlockChain log: Init Shard View shardID 1, height 841303
2021-01-09 01:31:10.281 blockchain.go:143 [INF] BlockChain log: Init Shard View shardID 2, height 290958
2021-01-09 01:31:11.454 blockchain.go:143 [INF] BlockChain log: Init Shard View shardID 3, height 826041
2021-01-09 01:31:12.756 blockchain.go:143 [INF] BlockChain log: Init Shard View shardID 4, height 907671
block <nil>
2021-01-09 01:31:12.757 incognito.go:154 [WRN] Server log: Gracefully shutting down the btc database...
2021-01-09 01:31:12.769 panic.go:679 [WRN] Server log: Shutdown complete
any idea what would be causing the “block <nil>” and/or how to solve this?