Unhandled unrecoverable program state following failed handshake with seed nodes #2549
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
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
sudo tc qdisc add dev eth0 root tbf rate 100kbit burst 1540 latency 50ms
sudo tc qdisc del ...
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.
The text was updated successfully, but these errors were encountered: