Same problem here. 
1 Like
Hi @iceman05 is this in regards to a recently recovered node where the channels have closed, and one or two are stuck?
Just looking for some further context to help you out
yeah Iceman and me got the “same” problem (we also had a channel together but this one closed by using the channel backup)…
In my case I had 30 channels and after the node crashed I downloaded the whole blockchain again, then used the umbrel backup file to restore the channels - - > 27 channels closed and three were left in status “waiting for close” but without any Information about local/remote balance. Two of them I could close by using chantool triggerforceclose but the last one only got a Tor address and so the triggerforceclose command doesn’t work.
Iceman got the same problem (waiting channel close, no information about local/remote balance in this channel) but an additional problem here is that the peer node also crashed and doesn’t have these information either. Now they don’t know how to close the channel and how many sats everyone of them should get.
wick3da has already explained it very well. Unfortunately, both my node and the other side’s node crashed almost at the same time. We both had to re-download the blockchain. All channels could be closed except for this one:
{
“total_limbo_balance”: “0”,
“pending_open_channels”: [
],
“pending_closing_channels”: [
],
“pending_force_closing_channels”: [
],
“waiting_close_channels”: [
{
“channel”: {
“remote_node_pub”: “02b902e9189d2e973c1e3745b16a8c9e9e2a8efe05748540961629ede2c200a1be”,
“channel_point”: “7129aa7c084559db766e0c3c0da82c3da87771be1dc3cf936e0237ecb5eae2c1:1”,
“capacity”: “2000000”,
“local_balance”: “0”,
“remote_balance”: “0”,
“local_chan_reserve_sat”: “0”,
“remote_chan_reserve_sat”: “0”,
“initiator”: “INITIATOR_REMOTE”,
“commitment_type”: “ANCHORS”,
“num_forwarding_packages”: “0”,
“chan_status_flags”: “ChanStatusRestored”,
“private”: true
},
“limbo_balance”: “0”,
“commitments”: {
“local_txid”: “”,
“remote_txid”: “”,
“remote_pending_txid”: “”,
“local_commit_fee_sat”: “0”,
“remote_commit_fee_sat”: “0”,
“remote_pending_commit_fee_sat”: “0”
},
“closing_txid”: “”
}
]
}
@iceman05 @wick3da Looks like chantools recovery is going to be the best tool here. GitHub - lightninglabs/chantools: A loose collection of tools all somehow related to lnd and Lightning Network channels.
It particular it looks like you are going to have to look over the zombie channel recovery process. https://github.com/lightninglabs/chantools/blob/master/doc/zombierecovery.md#file-format What Are Zombie Lightning Channels? - The Bitcoin Manual
Please have a look over these so you can get an idea for what you’ll need to do here, and try install chantools to your laptop/PC. Once thats done please let me know and we can proceed
1 Like
@iceman05 @wick3da @BTCsatsII @smolgrrr Any solutions to this? I have a Channel in “Closing” Status and not able to triggerforceclose with a tor-address. Any advice is greatly appreciated, thanks…
“total_limbo_balance”: “5005530”,
“pending_open_channels”: ,
“pending_closing_channels”: ,
“pending_force_closing_channels”: ,
“waiting_close_channels”: [
{
“channel”: {
“remote_node_pub”: “02e0d304ea61db67dcee3c3c4b53b1c43e3ed0a52e369cc86fe6e3562579739aa7”,
“channel_point”: “f540a1042bbe18a00d81e58b97e80f045b34f4738b0a06f91a8334b423c36fc2:1”,
“capacity”: “5009000”,
“local_balance”: “5005530”,
“remote_balance”: “0”,
“local_chan_reserve_sat”: “50090”,
“remote_chan_reserve_sat”: “50090”,
“initiator”: “INITIATOR_LOCAL”,
“commitment_type”: “ANCHORS”,
“num_forwarding_packages”: “0”,
“chan_status_flags”: “ChanStatusBorked|ChanStatusCommitBroadcasted|ChanStatusLocalCloseInitiator”,
“private”: false,
“memo”: “”
},
“limbo_balance”: “5005530”,
“commitments”: {
“local_txid”: “85c5fbeca40f0a5b94805299919d0eedf3b50f7247aeb48e4c186dbef357e0ac”,
“remote_txid”: “0a4c9a9e083c3380132dfd1d530a0db34030f66bcc1e02d4a71a724953b9fb72”,
“remote_pending_txid”: “”,
“local_commit_fee_sat”: “2810”,
“remote_commit_fee_sat”: “2810”,
“remote_pending_commit_fee_sat”: “0”
},
“closing_txid”: “85c5fbeca40f0a5b94805299919d0eedf3b50f7247aeb48e4c186dbef357e0ac”
Unfortunately, I haven’t made any progress on this topic yet. Somehow I hope there will be a simpler solution at some point.
@DarthCoin @smolgrrr @usernameisJim I used command ~/umbrel/scripts/app compose lightning exec lnd lncli wallet bumpfee 85c5fbeca40f0a5b94805299919d0eedf3b50f7247aeb48e4c186dbef357e0ac:0 --sat_per_vbyte 40 to change the fee rate, but get an ERROR: Couldn’t connect to Docker daemon at http+docker://localhost - is it running? Any other commands I can use to bump fee in the closing_txid? Any advice is greatly appreciated, thanks…