[bug]: lncli getinfo indicates "synced_to_chain: false" despite logs showing "Chain backend is fully synced" #9081
Labels
Comments
|
This can easily be possible. The log entry just confirms that the sync was true when starting up lnd, however this can change during operation. Can you provide your |
|
It's definitely staying synced to tip 
|
|
Might want to check your ZMQ settings. |
|
What am I looking for? lnd.conf: bitcoin.conf: |
|
I'd try removing the types |
|
Those are needed for other services, I can't remove them |
|
I can temporarily disable, but this is a bug if the solution is to turn them off |
|
Anyway those settings have been active on Start9 for a couple of years at least, I doubt that's the issue. Discussing with @Dominion5254 how to turn three of these off while leaving the other two on |
This seems like a red herring. Every single lnd-startos user has these same config options set in their Bitcoin Core config - But aside from Chris's case, this particular issue has never come up before. Is there anything else that could explain this behavior? |
|
Okay, was just a hunch. |
|
Does it still report as not being synced? Are there any changes to |
|
Can you also verify you are not doing a wallet rescan by accident, because LND will not report sync_to_chain=true, in case your walllet is not caught up with the current chain. |
|
@bitromortac yes it's still stuck in not synced to chain and not synced to graph, but the log still indicates that it's indeed synced to the tip What is the "original configuration"? This is the Start9 LND package and I've had this node for a while as a test node, but I don't think it's much different from the default Start9 config. Here it is in case that helps: |
|
@ziggie1984 I'm not sure how I would accidentally trigger a rescan; I definitely didn't do this intentionally but @Dominion5254 would have more info on whether Start9 triggers this in certain cases. I can try a rescan if you think that would help. |
|
Thanks for the config, there are two subsystems that are checked for onchain synchronization, the wallet and the graph builder. Could you post some logs from the wallet and graph systems, by setting |
|
|
Ah right, the graph refactor is not in 0.18.0, |
|
cool, guess i'll see if anything comes out
That's a very neat feature, rpc command to change logging levels |
|
Just a lot of this so far. Anything in particular I should be looking for? |
|
Maybe just this line, but I think that's not the problem:
It may help if you could provide a goroutine dump. You'd need to start with a profile port open, see https://docs.lightning.engineering/lightning-network-tools/lnd/debugging_lnd#capturing-pprof-data-with-lnd. Then it would be great to see the contents of the file created by |
|
Ahh darn, changing the command line will require rebuilding the docker image. I'll see if I can do that soon. |
|
You can also add that value to your config file (without the leading dashes, |
|
Here it is Btw I noticed the S9 configurator is probably stuck in this loop trying to add a bad watchtower. I removed the tower and the chain sync completed, and the graph sync started like this: ..etc. I'm actually not seeing the loop iterate, so I think maybe it's just actually stuck on the The watchtower was I'm not sure why this command would hang forever and never time out, nor am I sure why LND would not simply continue with the chain/graph sync while a watchtower is in the process of being added. Seems like maybe two bugs, one on the S9 side and the other on the LND side. I added the watchtower back and the node is stuck again, so this is definitely the problem. |
Can you capture the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Background
Reporting behavior described by @chrisguida here.
lncli getinforeturn value indicates"synced_to_chain": false- despite the logs indicating "Chain backend is fully synced".Logs:
Your environment
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 getinforequests should show synced_to_chain as true.Actual behaviour
Despite the logs indicating "Chain backend is fully synced',
lncli getinforequests indefinitely continue to show synced_to_chain as false.The text was updated successfully, but these errors were encountered: