Error during sync --nostop in 1.0.1 Release: Failed to handle [headers] message : Revert failed to produce correct last hash :

I get this error and it retries forever:

in client sync --nostop:
verbose 2021/04/14[32]23:34:00 handlers/headers.go:114 Header (not next) : 00000000000000000469d2f45d772c015e7ec29de23b0bc6452dabb90c63edce, subsystem: “SpyNode”
verbose 2021/04/14[32]23:34:00 handlers/headers.go:114 Header (not next) : 000000000000000004298f427af5306b8c01e3530868a297c68f1bb2e63580c2, subsystem: “SpyNode”
verbose 2021/04/14[32]23:34:00 handlers/headers.go:114 Header (not next) : 000000000000000004d25c749786f791d23bb73a93dee0aa6e86cde0a854421f, subsystem: “SpyNode”
verbose 2021/04/14[32]23:34:00 handlers/headers.go:114 Header (not next) : 0000000000000000055c6ccc26fd8f3c871919b7aed2b5c8f687b416c7483473, subsystem: “SpyNode”
info 2021/04/14[32]23:34:00 handlers/headers.go:127 Header previous block : 000000000000000004d25c749786f791d23bb73a93dee0aa6e86cde0a854421f, subsystem: “SpyNode”
info 2021/04/14[32]23:34:00 handlers/headers.go:130 Reorging to height 682960, subsystem: “SpyNode”
warn 2021/04/14[32]23:34:00 spynode/node.go:720 Failed to handle [headers] message : Revert failed to produce correct last hash : 0000000000000000040c574787ed1e3b578a8fc3d9be4213b09af4a3e1433afb, subsystem: “SpyNode”
error 2021/04/14[32]23:35:00 spynode/node.go:947 SpyNodeFailed timeouts : Headers request took longer than 60 seconds, subsystem: “SpyNode”
verbose 2021/04/14[32]23:35:00 spynode/node.go:527 Requesting stop, subsystem: “SpyNode”
verbose 2021/04/14[32]23:35:00 spynode/node.go:356 Monitor request timeouts finished, subsystem: “SpyNode”
verbose 2021/04/14[32]23:35:00 spynode/node.go:384 Check tx delays finished, subsystem: “SpyNode”
info 2021/04/14[32]23:35:00 spynode/node.go:410 Stopping, subsystem: “SpyNode”
verbose 2021/04/14[32]23:35:00 spynode/node.go:349 Monitor incoming finished, subsystem: “SpyNode”
verbose 2021/04/14[32]23:35:00 spynode/node.go:370 Process blocks finished, subsystem: “SpyNode”
verbose 2021/04/14[32]23:35:00 spynode/node.go:394 Monitor untrusted finished, subsystem: “SpyNode”
info 2021/04/14[32]23:35:00 spynode/node.go:437 Incoming threads stopped, subsystem: “SpyNode”
verbose 2021/04/14[32]23:35:00 spynode/node.go:377 Process unconfirmed txs finished, subsystem: “SpyNode”
verbose 2021/04/14[32]23:35:00 spynode/node.go:363 Send outgoing finished, subsystem: “SpyNode”
info 2021/04/14[32]23:35:00 spynode/node.go:457 Processing threads stopped, subsystem: “SpyNode”
verbose 2021/04/14[32]23:35:00 spynode/node.go:460 Saving, subsystem: “SpyNode”
verbose 2021/04/14[32]23:35:00 storage/transactions.go:80 Saving 0 unconfirmed txs, subsystem: “SpyNode”
verbose 2021/04/14[32]23:35:00 storage/peers.go:202 Saving 25 peers, subsystem: “SpyNode”
verbose 2021/04/14[32]23:35:00 spynode/node.go:471 Restarting, subsystem: “SpyNode”
verbose 2021/04/14[32]23:35:02 spynode/node.go:329 Re-connecting to 127.0.0.1:8333, subsystem: “SpyNode”
info 2021/04/14[32]23:35:02 spynode/node.go:960 Safe tx delay : 10 ms, subsystem: “SpyNode”
verbose 2021/04/14[32]23:35:02 handlers/version.go:31 (127.0.0.1:8333) Version : /Bitcoin SV:1.0.7/ protocol 70015, blocks 682964, subsystem: “SpyNode”
verbose 2021/04/14[32]23:35:02 spynode/node.go:869 Requesting headers, subsystem: “SpyNode”
verbose 2021/04/14[32]23:35:02 spynode/node.go:794 ReadMessage : Unknown Command : protoconf, subsystem: “SpyNode”
verbose 2021/04/14[32]23:35:02 handlers/headers.go:114 Header (not next) : 000000000000000008211edab6b60b71ba4f4022d72868238acddbe857d800d8, subsystem: “SpyNode”
verbose 2021/04/14[32]23:35:02 handlers/headers.go:114 Header (not next) : 000000000000000006d1cb61d133968075270e8439acadbe1da3c159bc230c19, subsystem: "SpyNode
:
:
verbose 2021/04/14[32]23:35:02 handlers/headers.go:114 Header (not next) : 00000000000000000791ef9b81910d34614ce0310c7986633da1dd02f84ff51d, subsystem: “SpyNode”
verbose 2021/04/14[32]23:35:02 handlers/headers.go:114 Header (not next) : 000000000000000004360a752fc4f30a35046b3ea3a0ec10c46ea400b76346be, subsystem: “SpyNode”
verbose 2021/04/14[32]23:35:02 handlers/headers.go:114 Header (not next) : 00000000000000000469d2f45d772c015e7ec29de23b0bc6452dabb90c63edce, subsystem: “SpyNode”
verbose 2021/04/14[32]23:35:02 handlers/headers.go:114 Header (not next) : 000000000000000004298f427af5306b8c01e3530868a297c68f1bb2e63580c2, subsystem: “SpyNode”
verbose 2021/04/14[32]23:35:02 handlers/headers.go:114 Header (not next) : 000000000000000004d25c749786f791d23bb73a93dee0aa6e86cde0a854421f, subsystem: “SpyNode”
verbose 2021/04/14[32]23:35:02 handlers/headers.go:114 Header (not next) : 0000000000000000055c6ccc26fd8f3c871919b7aed2b5c8f687b416c7483473, subsystem: “SpyNode”
info 2021/04/14[32]23:35:02 handlers/headers.go:127 Header previous block : 000000000000000004d25c749786f791d23bb73a93dee0aa6e86cde0a854421f, subsystem: “SpyNode”
info 2021/04/14[32]23:35:02 handlers/headers.go:130 Reorging to height 682960, subsystem: “SpyNode”
warn 2021/04/14[32]23:35:02 spynode/node.go:720 Failed to handle [headers] message : Revert failed to produce correct last hash : 0000000000000000040c574787ed1e3b578a8fc3d9be4213b09af4a3e1433afb, subsystem: “SpyNode”

