[bug]: failing link: peer sent us an HTLC that exceeded our max fee exposure with error: internal error

[emtll]

Background

Describe your issue here.

Your environment

• lnd v0.18.3-beta
• Linux minibolt 6.8.0-45-generic Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 30 12:02:04 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
• Bitcoin Core RPC client version v27.0.0

Actual behaviour

I don't know the reason for the error, but the channel goes offline and displays the following log. It does not return when attempting to reconnect. If there is a pending htlc, it remains disconnected until it expires and generates a force close.

Logs:

2024-10-17 12:17:19.949 [INF] PEER: Peer(035adfeca8fc95de5e2e9dbf9be39ac577b510e7dad0ad9287117d01f282eb667a): Loading ChannelPoint(4457ca2bff2f0bbd59ef5649dbfa7ffa86ee13ba6f2f3c5c01b1406fef049739:1), isPending=false
2024-10-17 12:17:19.950 [INF] HSWC: ChannelLink(4457ca2bff2f0bbd59ef5649dbfa7ffa86ee13ba6f2f3c5c01b1406fef049739:1): starting
2024-10-17 12:17:19.950 [INF] CNCT: Attempting to update ContractSignals for ChannelPoint(4457ca2bff2f0bbd59ef5649dbfa7ffa86ee13ba6f2f3c5c01b1406fef049739:1)
2024-10-17 12:17:19.950 [INF] HSWC: ChannelLink(4457ca2bff2f0bbd59ef5649dbfa7ffa86ee13ba6f2f3c5c01b1406fef049739:1): HTLC manager started, bandwidth=2233694 mSAT
2024-10-17 12:17:19.950 [INF] HSWC: ChannelLink(4457ca2bff2f0bbd59ef5649dbfa7ffa86ee13ba6f2f3c5c01b1406fef049739:1): Attempting to re-synchronize channel: SCID=861793:1950:1, status=ChanStatusDefault, initiator=false, pending=false, local commitment has height=598778, local_htlc_index=23606, local_log_index=316474, remote_htlc_index=292869, remote_log_index=316660, remote commitment has height=602941, local_htlc_index=23606, local_log_index=316474, remote_htlc_index=292869, remote_log_index=316660
2024-10-17 12:17:19.950 [INF] HSWC: ChannelLink(4457ca2bff2f0bbd59ef5649dbfa7ffa86ee13ba6f2f3c5c01b1406fef049739:1): received re-establishment message from remote side
2024-10-17 12:17:20.287 [ERR] HSWC: ChannelLink(4457ca2bff2f0bbd59ef5649dbfa7ffa86ee13ba6f2f3c5c01b1406fef049739:1): failing link: peer sent us an HTLC that exceeded our max fee exposure with error: internal error
2024-10-17 12:17:20.287 [ERR] HSWC: ChannelLink(4457ca2bff2f0bbd59ef5649dbfa7ffa86ee13ba6f2f3c5c01b1406fef049739:1): link failed, exiting htlcManager
2024-10-17 12:17:20.287 [INF] HSWC: ChannelLink(4457ca2bff2f0bbd59ef5649dbfa7ffa86ee13ba6f2f3c5c01b1406fef049739:1): exited
2024-10-17 12:17:20.287 [INF] HSWC: ChannelLink(4457ca2bff2f0bbd59ef5649dbfa7ffa86ee13ba6f2f3c5c01b1406fef049739:1): stopping

[ziggie1984]

can you check your dust-treshold config value and remove it from your config

[ziggie1984]

relates to #9182

[emtll]

Oh! Thank you!

[ziggie1984]

Closing because LND behaves as expected. We probably wanna remove the config setting so users don't shoot themselves in the foot.

[ziggie1984]

can you also check your setting for max-commit-fee-rate-anchors normally 100k(for the dust-treshold) should be good enough. Moreover are you restricting htlcs on the channel, feels like your channel is spammed with HTLCs?

[emtll]

In this channel that was off there was only 1, but I already had the same problem in another channel with 39 pending htlcs