node-launcher
node-launcher copied to clipboard
lightning-power-users
Lightning Never Finishes syncing: Waiting for chain backend to finish sync, start_height=
-
I'm submitting a ...
- [x ] bug report
-
What is the current behavior? Lightning Never Finishes syncing
-
If the current behavior is a bug, please provide the steps to reproduce Downloaded version 6.0.1 Windows bug fix and start notification and 6.0.2 Bump LND to v0.6-beta-rc3 neither will finish syncing older version worked just fine for months
-
What is the expected behavior? worked just fine for months with older versions
-
What is the motivation / use case for changing the behavior?
-
Please tell us about your environment:
- Operating System: [ Windows | 10 64bit]
-
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc
019-04-10 22:22:10.103 [INF] LTND: Version: 0.6.0-beta commit=v0.6-beta-rc3, build=production, logging=default
2019-04-10 22:22:10.103 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2019-04-10 22:22:10.104 [INF] CHDB: Checking for schema update: latest_version=8, db_version=8
2019-04-10 22:22:10.113 [INF] RPCS: password RPC server listening on 127.0.0.1:10009
2019-04-10 22:22:10.113 [INF] RPCS: password gRPC proxy started at 127.0.0.1:8081
2019-04-10 22:22:10.113 [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.
2019-04-10 22:22:12.624 [INF] LNWL: Opened wallet
2019-04-10 22:22:12.947 [INF] LTND: Primary chain is set to: bitcoin
unable to create chain control: unable to connect to bitcoind: -28: Verifying blocks...
2019-04-10 22:22:13.552 [INF] LTND: Shutdown complete
unable to connect to bitcoind: -28: Verifying blocks...
2019-04-10 22:22:16.764 [INF] LTND: Version: 0.6.0-beta commit=v0.6-beta-rc3, build=production, logging=default
2019-04-10 22:22:16.764 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2019-04-10 22:22:16.765 [INF] CHDB: Checking for schema update: latest_version=8, db_version=8
2019-04-10 22:22:16.774 [INF] RPCS: password RPC server listening on 127.0.0.1:10009
2019-04-10 22:22:16.774 [INF] RPCS: password gRPC proxy started at 127.0.0.1:8081
2019-04-10 22:22:16.774 [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.
2019-04-10 22:22:19.232 [INF] LNWL: Opened wallet
2019-04-10 22:22:19.635 [INF] LTND: Primary chain is set to: bitcoin
2019-04-10 22:22:19.920 [INF] LNWL: Started listening for bitcoind block notifications via ZMQ on tcp://127.0.0.1:18500
2019-04-10 22:22:19.920 [INF] LTND: Initializing bitcoind backed fee estimator
2019-04-10 22:22:19.920 [INF] LNWL: Started listening for bitcoind transaction notifications via ZMQ on tcp://127.0.0.1:18501
2019-04-10 22:22:21.136 [INF] LNWL: The wallet has been unlocked without a time limit
2019-04-10 22:22:21.694 [INF] LTND: LightningWallet opened
2019-04-10 22:22:22.655 [WRN] LNWL: Unable to synchronize wallet to chain: -8: Block height out of range
2019-04-10 22:22:24.273 [INF] HSWC: Restoring in-memory circuit state from disk
2019-04-10 22:22:24.429 [INF] HSWC: Payment circuits loaded: num_pending=0, num_open=0
2019-04-10 22:22:24.429 [INF] HSWC: Trimming open circuits for chan_id=562625:1132:1, start_htlc_id=3
2019-04-10 22:22:25.242 [INF] LTND: Channel backup proxy channel notifier starting
2019-04-10 22:22:25.242 [INF] ATPL: Instantiating autopilot with cfg: (*main.autoPilotConfig)(0xc000059100)({
Active: (bool) false,
Heuristic: (map[string]float64) (len=1) {
(string) (len=12) "preferential": (float64) 1
},
MaxChannels: (int) 5,
Allocation: (float64) 0.6,
MinChannelSize: (int64) 20000,
MaxChannelSize: (int64) 16777215,
Private: (bool) false,
MinConfs: (int32) 0
})
2019-04-10 22:22:25.243 [INF] RPCS: RPC server listening on 127.0.0.1:10009 2019-04-10 22:22:25.243 [INF] RPCS: gRPC proxy started at 127.0.0.1:8081 2019-04-10 22:22:26.120 [INF] LTND: Waiting for chain backend to finish sync, start_height=570821
I've experienced this as well but after leaving it open long enough it did end up syncing, did yours do that?
Sorry for the late response @PierreRochard It never did sync and I reverted back to 5.5.1 which still works fine for me!
I had to launch my older version 5.6.0, then sync the Bitcoin blockchain using that version. Exited, then started version 6.0.5. My guess is the new version was looking at the blocks in the old version somehow, even though version 6.0.5 said it was synced.
I'm having the same issue now with: lnd version 0.7.0-beta commit=v0.7.0-beta-4-ga6e77811b1578f5d48191d0b9a5d4cbf895626f5
connect command failing:
$ lncli connect
0217890e3aad8d35bc054f43acc00084b25229ecff0ab68debd82883ad65ee8266@23.237.77.11:9735
[lncli] rpc error: code = Unknown desc = chain backend is still syncing, server not active yet
Log:
Sep 03 10:04:40 btcnode01 lnd[14586]: 2019-09-03 10:04:40.676 [DBG] LTND: Populating dependenci[0/1182]
ub RPC server: ChainRPC
Sep 03 10:04:40 btcnode01 lnd[14586]: 2019-09-03 10:04:40.676 [DBG] LTND: Populating dependencies for s
ub RPC server: InvoicesRPC
Sep 03 10:04:40 btcnode01 lnd[14586]: 2019-09-03 10:04:40.676 [DBG] LTND: Populating dependencies for s
ub RPC server: RouterRPC
Sep 03 10:04:40 btcnode01 lnd[14586]: 2019-09-03 10:04:40.676 [DBG] LTND: Populating dependencies for s
ub RPC server: WatchtowerRPC
Sep 03 10:04:40 btcnode01 lnd[14586]: 2019-09-03 10:04:40.679 [INF] RPCS: RPC server listening on 127.0
.0.1:10009
Sep 03 10:04:40 btcnode01 lnd[14586]: 2019-09-03 10:04:40.686 [INF] RPCS: gRPC proxy started at 127.0.0
.1:8081
Sep 03 10:04:40 btcnode01 lnd[14586]: 2019-09-03 10:04:40.688 [INF] LTND: Waiting for chain backend to
finish sync, start_height=559785
I've waited 12 hours and it's still hung up. What to do? Thanks!
