[bug]: pendingsweeps empty after

[cocktailsk]

Background

I had a forcelosed channel in this tx: https://mempool.space/tx/a9c786f914f9ffde990e6c1213112701dac9642694f5f3e34c5bacb2420fe435#flow=&vout=5

the last output was not swept and a after the update to 0.19.1 the lncli wallet pendingsweeps is empty
$ lncli wallet pendingsweeps

{
    "pending_sweeps": []
}

the pendingchannels still shows balance in limbo 499065

$ lncli pendingchannels

{
    "total_limbo_balance":  "499065",
    "pending_open_channels":  [
        {
            "channel":  {
                "remote_node_pub":  "02e91ff08cba7981d73dd56fbb3e9123b101c9c94aafd27a7d70094ae479ba2c18",
                "channel_point":  "4a30680c6ea4561763a4043fb29a3bd2ac24e71606628c4781397e73985290b7:2",
                "capacity":  "4546609",
                "local_balance":  "0",
                "remote_balance":  "4544544",
                "local_chan_reserve_sat":  "45466",
                "remote_chan_reserve_sat":  "45466",
                "initiator":  "INITIATOR_REMOTE",
                "commitment_type":  "ANCHORS",
                "num_forwarding_packages":  "0",
                "chan_status_flags":  "",
                "private":  false,
                "memo":  "",
                "custom_channel_data":  ""
            },
            "commit_fee":  "1405",
            "commit_weight":  "772",
            "fee_per_kw":  "1250",
            "funding_expiry_blocks":  1482
        }
    ],
    "pending_closing_channels":  [],
    "pending_force_closing_channels":  [
        {
            "channel":  {
                "remote_node_pub":  "0319117eb1ed3b90b7be6ca2e309afc61dff987154d8aa50a421fec0be51aa2b15",
                "channel_point":  "767b368ad7b047a2d39d22b2acdb831d297049b789170f6e55790ebffd08ee1a:1",
                "capacity":  "999999",
                "local_balance":  "187750",
                "remote_balance":  "11631",
                "local_chan_reserve_sat":  "0",
                "remote_chan_reserve_sat":  "0",
                "initiator":  "INITIATOR_REMOTE",
                "commitment_type":  "ANCHORS",
                "num_forwarding_packages":  "0",
                "chan_status_flags":  "",
                "private":  false,
                "memo":  "",
                "custom_channel_data":  ""
            },
            "closing_txid":  "a9c786f914f9ffde990e6c1213112701dac9642694f5f3e34c5bacb2420fe435",
            "limbo_balance":  "499065",
            "maturity_height":  0,
            "blocks_til_maturity":  0,
            "recovered_balance":  "0",
            "pending_htlcs":  [
                {
                    "incoming":  false,
                    "amount":  "499065",
                    "outpoint":  "79098bb2e7291b6eb8b37eda2d599608f2cbe664ef508ebadfa4c91d45a476af:0",
                    "maturity_height":  902529,
                    "blocks_til_maturity":  -2086,
                    "stage":  1
                }
            ],
            "anchor":  "LOST"
        }
    ],
    "waiting_close_channels":  []
}

the LND log does not show any "SWPR"
for the channel point I found this in the logs:
lightning_lnd_1 | 2025-07-08 16:40:48.048 [INF] CNCT: ChannelArbitrator(767b368ad7b047a2d39d22b2acdb831d297049b789170f6e55790ebffd08ee1a:1): skipping reading close events in state=StateWaitingFullResolution

Your environment

• version of lnd update to 0.19.1
• Umbrel

[yyforyongyu]

Can you restart your node with debug mode? I'm looking for SWPR=debug,CNCT=debug

[cocktailsk]

Nothign for SWPR, below 2 lines for CNCT

lightning_lnd_1 | 2025-07-09 13:09:18.171 [INF] CNCT: ChannelArbitrator(767b368ad7b047a2d39d22b2acdb831d297049b789170f6e55790ebffd08ee1a:1): skipping reading close events in state=StateWaitingFullResolution

lightning_lnd_1 | 2025-07-09 13:09:18.172 [INF] CNCT: ChannelArbitrator(4a30680c6ea4561763a4043fb29a3bd2ac24e71606628c4781397e73985290b7:2) no close event

[cocktailsk]

Adding the log file for more details based on @guggero 's suggestion (thanks)
umbrel_lightning_2025-07-18_18-12.log

[guggero]

Thanks. This is just the summary log from all services. But we need the full lnd.log (not sure where Umbrel keeps that).

[cocktailsk]

got it here you go: lnd.log

[guggero]

Thanks, that's the correct log. But I don't really see any debug output of the sweeper. Did you do this as well?

#10053 (comment)

[cocktailsk]

sorry learning step by step what works and how, hope this is what is needed
lnd (5).log

[guggero]

Yes, this looks better, thanks!

@yyforyongyu looks like the sweeper is confused because the anchor has already been spent:

2025-07-21 10:25:44.405 [WRN] SWPR: Failing record=1: found orphan inputs: a9c786f914f9ffde990e6c1213112701dac9642694f5f3e34c5bacb2420fe435:1 (CommitmentAnchor)
a9c786f914f9ffde990e6c1213112701dac9642694f5f3e34c5bacb2420fe435:5 (HtlcOfferedTimeoutSecondLevelInputConfirmed)
26dc041ddaf5e28c255be2bc6b48d90794483178dabd7351e8a2603c72bba336:0 (TaprootPubKeySpend)
ba82ef976a435cd38cef60477f9ad48a1ddf2aaea29e8ae8a963cfe7666ac124:0 (TaprootPubKeySpend)

2025-07-21 10:25:44.405 [INF] SWPR: Tx=cc467b29a8420111b8591f4ccd3cc40bff2ea0fd37cd1c7e152a6c7e0cb944c6 failed with unexpected error: input no longer exists
2025-07-21 10:25:44.410 [ERR] SWPR: Failed to sweep input: a9c786f914f9ffde990e6c1213112701dac9642694f5f3e34c5bacb2420fe435:5 (HtlcOfferedTimeoutSecondLevelInputConfirmed), error: input no longer exists
2025-07-21 10:25:44.410 [ERR] SWPR: Failed to sweep input: a9c786f914f9ffde990e6c1213112701dac9642694f5f3e34c5bacb2420fe435:1 (CommitmentAnchor), error: input no longer exists
2025-07-21 10:25:44.410 [WRN] CNCT: ChannelArbitrator(767b368ad7b047a2d39d22b2acdb831d297049b789170f6e55790ebffd08ee1a:1): *contractcourt.anchorResolver(a9c786f914f9ffde990e6c1213112701dac9642694f5f3e34c5bacb2420fe435:1): our anchor spent by someone else
2025-07-21 10:25:44.410 [INF] CNCT: ChannelArbitrator(767b368ad7b047a2d39d22b2acdb831d297049b789170f6e55790ebffd08ee1a:1): *contractcourt.anchorResolver(a9c786f914f9ffde990e6c1213112701dac9642694f5f3e34c5bacb2420fe435:1): resolved in tx <nil>
2025-07-21 10:25:44.434 [INF] CNCT: ChannelArbitrator(767b368ad7b047a2d39d22b2acdb831d297049b789170f6e55790ebffd08ee1a:1): a contract has been fully resolved!
2025-07-21 10:25:44.434 [INF] CNCT: ChannelArbitrator(767b368ad7b047a2d39d22b2acdb831d297049b789170f6e55790ebffd08ee1a:1): still awaiting contract resolution

[yyforyongyu]

yeah it's the same as #10051, will be fixed by #10060. Meanwhile you can this approach to fix it mannually.