HERE IS THE BLOCKCHAIN INFO NOW:
[email protected]:~/.bitcoin$ ./bitcoin-cli getinfo
{
“version”: 101000700,
“protocolversion”: 70015,
“blocks”: 682964,
“timeoffset”: 1,
“connections”: 10,
“proxy”: “”,
“difficulty”: 101841453334.2475,
“testnet”: false,
“stn”: false,
“paytxfee”: 0.00000000,
“relayfee”: 0.00000250,
“errors”: “”,
“maxblocksize”: 2000000000,
“maxminedblocksize”: 128000000,
“maxstackmemoryusagepolicy”: 100000000,
“maxstackmemoryusageconsensus”: 200000000
}
[email protected]:~/.bitcoin$
[email protected]:~/.bitcoin$ ./bitcoin-cli getblockchaininfo
{
“chain”: “main”,
“blocks”: 682964,
“headers”: 682964,
“bestblockhash”: “0000000000000000082ba0fc4977917386a63c328a3d130febf3d89e94d29367”,
“difficulty”: 101841453334.2475,
“mediantime”: 1618449942,
“verificationprogress”: 0.9999978990047459,
“chainwork”: “00000000000000000000000000000000000000000129b8f4f47decc61b494628”,
“pruned”: false,
“softforks”: [
{
“id”: “bip34”,
“version”: 2,
“reject”: {
“status”: true
}
},
{
“id”: “bip66”,
“version”: 3,
“reject”: {
“status”: true
}
},
{
“id”: “bip65”,
“version”: 4,
“reject”: {
“status”: true
}
},
{
“id”: “csv”,
“version”: 5,
“reject”: {
“status”: true
}
}
]
}
[email protected]:~/.bitcoin$

I modified some tests and tried to reproduce this, but was unsuccessful. The only thing I can guess is that you were maybe running two instances at once on the same storage and that cause the storage to be corrupted, or somehow your storage was corrupted.

You should be able to recover by deleting only the spynode directory under the standalone directory in your configured storage directory.