App backend unresponsive after open-closing LN channel multiple times #1187
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
|
I'll see whether I can reproduce it on a desktop build (it would do wonders for debuggability to have it on local machine). |
|
Some logs from my phone: run 1: You can see that between sending run 2: |
|
@holzeis how did you run the app? was it the 10101-test or self-deployed with this is likely not correct! |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Closing for now, reopen if the issue reappears. |
This was
linked to
pull requests
Aug 30, 2023
|
Reopening, as it just happened to me on the latest build 1.2.3 (1965) that the app got stuck (see logs). This time the attempt to paying the JIT channel opening fees have been triggered after the channel has been updated. https://nextcloud.holzeis.me/s/aRtN9LBDREBfHwL What have I done?I constantly opened a channel and closed it again. After the 8 or 9th attempt I got the app in a state where it wasn't responding anymore (resp. hanging). |
Do you really mean opening and closing a channel? Or do you mean opening closing a sub-channel / position |
I really mean opening and closing a lightning channel. |
luckysori
changed the title
Merged
|
I am removing this ticket from the current iteration as the described scenario is not as critical anymore. Also this may get fixed with upgrading ldk to 0.1.116. Let's revisit this bug afterwards again. |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are seeing quite a lot of ping timeouts to the app on the latest version on the coordinator 1.2.3 (1937). It appears there is some blocking task running on the phone that is responsible for those timeouts.
Testing the latest version on regtest 1.2.3 (1937) funding the wallet, opening or closing a position were randomly failing or taking a very long time. e.g. we observed that processing a
SubChannelCloseFinalizetook about 2 minutes on the phone for no apparent reason. (No logs in between processingSubChannelCloseConfirmmessage and sendingFinalizemessage)We presume the ping timeout is just one symptom of that issue.
https://itchysats.grafana.net/explore?orgId=1&panes=%7B%22U8i%22:%7B%22datasource%22:%22grafanacloud-logs%22,%22queries%22:%5B%7B%22refId%22:%22A%22,%22datasource%22:%7B%22type%22:%22loki%22,%22uid%22:%22grafanacloud-logs%22%7D,%22editorMode%22:%22builder%22,%22expr%22:%22%7Bcontainer%3D%5C%22coordinator%5C%22,%20setup%3D%5C%22get10101-regtest%5C%22%7D%20%7C%3D%20%60ping%20timeout%60%20%7C%20json%22,%22queryType%22:%22range%22%7D%5D,%22range%22:%7B%22from%22:%22now-1h%22,%22to%22:%22now%22%7D%7D%7D&schemaVersion=1
The text was updated successfully, but these errors were encountered: