Closed MarcHagen closed 6 years ago
I get a different Assertion Error every time a getHeaders response was not received (which happens every time I started the node after a few messages).
I am connected to a 0.15.99 remote node.
[2017-10-16T19:42:35.357Z] info: Header Service: download progress: 272000/490188 (55.49%)
[2017-10-16T19:42:35.920Z] info: Header Service: download progress: 274000/490188 (55.90%)
[2017-10-16T19:42:38.110Z] info: Header Service: we have not received a response to getHeaders from the network, retrying.
[2017-10-16T19:42:40.112Z] info: Header Service: we have not received a response to getHeaders from the network, retrying.
[2017-10-16T19:42:42.115Z] info: Header Service: we have not received a response to getHeaders from the network, retrying.
[2017-10-16T19:42:44.114Z] info: Header Service: we have not received a response to getHeaders from the network, retrying.
[2017-10-16T19:42:45.228Z] error: uncaught exception: { AssertionError [ERR_ASSERTION]: headers not in order: 0000000000000004b8ed801f8a09ba8c1248a5b1dd1533a35124a80438573f59 -and- 0000000000000003fe2d3425e9f9b906f02f40b3db90d908ba0fbd1e44cf43f8 Last header at height: 276000
/home/bitcoin/.nvm/versions/node/v8.4.0/lib └── bitcore@5.0.0-beta.9
I cannot run bitcore because it's keeps crashing on this error. If i comment the assert on 641 it will work just fine and start syncing