Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug]: rebalance payment stuck and cause force close #7509

Closed
scissorstail opened this issue Mar 12, 2023 · 5 comments
Closed

[bug]: rebalance payment stuck and cause force close #7509

scissorstail opened this issue Mar 12, 2023 · 5 comments
Labels
bug Unintended code behaviour needs triage

Comments

@scissorstail
Copy link

scissorstail commented Mar 12, 2023

Background

Describe your issue here.

Your environment

  • 0.15.5-beta
  • Linux server 5.15.0-67-generic x86_64 x86_64 x86_64 GNU/Linux
  • bitcoind:v24.0.1
  • Using docker image from lightninglabs/lnd:v0.15.5-beta, bitcoind is running on another machine and connected with RPC

Steps to reproduce

During rebalancing, sometimes certain attempts do not resolve until they are force-closed.
I have confirmed that all nodes on the rebalancing path are alive.

There are currently two HTLCs in the same situation, with 64(resolved) and 95 hours left until expiration, respectively.
I am losing channels little by little.

Expected behaviour

Rebalance HTLC resolved

Actual behaviour

Rebalance HTLC not resolved and finally force-closed

@scissorstail scissorstail added bug Unintended code behaviour needs triage labels Mar 12, 2023
@alexbosworth
Copy link
Contributor

what is your cltv delta?

@scissorstail
Copy link
Author

It is 144.

@ziggie1984
Copy link
Collaborator

; A period to wait before for closing channels with outgoing htlcs that have
; timed out and are a result of this nodes instead payment. In addition to our
; current block based deadline, if specified this grace period will also be taken
; into account. Valid time units are {s, m, h}.
; payments-expiration-grace-period=30s

Set this in your config to a very high value and you should be fine!

@scissorstail
Copy link
Author

Since the two mentioned HTLCs have been resolved, I cannot be certain if the rebalance was the cause. As it's resolved now, I close this issue. thanks.

@scissorstail
Copy link
Author

It happened again today in front of me and I checked the logs. It is a duplicate of #7180
But I don't know why this is happening almost once a week. I think it would be better to reduce the rebalance attempts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unintended code behaviour needs triage
Projects
None yet
Development

No branches or pull requests

3 participants