lnd: Payment status: IN_FLIGHT (stuck) - (updated) -> v0.13.1-beta.rc2

Background

We have payments that are stuck in “IN_FLIGHT” even after upgrading from v0.13.0rc3-beta to v0.13.0-beta. Here we will be analyzing just 1 of these payments with payment hash 41abd340f698c0db087b0d9f15cc0a514affd142108eed71d16a12c65d223b30

Your environment

version of lnd v0.13.0-beta
which operating system (uname -a on *Nix)
Ubuntu 20.04
version of btcd, bitcoind, or other backend
bitcoind zmq
any other relevant environment details docker

Steps to reproduce

Unsure, supposedly this was supposed to auto resolve. The expiration is 5000+ blocks after blockheight.

Expected behaviour

Auto resolve to Failed payment I would assume?

Actual behaviour

Still shows IN_FLIGHT using lncli trackpayment

Please see pastebin for details: https://pastebin.com/Ep8Sr2Sn ^ Above we have output of lncli trackpayment and after doing some pagination showing the output of the lncli listpayments

About this issue

Original URL
State: open
Created 3 years ago
Comments: 20 (1 by maintainers)

Most upvoted comments

running v0.13.1-beta.rc2 did not resolve this issue @yyforyongyu (updating title of issue).

Thanks for the update! This will be fixed in two steps,

clean the circuit maps for closed channels #4364
timeout payments when loading them from disk #5461

yyforyongyu on Aug 20, 2021

@yyforyongyu, just fyi… im @miketwenty1 You tagged the wrong Michael there. 😂

We currently have 676 IN_FLIGHT payments for this node.

@michael1011 Just to be sure, all these payments should have been marked as failed right?

Every "failure_reason" is "FAILURE_REASON_NONE"

miketwenty1 on Jun 30, 2021

I did respond to @yyforyongyu, I look forward to working with you. I provided the information you asked for on slack.

miketwenty1 on Jun 30, 2021

I messaged you information on slack, we can discuss there and post our conclusion/ findings here afterwards.

miketwenty1 on Jun 18, 2021