lightning-power-users / node-launcher

Easiest Bitcoin Lightning desktop app, for Windows, macOS, and Linux
MIT License
357 stars 67 forks source link

Bitcoin Node doesn't properly finish syncing #256

Open jgmontoya opened 5 years ago

jgmontoya commented 5 years ago

Node apparently syncs but tray icon 'status' doesn't go to "synced", it stays at

ETA: X minutes from now, 100% done

Where X is roughly an estimation of the next block (checking the blockchain height on an explorer (I used this one) It shows that the node is synced up to the latest block (at least according to the height shown by the "Bitcoind Output" window.

When I trying to restart the node (exiting the app and executing it again) it has to sync the last part of the blockchain again (around ~5%) instead of starting from where it was before. In other words, when restarted the height was lower than what it was before being stopped and it has to download that again.

The lightning wallet doesn't seem to work either (I believe it's probably because of the node not appearing as "synced").

Executing node-launcher from scratch and interrupting the syncing process.

It should identify that it has reached the latest blocks and show "synced". It should be able to save the latest blocks correctly and restart from that point. Lightning node should work.

Screenshot of the tray icon and "Bitcoind Ouput" in case it helps:

tray_icon last_output

jgmontoya commented 5 years ago

Hi,

Managed to solve this by downloading the bitcoin core wallet and letting it finish syncing. After that node launcher correctly identified the synced blockchain.

i22ie commented 5 years ago

Hi

Thanks jgmontoya, that was timely. I had exactly the same issue, also now solved.

robbie2121 commented 5 years ago

I get the same issue once in a while too. Opening bitcoin core letting it synch for a bit then close it and re-launch node launcher seems to resolve it.

feitsau commented 5 years ago

I also have this issue. It seems that any progress (on the chain) made when Node Launcher is active is lost when I close it and open it again. It always starts from the last spot Bitcoin Core synced to. This means if Node Launcher is active for a long time (days) it takes longer and longer to sync each time I open it again (unless I first run Bitcoin Core to sync then close it). This seems like something is not working as intended.