Waiting Close Channel - ChanStatusLocalDataLoss|ChanStatusRestored

[AiKawai]

Background

• Voltage drop occurs: $ vcgencmd get_throttled => throttled=0x50000
• channel.db is corrupted
• Recovery from SCB
• One channel is "Waitting Close"
• No way to contact peer

What else is there to do but wait for the force close?

Environment

• Umbrel 0.5.3-build-d6641f8
• LND 0.15.5-beta

Expected behaviour

Close channel and collect funds

Actual behaviour

lnshell@xxx:~$ lncli pendingchannels
{
    "total_limbo_balance": "0",
    "pending_open_channels": [
    ],
    "pending_closing_channels": [
    ],
    "pending_force_closing_channels": [
    ],
    "waiting_close_channels": [
        {
            "channel": {
                "remote_node_pub": "0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f",
                "channel_point": "0857b273c2b9a4b8f5b0c54fa426dfba2bfe76667b034ab199dc7a10561cea9e:1",
                "capacity": "14000000",
                "local_balance": "0",
                "remote_balance": "0",
                "local_chan_reserve_sat": "0",
                "remote_chan_reserve_sat": "0",
                "initiator": "INITIATOR_REMOTE",
                "commitment_type": "STATIC_REMOTE_KEY",
                "num_forwarding_packages": "0",
                "chan_status_flags": "ChanStatusLocalDataLoss|ChanStatusRestored"
            },
            "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": ""
        }
    ]
}

lnshell@xxx:~$ lncli closechannel --force 0857b273c2b9a4b8f5b0c54fa426dfba2bfe76667b034ab199dc7a10561cea9e 1
[lncli] rpc error: code = Unknown desc = cannot close channel with state: ChanStatusLocalDataLoss|ChanStatusRestored

[AiKawai]

lnshell@xxx:~$ lncli connect 0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f@73.114.40.246:9735
[lncli] rpc error: code = Unknown desc = already connected to peer: 0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f@73.114.40.246:9735

[AiKawai]

