Closed Varunram closed 6 years ago
With recent updates patched in, regtest sync seems to be not working properly. Getting
2018/08/02 22:25:48.988339 got header tip height 145 2018/08/02 22:25:48.988516 Got verack. Whatever. 2018/08/02 22:25:48.988572 Got unknown message type alert 2018/08/02 22:25:48.988641 Got unknown message type sendheaders 2018/08/02 22:25:48.989156 get headers message has 13 header hashes, first one is 201d6f967a3dd111ce0e4711b328116a53d303ef309f109a3642b0f14fa61844 2018/08/02 22:25:48.989530 got 1 headers. Range: 76b9a67fa303f9b41db86342f3655a7f5cc63f6fe854423c730646caf04b2efb - 76b9a67fa303f9b41db86342f3655a7f5cc63f6fe854423c730646caf04b2efb 2018/08/02 22:25:48.989567 header file position: 11600 2018/08/02 22:25:48.989580 made 146 header slice 2018/08/02 22:25:48.993253 Error loading StatCom: StatComFromBytes got 235 bytes, expect at least 357 2018/08/02 22:25:49.022496 StatComFromBytes got 235 bytes, expect at least 357
will investigate and report further or close with the reason if found.
After an hour of trying, I guess the only way in the end was to nuke ln.db. Sad :(
ln.db
With recent updates patched in, regtest sync seems to be not working properly. Getting
will investigate and report further or close with the reason if found.