[bug]: LND 0.18.0~1 refuses to sync

[chrisguida]

cc @Dominion5254

LND prints in the log that it's synced

2024-09-05T18:24:10-06:00  2024-09-06 00:24:10.173 [INF] LNWL: Started rescan from block 00000000000000000001e49e5678118a46d43055ebfcd493249da9cf8a2a2f81 (height 860066) for 27726 addresses
2024-09-05T18:24:10-06:00  2024-09-06 00:24:10.285 [INF] LNWL: Catching up block hashes to height 860066, this might take a while
2024-09-05T18:24:10-06:00  2024-09-06 00:24:10.293 [INF] LNWL: Done catching up block hashes
2024-09-05T18:24:10-06:00  2024-09-06 00:24:10.293 [INF] LNWL: Finished rescan for 27726 addresses (synced to block 00000000000000000001e49e5678118a46d43055ebfcd493249da9cf8a2a2f81, height 860066)
2024-09-05T18:24:10-06:00  2024-09-06 00:24:10.386 [INF] LTND: Chain backend is fully synced (end_height=860066)!
2024-09-05T18:24:10-06:00  2024-09-06 00:24:10.386 [INF] NANN: HostAnnouncer starting
2024-09-05T18:24:10-06:00  2024-09-06 00:24:10.386 [WRN] HLCK: check: disk space configured with 0 attempts, skipping it
2024-09-05T18:24:10-06:00  2024-09-06 00:24:10.386 [WRN] HLCK: check: tls configured with 0 attempts, skipping it
2024-09-05T18:24:10-06:00  2024-09-06 00:24:10.386 [INF] LNWL: SigPool starting
2024-09-05T18:24:10-06:00  2024-09-06 00:24:10.389 [INF] NTFN: New block epoch subscription
2024-09-05T18:24:10-06:00  2024-09-06 00:24:10.389 [INF] NTFN: New block epoch subscription
2024-09-05T18:24:10-06:00  2024-09-06 00:24:10.389 [INF] CHNF: ChannelNotifier starting
2024-09-05T18:24:10-06:00  2024-09-06 00:24:10.389 [INF] PRNF: PeerNotifier starting
2024-09-05T18:24:10-06:00  2024-09-06 00:24:10.389 [INF] BTCN: Broadcaster now active
2024-09-05T18:24:10-06:00  2024-09-06 00:24:10.389 [INF] HSWC: HtlcNotifier starting
2024-09-05T18:24:10-06:00  2024-09-06 00:24:10.389 [INF] NTFN: New block epoch subscription

But somehow LND thinks it's not synced:

    "synced_to_chain":  false,
    "synced_to_graph":  false,

It then hangs in this state for weeks

It appears to be using neutrino (see "BTCN" log messages above), which is odd because I have it set to use bitcoind as the blockchain backend, and bitcoind is definitely synced. I have a CLN node attached to the same bitcoind and it's fine.

Occasionally it syncs the chain but then can't seem to sync the graph.

[Dominion5254]

Closing this issue as there doesn't seem to be anything indicating this is an issue with lnd-startos. If lncli getinfo requests are providing seemingly erroneous information regarding the status of synced_to_chain this would be a problem with the upstream service.

Upstream issue opened here