[bug]: channel stuck in waiting_close_channels #8560
Labels
Comments
|
Thanks for submitting this issue.
The remote commitment got confirmed see: 9d82dcc2eec62a43cb0e4fe6a02a4c3dccc30ee9acd4fc9591ccbaa327fb45b3, that's why you cannot see the local one somewhere. So find out why your LND did not recognize the spent of the channel point, can you
|
|
Both lines appear in the log. After restarting with |
|
The rescan for the output might take a while don't stop the node:
normally it should be able to recognize the spend of the channel opening. |
|
Ah indeed, I let the node run for the night and now the channel is gone from waiting_close_channels. What was the cause of this? did lnd miss a transaction at some point? Or is there a bug is some logic that |
|
Yes I haven't been able to reproduce this edge case which happens sometime, where the height_hint cache has a wrong value in it. We are aware of this behavior and track it here: #8120 Therefore I am closing this issue. Feel free to reach out if you have further questions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Background
I have a LND node on testnet which has one channel in waiting_close_channels. Though when I look at the on-chain transactions, the channel has been (force) closed by the other node.
I suspect this was the sequence of actions:
"initiator": "INITIATOR_REMOTE").I tried restarting LND with a full rescan, but that did not help.
AFAICS there was no local balance on my side, the close transaction yielded coins only to the remote node.
It's also interesting that the committment local_txid (see below) can not be found in the mempool.
{ "channel": { "remote_node_pub": "038863cf8ab91046230f561cd5b386cbff8309fa02e3f0c3ed161a3aeb64a643b9", "channel_point": "5ab08b2c8f1e442821746736582dbb390757488e27946f7967c6d678d71381bc:0", "capacity": "16776923", "local_balance": "0", "remote_balance": "16776740", "local_chan_reserve_sat": "167769", "remote_chan_reserve_sat": "167769", "initiator": "INITIATOR_REMOTE", "commitment_type": "STATIC_REMOTE_KEY", "num_forwarding_packages": "0", "chan_status_flags": "ChanStatusCoopBroadcasted|ChanStatusLocalCloseInitiator", "private": false, "memo": "" }, "limbo_balance": "0", "commitments": { "local_txid": "42a6fba91adf0e78cd6305f3c2854cbfde3bd5e9a1ad26f3428da53b71ee121a", "remote_txid": "9d82dcc2eec62a43cb0e4fe6a02a4c3dccc30ee9acd4fc9591ccbaa327fb45b3", "remote_pending_txid": "", "local_commit_fee_sat": "183", "remote_commit_fee_sat": "183", "remote_pending_commit_fee_sat": "0" }, "closing_txid": "" }Your environment
lnd: lnd version 0.17.4-betauname -aon *Nix): Darwin Kernel Version 22.2.0btcd,bitcoind, or other backend: bitcoind in neutrino modeSteps to reproduce
This has happened a while ago, but I can provide any information you want. The node is on testnet and I'm trying to shut it down, so has no funds anymore.
Expected behaviour
LND notices the force channel close and clears the channel from its local database.
Actual behaviour
Channel is stuck in waiting_close_channels forever, even after a full chain rescan.
The text was updated successfully, but these errors were encountered: