loop
loop copied to clipboard
lightninglabs
very old failed swap never disappears
After asking in slack I was advised to open an issue.
An old swap/payment keeps popping up in loopd output and lnd logs. The swap was a loop out, dated 9th of July 2021. The loop out was to rebalance a channel. That channel has been closed succesfully on 12th of July 2021. The channel closing transaction has only one output, which holds all the sats I expected, as if the loop out did not happen.
The old swap that keeps popping up in the logs is in the output of both these commands:
loop listswaps|jq '.swaps[]|select(.state=="INITIATED")'
lncli listpayments --include_incomplete | jq '.payments[]|select(.status=="IN_FLIGHT")'
I can lncli decodepayment on the payment request. It shows an expiry equivalent to 365 days.
I'm not sure wat more information to provide. Is it possible to make the payment that will never succeed disappear?
The channel closing transaction has only one output, which holds all the sats I expected, as if the loop out did not happen.
It sounds like the loop out didn't succeed, can you confirm?
Also, please provide the logs you've mentioned and the respective outputs of those commands. Redact info as you require or send me an email at [email protected]
Ah I see the title now, appears it is failed. Please provide the logs requested in which case
Thanks for the report @lightningbrie!
What version of loop/lnd are you running? In the past we had an issue with payments getting stuck in INFLIGHT when they'd actually failed. Could be that, in which case upgrading lnd should suffice.
Hi @carlaKC and @arshbot , thank you for for looking into this. The current versions are loop 0.15.1-beta and lnd 0.14.1-beta.
I'm not sure what versions I was on in July. Probably what was current by then, as I tend to upgrade to new releases within a week.
Ah I see the title now, appears it is failed. Please provide the logs requested in which case
Does a grep abcdef loopd.log (abcdef being the first 6 characters of the payment) return any sensitive information that I shouldn't paste here? If so and the output would be useful, I would like to learn what to strip out so I can paste it.
If so and the output would be useful, I would like to learn what to strip out so I can paste it
Best practice is to xxxx out payment hash + channel IDs, but if you prefer to submit logs privately feel free to email them through or send on lnd slack (I'm just carla on there).
Useful information here would be the output of lncli trackpayment {swaphash}, so that we can see why the payment is stuck.
Looks like this may be related to lightningnetwork/lnd/issues/5461. Once we fix upstream, the stuck swap will clear.
Funds will all be back in your custody, it's just a matter of the payment being stuck in-flight when it's actually failed.