question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

LND never finishes sync.

See original GitHub issue

Macos 10.13.6, clean install everything from 5.1.1 release. LND is never able to finish sync, and getinfo always reports “synced_to_chain”: false.


2018-12-18 18:08:28.794 [INF] LTND: Version: 0.5.1-beta commit=, build=production, logging=default 2018-12-18 18:08:28.794 [INF] LTND: Active chain: Bitcoin (network=mainnet) 2018-12-18 18:08:28.795 [INF] CHDB: Checking for schema update: latest_version=7, db_version=7 2018-12-18 18:08:28.803 [INF] RPCS: password RPC server listening on 127.0.0.1:10010 2018-12-18 18:08:28.803 [INF] RPCS: password gRPC proxy started at 127.0.0.1:8081 2018-12-18 18:08:28.803 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it. 2018-12-18 18:08:38.417 [INF] LNWL: Opened wallet 2018-12-18 18:08:38.474 [INF] LTND: Primary chain is set to: bitcoin 2018-12-18 18:08:38.477 [INF] LTND: Initializing bitcoind backed fee estimator 2018-12-18 18:08:38.477 [INF] LNWL: Started listening for bitcoind transaction notifications via ZMQ on tcp://127.0.0.1:18503 2018-12-18 18:08:38.477 [INF] LNWL: Started listening for bitcoind block notifications via ZMQ on tcp://127.0.0.1:18502 2018-12-18 18:08:39.105 [INF] LNWL: The wallet has been unlocked without a time limit 2018-12-18 18:08:39.106 [INF] LTND: LightningWallet opened 2018-12-18 18:08:39.110 [INF] LNWL: Started rescan from block 000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f (height 0) for 3 addresses 2018-12-18 18:08:39.110 [INF] LNWL: Starting rescan from block 000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f 2018-12-18 18:08:39.110 [INF] HSWC: Restoring in-memory circuit state from disk 2018-12-18 18:08:39.111 [INF] HSWC: Payment circuits loaded: num_pending=0, num_open=0 2018-12-18 18:08:39.112 [INF] RPCS: RPC server listening on 127.0.0.1:10010 2018-12-18 18:08:39.112 [INF] RPCS: gRPC proxy started at 127.0.0.1:8081 2018-12-18 18:08:39.113 [INF] LTND: Waiting for chain backend to finish sync, start_height=554344 2018-12-18 18:09:10.084 [INF] LNWL: Rescan finished at 0 (000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f) 2018-12-18 18:09:10.085 [ERR] LNWL: Unable to complete chain rescan: Post http://127.0.0.1:8332: dial tcp 127.0.0.1:8332: connect: operation timed out 2018-12-18 18:09:10.085 [INF] LNWL: Catching up block hashes to height 0, this might take a while 2018-12-18 18:09:10.085 [INF] LNWL: Done catching up block hashes 2018-12-18 18:09:10.086 [INF] LNWL: Finished rescan for 3 addresses (synced to block 000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, height 0) 2018-12-18 18:09:33.406 [ERR] LNWL: Failed to process consensus server notification (name: blockconnected, detail: failed to store sync information 0000000000000000002ae9ee04124233376d3a608d702866213613b5163fb0d9: failed to fetch block hash for height 554344: block not found) 2018-12-18 18:11:41.757 [ERR] LNWL: Failed to process consensus server notification (name: blockconnected, detail: failed to store sync information 0000000000000000001ee8666d4453b3b1da908c5cd12a47b9b4ef16a7f78372: failed to fetch block hash for height 554345: block not found)

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:9 (1 by maintainers)

github_iconTop GitHub Comments

1reaction
bvolpatocommented, Jan 10, 2019

It seems that restart after the initial scan should always be recommended/done. There’s this and also I was just able to reproduce this error where ZMQ missed a block and just fixed it by restarting lnd: https://github.com/lightningnetwork/lnd/issues/1597

0reactions
ghostcommented, Mar 30, 2019

Seems to be resolved.

Steps taken: Reboot Disabled VPN Reset router + port forwarding Reset TLS certificates Restarted LND a couple of times

Read more comments on GitHub >

github_iconTop Results From Across the Web

LND with Neutrino never finishes syncing after restart #1559
I run LND with a Neutrino backend on the Bitcoin testnet chain. During the initial sync, the node has 3 peers and syncs...
Read more >
Why does CLN (Core Lightning) sync from Genesis while LND ...
This seems to give a huge advantage over CLN on first startup times. As of now, my CLN node has spent over 14...
Read more >
RaspiBlitz node won't finish syncing, help : r/lightningnetwork
I've been going through the setup at https://github.com/rootzoll/raspiblitz but it has been stuck on the "Node is Syncing" screen here. I know ...
Read more >
lnd_comp_mct.F90
Set the land model MCT GS map private :: lnd_chkAerDep_mct ! ... dtime_sync,' never align' call endrun ( sub//' ERROR: time out of...
Read more >
Umbrel Troubleshooting Guide
Restarting the node when is in a sync process can break more things than fix them. So until your are sure that you...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found