Node banning all peers

Tech Support
1

While I was in the middle of a transaction I interrupted the connection. Now it seems like my node thinks all other peers want to pass me bad blocks and keeps banning everyone. What can I do?
From the log:
…
Already Spent: Commitment(08eb9540db33d56ae34aabc6f63df55e190d64bafd29b82b2e26d9764e901b9587) }
20190127 21:30:54.541 DEBUG grin_servers::common::adapters - process_block: block 0000013fe8ff refused by chain: Other Error: Error { inner:

Already Spent: Commitment(08eb9540db33d56ae34aabc6f63df55e190d64bafd29b82b2e26d9764e901b9587) }
20190127 21:30:54.542 DEBUG grin_p2p::protocol - handle_payload: received block: msg_len: 4419
20190127 21:30:54.546 DEBUG grin_servers::grin::sync::body_sync - block_sync: 16942/17362 requesting blocks [0000013fe8ff] from 1 peers
20190127 21:30:54.546 DEBUG grin_p2p::peer - Requesting block 0000013fe8ff from peer 47.101.166.239:13414.
20190127 21:30:54.559 DEBUG grin_servers::grin::sync::body_sync - body_sync: no pending block request, asking more
20190127 21:30:54.559 DEBUG grin_chain::chain - body_sync: body_head - 000001dd314a, 16942, header_head - 000004849f4d, 17362, sync_head - 000004849f4d, 17362
20190127 21:30:54.565 DEBUG grin_servers::grin::sync::body_sync - block_sync: 16942/17362 requesting blocks [0000013fe8ff] from 1 peers
20190127 21:30:54.565 DEBUG grin_p2p::peer - Requesting block 0000013fe8ff from peer 47.101.166.239:13414.
20190127 21:30:54.565 DEBUG grin_servers::grin::sync::body_sync - Skipped request to 47.101.166.239:13414: Send(“sending on a full channel”)
20190127 21:30:54.577 DEBUG grin_servers::grin::sync::body_sync - body_sync: no pending block request, asking more
20190127 21:30:54.577 DEBUG grin_chain::chain - body_sync: body_head - 000001dd314a, 16942, header_head - 000004849f4d, 17362, sync_head - 000004849f4d, 17362
20190127 21:30:54.584 DEBUG grin_servers::grin::sync::body_sync - block_sync: 16942/17362 requesting blocks [0000013fe8ff] from 1 peers
20190127 21:30:54.584 DEBUG grin_p2p::peer - Requesting block 0000013fe8ff from peer 47.101.166.239:13414.
20190127 21:30:54.584 DEBUG grin_servers::grin::sync::body_sync - Skipped request to 47.101.166.239:13414: Send(“sending on a full channel”)
20190127 21:30:54.596 DEBUG grin_servers::grin::sync::body_sync - body_sync: no pending block request, asking more
20190127 21:30:54.596 DEBUG grin_chain::chain - body_sync: body_head - 000001dd314a, 16942, header_head - 000004849f4d, 17362, sync_head - 000004849f4d, 17362
20190127 21:30:54.599 DEBUG grin_p2p::conn - Connection close with 114.24.27.168:3414 initiated by us
20190127 21:30:54.646 DEBUG grin_servers::common::adapters - Received block 0000013fe8ff at 16943 from 47.101.166.239:13414 [in/out/kern: 2/5/3] going to process.
20190127 21:30:54.646 DEBUG grin_p2p::peers - Received a bad block 0000013fe8ff from 47.101.166.239:13414, the peer will be banned
20190127 21:30:54.653 DEBUG grin_p2p::conn - Connection close with 47.101.166.239:13414 initiated by us
20190127 21:30:54.881 WARN grin::cmd::server - Shutting down…
20190127 21:30:55.882 WARN grin::cmd::server - Shutdown complete.

2

Well, my moderate technical skills only got me to deleting ~/.grin/main/lmdb, which will cause my machine to revalidate the entire chain (~5min) and got me back running again. I guess there should be a better solution.