Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug]: lncli getinfo indicates "synced_to_chain: false" despite logs showing "Chain backend is fully synced" #9081

Open
Dominion5254 opened this issue Sep 10, 2024 · 0 comments
Labels
bug Unintended code behaviour needs triage

Comments

@Dominion5254
Copy link

Background

Reporting behavior described by @chrisguida here.
lncli getinfo return value indicates "synced_to_chain": false - despite the logs indicating "Chain backend is fully synced".

Logs:

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

Your environment

  • LND 0.18.0 running on StartOS 0.3.5~1
  • bitcoind backend (fully synced)

Steps to reproduce

Behavior can't seem to be reproduced aside from the user in question. But for the user in question, the behavior persists across restarts of lnd.

Expected behaviour

If the logs are indicating "Chain backend is fully synced', lncli getinfo requests should show synced_to_chain as true.

Actual behaviour

Despite the logs indicating "Chain backend is fully synced', lncli getinfo requests indefinitely continue to show synced_to_chain as false.

@Dominion5254 Dominion5254 added bug Unintended code behaviour needs triage labels Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unintended code behaviour needs triage
Projects
None yet
Development

No branches or pull requests

1 participant