LND generated too big onchain transaction

[Overtorment]

Background

Tried to consolidate some of utxos, and LND generated a pretty big tx (273 kb).
Tx was never broadcast by lnd, i.e. its not visible on block explorers.
I tried grabbing raw txhex manually from listchaintxns and broadcasting it, but all public apis reject it with Invalid transaction. Error: tx-size, code: -26
I would try to craft 5 times smaller transaction, but LND already thinks those utxos are spent.
What do I do here?

Your environment

• version of lnd v0.15.0-beta.rc1-dirty
• which operating system (uname -a on *Nix) Linux lnd2 4.15.0-161-generic #169-Ubuntu SMP Fri Oct 15 13:41:54 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
• bitcoind

Expected behaviour

Probably gracefully fail and not craft huge txs

[Roasbeef]

Being tracked here: #4760.

On restart lnd should try to rebroadcast, find it was rejected, and make those UTXOs available again.

Alternatively, you can use the PSBT APIs to do a fund PSBT call that specifies all the inputs in the too large transaction (in diff chunks), and then sign/finalize that to double spend it. Or construct a transaction with the inputs manually, and use the regular signrpc calls to generate valid transactions that spend a subset of the inputs.

[Overtorment]

will try restarting.
any way to make lnd forget or abandon a specific onchain tx?

[Roasbeef]

any way to make lnd forget or abandon a specific onchain tx?

A specific one: no (you can drop all transactions, but ofc that would be over kill). Even if you make+broadcast a new transaction that has just one overlapping input, and that one is mined, then lnd should free up all those UTXOs.

[Overtorment]

i think restarting didnt help.
ill try crafting 1 input tx to invalidate the whole bunch

[Overtorment]

well, spending a couple of inputs didnt help. even restarted lnd afterwards.
invalidated tx is still present on listchaintxns with

            "block_hash": "",
            "block_height": 0,

any other ideas?

[Roasbeef]

well, spending a couple of inputs didnt help. even restarted lnd afterwards.

Did the inputs get confirmed?

[Roasbeef]

Do you have the set of logs for when you first broadcasted the transaction?

You should see something like: unmatched backend error: -26: 64: tx-size. Right above that, it then shuld either say if it was unable to remove the transaction, or did successfully: https://github.com/btcsuite/btcwallet/blob/master/wallet/wallet.go#L3743-L3761

[Overtorment]

logs are lost, im afraid, but i dont remember such line when i was reading them

[Overtorment]

Did the inputs get con

yes, waited several confs

[Roasbeef]

So I went to reproduce this scenario (with an actual wallet instance), and found that the transaction was properly removed and the UTXOs were freed up as well. The PR I made (#6583) doesn't actually do anything in practice unfortunately: even without that upfront sanity check, the transaction is still removed.

[Overtorment]

so, basically, could not reproduce. weird.