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

Unhandled unrecoverable program state following failed handshake with seed nodes #2549

Closed
agb19 opened this issue Mar 17, 2019 · 2 comments
Closed
Assignees
Labels
a:bug in:network is:critical https://bisq.wiki/Critical_bug is:priority PR or issue marked with this label is up for compensation

Comments

@agb19
Copy link
Contributor

agb19 commented Mar 17, 2019

Related to: #2547, possibly #2474, #2327

This is a slightly edited re-post of the issue reported at:
https://bisq.community/t/issue-bisq-startup-problem-on-slow-networks-3-4-problem/7233/3

Details:
After a network congestion/degradation during startup (issue #2547), Bisq remains in a dead-end state that doesn't recover even after the network performance is restored. The only way to recover is restarting the program.
This condition is not properly handled nor reported in the UI, causing confusion to unaware users.

Steps to reproduce

Expected result
The program should attempt to recover seamlessly from the degraded state when the network conditions allow it.

Alternative expected result
The program should detect the dead-end state and report it in the UI along with some information about its probable cause, then exit or restart in order to attempt to recover from this state.

Actual result
The program keeps running, displays a progress indicator and shows the offers, trades, wallet contents, exchange rates etc, creating a false appearance of almost-operational and a false expectation of further progress, when in reality it is in an unrecoverable no-op state.

@agb19 agb19 changed the title Unhandled unrecoverable program state following failed seed handshake Unhandled unrecoverable program state following failed handshake with seed nodes Mar 17, 2019
@agb19
Copy link
Contributor Author

agb19 commented Apr 11, 2019

After further testing on this issue, I have some additional information.
Completely removing network connectivity for 30 seconds, effectively bringing the application into "all connections lost" state, appears to reset this condition and re-enable the application to attempt seed node handshakes, which, subject to improved network conditions, may lead to a successful startup.

Tested multiple times on a laptop computer using the hardware wifi switch.

(Bisq versions: 0.9.5 - 0.9.8)

@ripcurlx
Copy link
Contributor

Related to: #3797 #1023 #3763 #3347

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:bug in:network is:critical https://bisq.wiki/Critical_bug is:priority PR or issue marked with this label is up for compensation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants