Bitcoin Synced, LND Waiting... "Possible Reorg"

[laddieri]

• I'm submitting a ...

  • [ ] bug report
  • [ ] feature request
  • [x] support request

• What is the current behavior? Bitcoin is fully synced. LND stuck at "waiting for chain backend to finish sync". Further debug info shows errors in LND output: "Possible reorg at block...." and "Disconnecting Block 581063..."

2019-06-17 19:31:27.971 [INF] LTND: Version: 0.6.0-beta commit=v0.6-beta, build=production, logging=default 2019-06-17 19:31:27.971 [INF] LTND: Active chain: Bitcoin (network=mainnet) 2019-06-17 19:31:27.972 [INF] CHDB: Checking for schema update: latest_version=8, db_version=8 2019-06-17 19:31:27.980 [INF] RPCS: password RPC server listening on 127.0.0.1:10009 2019-06-17 19:31:27.980 [INF] RPCS: password gRPC proxy started at 127.0.0.1:8080 2019-06-17 19:31:27.980 [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-06-17 19:31:30.168 [INF] LNWL: Opened wallet 2019-06-17 19:31:30.320 [INF] LTND: Primary chain is set to: bitcoin 2019-06-17 19:31:35.262 [INF] LNWL: Started listening for bitcoind block notifications via ZMQ on tcp://127.0.0.1:18500 2019-06-17 19:31:35.262 [INF] LNWL: Started listening for bitcoind transaction notifications via ZMQ on tcp://127.0.0.1:18501 2019-06-17 19:31:35.262 [INF] LTND: Initializing bitcoind backed fee estimator 2019-06-17 19:31:43.880 [DBG] LNWL: Using minimum fee rate of 253 sat/kw 2019-06-17 19:31:44.911 [INF] LNWL: The wallet has been unlocked without a time limit 2019-06-17 19:31:52.158 [INF] LTND: LightningWallet opened 2019-06-17 19:31:52.158 [DBG] LNWL: Birthday block has already been verified: height=564050, hash=00000000000000000026c3ed5a09665261ca9ebbb48ea20124589c73576a69c8 2019-06-17 19:31:52.289 [WRN] LNWL: Unable to synchronize wallet to chain: -8: Block height out of range 2019-06-17 19:31:59.843 [INF] HSWC: Restoring in-memory circuit state from disk 2019-06-17 19:31:59.845 [INF] HSWC: Payment circuits loaded: num_pending=0, num_open=0 2019-06-17 19:31:59.850 [TRC] SRVR: Sweeper batch window duration: 30s 2019-06-17 19:31:59.851 [INF] LTND: Channel backup proxy channel notifier starting 2019-06-17 19:31:59.851 [INF] ATPL: Instantiating autopilot with cfg: (*main.autoPilotConfig)(0xc000057240)({ 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-06-17 19:31:59.851 [DBG] LTND: Populating dependencies for sub RPC server: SignRPC 2019-06-17 19:31:59.851 [DBG] LTND: Populating dependencies for sub RPC server: WalletKitRPC 2019-06-17 19:31:59.851 [DBG] LTND: Populating dependencies for sub RPC server: AutopilotRPC 2019-06-17 19:31:59.851 [DBG] LTND: Populating dependencies for sub RPC server: ChainRPC 2019-06-17 19:31:59.851 [DBG] LTND: Populating dependencies for sub RPC server: InvoicesRPC 2019-06-17 19:31:59.851 [DBG] LTND: Populating dependencies for sub RPC server: RouterRPC 2019-06-17 19:31:59.852 [DBG] IRPC: Invoices RPC server successfully registered with root gRPC server 2019-06-17 19:31:59.852 [DBG] WLKT: WalletKit RPC server successfully registered with root gRPC server 2019-06-17 19:31:59.852 [DBG] SGNR: Signer RPC server successfully register with root gRPC server 2019-06-17 19:31:59.852 [DBG] RPCS: Starting sub RPC server: InvoicesRPC 2019-06-17 19:31:59.852 [DBG] RPCS: Starting sub RPC server: WalletKitRPC 2019-06-17 19:31:59.852 [DBG] RPCS: Starting sub RPC server: SignRPC 2019-06-17 19:31:59.852 [DBG] RPCS: Starting sub RPC server: ChainRPC 2019-06-17 19:31:59.852 [INF] RPCS: RPC server listening on 127.0.0.1:10009 2019-06-17 19:31:59.852 [INF] RPCS: gRPC proxy started at 127.0.0.1:8080 2019-06-17 19:31:59.853 [INF] LTND: Waiting for chain backend to finish sync, start_height=581138 2019-06-17 19:32:07.506 [DBG] LNWL: Possible reorg at block 00000000000000000016e1f703906fd1306bb133c234026f8f8abf98c885783c 2019-06-17 19:32:22.321 [DBG] LNWL: Disconnecting block 581063 (0000000000000000001b67ec2be2f56e1caa4adf86705c2229b7f2918778a11a)

• If the current behavior is a bug, please provide the steps to reproduce

• What is the expected behavior?

• What is the motivation / use case for changing the behavior?

• Please tell us about your environment: Windows 10

  • Operating System: [ Windows | macOS | Linux ]

• Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc) Restarting computer and/or Node Launcher seems to randomly fix this problem. Hard to duplicate a solution.

[laddieri]

I was able to get LND synced and fully functional by restarting the computer, opening Node Launcher, waiting for the previously mentioned "reorg" problem to reappear, then closing "Node Launcher" and reopening it. It still seems pretty unpredictable.

[laddieri]

Update: I also was able to get LND to sync by issuing the "stop" command in the lncli console after getting the "possible reorg" error. This restarts LND and it syncs.