2023-01-26 23:11:41.379 [INF] DISC: GossipSyncer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): requesting new chans from height=0 and 773774 blocks after
2023-01-26 23:11:42.438 [INF] DISC: GossipSyncer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): buffering chan range reply of size=8185
2023-01-26 23:11:43.171 [INF] DISC: GossipSyncer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): buffering chan range reply of size=8186
2023-01-26 23:11:43.827 [INF] DISC: GossipSyncer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): buffering chan range reply of size=8185
2023-01-26 23:11:44.428 [INF] DISC: GossipSyncer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): buffering chan range reply of size=8186
2023-01-26 23:11:44.844 [INF] DISC: GossipSyncer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): buffering chan range reply of size=8181
2023-01-26 23:11:45.288 [INF] DISC: GossipSyncer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): buffering chan range reply of size=8186
2023-01-26 23:11:45.576 [INF] DISC: GossipSyncer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): buffering chan range reply of size=8185
2023-01-26 23:11:45.854 [INF] DISC: GossipSyncer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): buffering chan range reply of size=8186
2023-01-26 23:11:46.082 [INF] DISC: GossipSyncer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): buffering chan range reply of size=8185
2023-01-26 23:11:46.090 [INF] DISC: GossipSyncer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): buffering chan range reply of size=1333
2023-01-26 23:11:46.091 [INF] DISC: GossipSyncer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): filtering through 74998 chans
2023-01-26 23:11:46.224 [INF] DISC: GossipSyncer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): starting query for 27 new chans
2023-01-26 23:11:46.224 [INF] DISC: GossipSyncer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): querying for 27 new channels
2023-01-26 23:11:46.589 [INF] DISC: GossipSyncer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): no more chans to query
2023-01-27 00:29:42.102 [ERR] RPCS: [connectpeer]: error connecting to peer: already connected to peer: 0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f@73.114.40.246:9735
2023-01-27 00:29:42.102 [ERR] RPCS: [/lnrpc.Lightning/ConnectPeer]: already connected to peer: 0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f@73.114.40.246:9735
2023-01-27 00:54:27.219 [INF] SRVR: Disconnecting from 0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f@73.114.40.246:9735
2023-01-27 00:54:27.219 [INF] PEER: Peer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): disconnecting 0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f@73.114.40.246:9735, reason: server: DisconnectPeer called
2023-01-27 00:54:27.219 [INF] PEER: Peer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): unable to read message from peer: read tcp 10.21.21.9:33700->73.114.40.246:9735: use of closed network connection
2023-01-27 00:58:26.587 [INF] NTFN: New spend subscription: spend_id=1, outpoint=0857b273c2b9a4b8f5b0c54fa426dfba2bfe76667b034ab199dc7a10561cea9e:1, script=0 b0e308ef1231ceeb4bf8f19ab60dfc7edd7dd46e611102707293d8542ea6e537, height_hint=773783
2023-01-27 00:58:26.587 [INF] NTFN: Dispatching historical spend rescan for outpoint=0857b273c2b9a4b8f5b0c54fa426dfba2bfe76667b034ab199dc7a10561cea9e:1, script=0 b0e308ef1231ceeb4bf8f19ab60dfc7edd7dd46e611102707293d8542ea6e537, start=773783, end=773783
2023-01-27 00:58:26.605 [INF] CNCT: Close observer for ChannelPoint(0857b273c2b9a4b8f5b0c54fa426dfba2bfe76667b034ab199dc7a10561cea9e:1) active
2023-01-27 00:58:26.608 [INF] CNCT: ChannelArbitrator(0857b273c2b9a4b8f5b0c54fa426dfba2bfe76667b034ab199dc7a10561cea9e:1): starting state=StateDefault, trigger=chainTrigger, triggerHeight=773783
2023-01-27 00:58:28.480 [WRN] CHBU: Replacing disk backup for ChannelPoint(0857b273c2b9a4b8f5b0c54fa426dfba2bfe76667b034ab199dc7a10561cea9e:1) w/ newer version
2023-01-27 00:58:49.176 [INF] SRVR: Established connection to: 0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f@73.114.40.246:9735
2023-01-27 00:58:49.176 [INF] SRVR: Finalizing connection to 0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f@73.114.40.246:9735, inbound=false
2023-01-27 00:58:49.372 [INF] PEER: Peer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): loading ChannelPoint(0857b273c2b9a4b8f5b0c54fa426dfba2bfe76667b034ab199dc7a10561cea9e:1)
2023-01-27 00:58:49.372 [WRN] PEER: Peer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): Unable to find our forwarding policy for channel 0857b273c2b9a4b8f5b0c54fa426dfba2bfe76667b034ab199dc7a10561cea9e:1, using default values
2023-01-27 00:58:49.372 [INF] HSWC: ChannelLink(0857b273c2b9a4b8f5b0c54fa426dfba2bfe76667b034ab199dc7a10561cea9e:1): starting
2023-01-27 00:58:49.374 [INF] CNCT: Attempting to update ContractSignals for ChannelPoint(0857b273c2b9a4b8f5b0c54fa426dfba2bfe76667b034ab199dc7a10561cea9e:1)
2023-01-27 00:58:49.375 [INF] HSWC: ChannelLink(0857b273c2b9a4b8f5b0c54fa426dfba2bfe76667b034ab199dc7a10561cea9e:1): HTLC manager started, bandwidth=0 mSAT
2023-01-27 00:58:49.375 [INF] HSWC: ChannelLink(0857b273c2b9a4b8f5b0c54fa426dfba2bfe76667b034ab199dc7a10561cea9e:1): attempting to re-synchronize
2023-01-27 00:58:49.376 [INF] PEER: Peer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): Negotiated chan series queries
2023-01-27 00:58:49.376 [INF] DISC: Creating new GossipSyncer for peer=0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f
2023-01-27 00:58:49.388 [INF] DISC: GossipSyncer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): applying new update horizon: start=2106-02-07 06:28:15 +0000 UTC, end=2242-03-16 12:56:30 +0000 UTC, backlog_size=0
2023-01-27 00:58:49.608 [INF] HSWC: ChannelLink(0857b273c2b9a4b8f5b0c54fa426dfba2bfe76667b034ab199dc7a10561cea9e:1): received re-establishment message from remote side
2023-01-27 00:58:49.608 [ERR] LNWL: ChannelPoint(0857b273c2b9a4b8f5b0c54fa426dfba2bfe76667b034ab199dc7a10561cea9e:1): sync failed with local data loss: remote believes our tail height is 48058, while we have 0!
2023-01-27 00:58:49.608 [WRN] LNWL: ChannelPoint(0857b273c2b9a4b8f5b0c54fa426dfba2bfe76667b034ab199dc7a10561cea9e:1): detected restored triggering DLP
2023-01-27 00:58:49.608 [WRN] HSWC: ChannelLink(0857b273c2b9a4b8f5b0c54fa426dfba2bfe76667b034ab199dc7a10561cea9e:1): error when syncing channel states: ChannelPoint(0857b273c2b9a4b8f5b0c54fa426dfba2bfe76667b034ab199dc7a10561cea9e:1) with CommitPoint(037506c0e8e8d66da641755c4d69590941c7cf9bc43fa4c0384f7677eda1ccaa1c) had possible local commitment state data loss
2023-01-27 00:58:49.619 [ERR] HSWC: ChannelLink(0857b273c2b9a4b8f5b0c54fa426dfba2bfe76667b034ab199dc7a10561cea9e:1): failing link: unable to synchronize channel states: ChannelPoint(0857b273c2b9a4b8f5b0c54fa426dfba2bfe76667b034ab199dc7a10561cea9:1) with CommitPoint(037506c0e8e8d66da641755c4d69590941c7cf9bc43fa4c0384f7677eda1ccaa1c) had possible local commitment state data loss with error: unable to resume channel, recovery required
2023-01-27 00:58:49.620 [INF] HSWC: ChannelLink(0857b273c2b9a4b8f5b0c54fa426dfba2bfe76667b034ab199dc7a10561cea9e:1): exited
2023-01-27 00:58:49.620 [INF] HSWC: ChannelLink(0857b273c2b9a4b8f5b0c54fa426dfba2bfe76667b034ab199dc7a10561cea9e:1): stopping

[guggero]

Unfortunately you can't force close a channel if you have to restore from SCB, as that information is not contained in the backup file. Since you're able to connect to the remote node, they should force close. But because it looks like the peer is CLN, you might be hitting #7301, which would mean you'd need to wait for them to upgrade to a version that fixes the behavior. But I think the operator of the node is somewhat known and there should be ways to contact them.

[AiKawai]

Understood. It looks like there is nothing more i can do. I will wait patiently. Thank you very much.