failing link: internal error with error: remote error #8332
Replies: 4 comments
-
I received additional information from my peer :
My peer added on my advice this line :
...to his Unfortunately, it doesn't help. |
Beta Was this translation helpful? Give feedback.
-
The remote node has a balance of 58063 and a reserve requirement of 55000, plus an outgoing htlc of 50000, which caused this line to be executed: Line 3900 in 4d8fa34 Unfornately I don't think there's an easy fix, as the channel has already dipped below chan reserve. However this should not happen again once #8096 is merged. |
Beta Was this translation helpful? Give feedback.
-
Hey @yyforyongyu , can you guys release a hotfix for those cases to enable the channel to get online? Then, we can send an HTLC to balance the channel manually. I'm going to the 5th lost channel to this bug. |
Beta Was this translation helpful? Give feedback.
-
Unfortunately, today nodes will just retransmit exactly what they sent before the last connection. In this case, it'll keep sending that HTLC that violates the reserve constraints. This is a known edge case in the spec. The PR linked above should prevent it, but since there's no way to revert a commitment in the protocol today, the channel will need to be force closed in order to continue.
That config will allow 100% of your balance to go to fees, which I don't think is what you actually want. What's happening is that you don't have enough balance in the channel (or your peer) to pay for the HTLC. Closing for now as we have #8096 which will work around this quirk in the spec to prevent this from happening in the future. This might be happening more frequently due to higher fees persistently on chain. One way to work around this, would be to start to increase the reserve of the channels you start to open. This gives you more buffer room to pay for HTLC fees. Ultimately, there's a circular requirement here: as you need fees to be able to pay for HTLCs, even when sending. We can continue in a discussion if y'all would like. |
Beta Was this translation helpful? Give feedback.
-
Me : LND 0.17.3, bitcoind 25 (full indexed, mempool = 3Gb), Ubuntu, clearnet only
My peer : LND 0.17.3, bitcoind 25, Linux, hybrid (clearnet+tor)
Immediately after the connection with my peer is restored, my HSWC fails the link.
The log from my side is quite short :
The log from my peer's side (UPD: there are more logs below) :
There are some pending HTLCs in our channel :
Please note the HTLC with
"htlc_index": "66407"
because in the log :UpdateFailHTLC(chan_id=3e5b08f59ea851889964fbb5d4d6e6a722c4b488d68f2162f82eca9d6177e875, id=66407
The state of the channel (from my side) :
My peer's node restart doesn't help, the channel remains disabled.
This channel will be FCed soon because of a HTLC expiration.
Can I (or my peer) do something to prevent it?
We are ready to provide any necessary information.
Beta Was this translation helpful? Give feedback.
All reactions