Background
Helping a node operator, he had several channels in the category waiting_close_channels, which as far as I understood are there until the closure is seen onchain. However, his Transaction are already confirmed for more than 4000 Blocks and channels still remain marked as waiting_close_channels. After several restarts and also a wallet rescan nothing tends to help. My question is how I can somehow trigger lnd in a state where it checks relevant blocks again and sees the transaction onchain. Because right now there are a lot of funds locked in limbo (including htlcs which went onchain)
Your environment
- version of
lnd: 0.14.2-beta
- version of
bitcoind : v 22.0
Steps to reproduce
Tell us how to reproduce this issue. Please provide stacktraces and links to code in question.
Expected behaviour
lnd recognizes the spend channelfunding and sweeps the relavant outputs that belong to oneself.
Actual behaviour
Funds are not swept bc lnd keeps them in waiting_close_channels
Background
Helping a node operator, he had several channels in the category
waiting_close_channels, which as far as I understood are there until the closure is seen onchain. However, his Transaction are already confirmed for more than 4000 Blocks and channels still remain marked as waiting_close_channels. After several restarts and also a wallet rescan nothing tends to help. My question is how I can somehow trigger lnd in a state where it checks relevant blocks again and sees the transaction onchain. Because right now there are a lot of funds locked in limbo (including htlcs which went onchain)Your environment
lnd: 0.14.2-betabitcoind: v 22.0Steps to reproduce
Tell us how to reproduce this issue. Please provide stacktraces and links to code in question.
Expected behaviour
lnd recognizes the spend channelfunding and sweeps the relavant outputs that belong to oneself.
Actual behaviour
Funds are not swept bc lnd keeps them in waiting_close_channels