Closed t-bast closed 4 years ago
Thanks for the report! Not much we can do on our end without knowing the version of lnd
the user was running. We believe that we've fixed the prior instances of state de-sync upon reconnection with v0.9.1
, which was released a few weeks ago.
I just got word from the operator, he was running 0.8.0 at the time and upgraded two days later (too bad). So you believe this is fixed in 0.9.0?
So you believe this is fixed in 0.9.0?
v0.9.1
(our latest release)
Closing for now as based on the current information the user was running a version before our fix landed.
I've been investigating a force-close we experienced with an lnd node after a re-start. During the HTLC fulfill, we rebooted after sending our
revoke_and_ack
but before sending ourcommit_sig
. Here are the logs from my side:When we reconnect, lnd expects the commit tx that still has the HTLC, whereas they did send their
commit_sig
and received ourrevoke_and_ack
. Notice how the commitment numbers don't match up the way they should.I have reached out to the operator of the lnd node (zapread.com) to find out what version they're running and ideally get their logs. I'll update this issue once I have them. If you know how to reach the owner, please ping them on my behalf.
However it feels to me that this is somewhat easy to reproduce with the exact steps the logs show (unless there's a tricky race condition happening).
Let me know how I can help, it would be great to reduce those channel close on reconnect.