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
Channel Waiting Close with transaction not broadcast and cannot force close #5552
Comments
What do you see in the logs while attempting to force close (possibly grepping for the outpoint TXID)? |
The channel finally closed, I don't know why. Therefore the problem is 'solved'. I did search at the logs and cannot see anything in them about the closing TX until the point at which it was successful a few hours ago, at which point it all looks normal. There is no trace of the failed attempt to force close, at least not including the TX ID. As it is already closed I can't try again to repro the issue of the close command not responding. log of the eventual successful force close, with a couple of minutes either side, is included below. I'll keep the logs for reference by otherwise this node I'll be disconnecting as it never worked right. Thank you for your time. I presume this issue can be closed now.
|
I'm guessing you might've hit a longer timeout with the neutrino backend during broadcast of the initial force close transaction. |
Background
This is similar, perhaps identical, to issue #5341 . If I should talk about it there instead please let me know.
I am trying to close a channel and unable to do so. I used the web interface RTL to try to close it, and it is now in the Wait Closing Channel state but has been for many hours.
When I open up the "Wait Closing Channel Information" it shows me a transaction ID, but this transaction is not visible in mempool.space and not visible in my local mempool.
I've been in similar situations before because the two nodes I have set up never seem to work. Therefore I have experience opening, closing, force closing channels.
But in the previous cases I could force close using the channel point to get another transaction broadcast, but this time it doesn't work so I'm stuck.
Your environment
Here are all the pending channels; the problematic one is the one with node 03858f3b77447b572733e6e888cbbf36b8bc8483bb9716041953bb284495655522
I have already reached out to the operator of that node, advised him of the situation, and suggested he force close from his end. If that works then this is academic from my perspective, but perhaps useful data to see a stuck case??
The problematic channel mentioned above has two transactions mentioned;
I can't see these in mempool.space. I also can't see the local one in the local mempool.
Steps to reproduce
Expected behaviour
After doing lncli closechannel it should reply almost immediately with the tx id of a new transactioni
Actual behaviour
I try to force close but after 8 hours nothing has happened so I press ctrl-C and it looks like this:
The text was updated successfully, but these errors were encountered: