<p>Possibly related to: <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="414939024" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/bisq/issues/2474" data-hovercard-type="issue" data-hovercard-url="/bisq-network/bisq/issues/2474/hovercard" href="https://github.com/bisq-network/bisq/issues/2474">#2474</a>, <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="403767347" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/bisq/issues/2327" data-hovercard-type="issue" data-hovercard-url="/bisq-network/bisq/issues/2327/hovercard" href="https://github.com/bisq-network/bisq/issues/2327">#2327</a>. Uses <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="400284278" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/bisq/issues/2278" data-hovercard-type="issue" data-hovercard-url="/bisq-network/bisq/issues/2278/hovercard" href="https://github.com/bisq-network/bisq/issues/2278">#2278</a>.</p>
<p>This is a slightly edited re-post of the issue reported at:<br>
<a href="https://bisq.community/t/issue-bisq-startup-problem-on-slow-networks-3-4-problem/7233" rel="nofollow">https://bisq.community/t/issue-bisq-startup-problem-on-slow-networks-3-4-problem/7233</a></p>
<p><strong>Summary</strong>:<br>
On slow/congested networks, Bisq never progresses past step 3/4 of the startup sequence, due to a timeout occurring in the initial handshake to seed nodes.</p>
<p><strong>Details</strong>:<br>
One of the compulsory steps in the Bisq client startup sequence is a special handshake with a seed node, consisting in an exchange of large data packets in the 1.5 MB size range (PreliminaryGetDataRequest in the debug log). On slow networks, specifically when the network <em>output</em> channel is degraded, this handshake fails systematically with a timeout error, resulting in an inability to start up (the "3/4" problem).</p>
<p>Bisq versions tested: 0.8.1, 0.9.3, 0.9.4, 0.9.5<br>
Test platform: Tails 3.10, 3.11, 3.12 (Debian 9); Compatibility workarounds from <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="400284278" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/bisq/issues/2278" data-hovercard-type="issue" data-hovercard-url="/bisq-network/bisq/issues/2278/hovercard" href="https://github.com/bisq-network/bisq/issues/2278">#2278</a></p>
<p>To reproduce the bug, use a working Bisq installation and limit the network output bandwidth to a small value (100 kbps in my example) using the Linux TBF qdisc.</p>
<p><strong>Steps to reproduce</strong>:</p>
<ul>
<li>start with a correctly installed and tested operational copy of Bisq</li>
<li>close the application</li>
<li>in a terminal, execute (replace eth0 with name of default route interface):<br>
<code>sudo tc qdisc add dev eth0 root tbf rate 100kbit burst 1540 latency 50ms</code></li>
<li>start the application as usual</li>
</ul>
<p><strong>Expected result</strong>:<br>
Bisq should complete the startup sequence and operate (with some lag due to network bandwidth limitation).</p>
<p><strong>Actual result</strong>:<br>
Bisq never progresses past step 3/4 of startup sequence, resulting in complete no-op.</p>
<p><strong>Log fragment</strong></p>
<pre><code>Feb-26 12:16:38.651 [JavaFX Application Thread] INFO b.n.p.p.g.RequestDataHandler: We send a PreliminaryGetDataRequest to peer fl3mmribyxgrv63c.onion:8000.
Feb-26 12:17:38.555 [JavaFX Application Thread] WARN b.n.p.p.g.RequestDataManager: We have started already a requestDataHandshake to peer. nodeAddress=fl3mmribyxgrv63c.onion:8000
Feb-26 12:17:38.652 [JavaFX Application Thread] INFO b.n.p.p.g.RequestDataHandler: A timeout occurred at sending getDataRequest:PreliminaryGetDataRequest(supportedCapabilities=[0, 1, 2, 7]) on nodeAddress:fl3mmribyxgrv63c.onion:8000
Feb-26 12:18:44.754 [InputHandler-fl3mmribyxgrv63c.onion:8000] INFO b.n.p.n.Connection$SharedModel: Shut down caused by exception java.net.SocketTimeoutException: Read timed out on connection=Connection{peerAddress=Optional[fl3mmribyxgrv63c.onion:8000], peerType=SEED_NODE, uid=‘1c112047-32de-4631-93e9-5c6a175a30ee’}
Feb-26 12:18:44.774 [JavaFX Application Thread] INFO b.n.p.p.PeerManager: onDisconnect called: nodeAddress=Optional[fl3mmribyxgrv63c.onion:8000], closeConnectionReason=CloseConnectionReason{sendCloseMessage=false, isIntended=false} SOCKET_TIMEOUT
Feb-26 12:18:44.822 [JavaFX Application Thread] INFO b.n.p.p.p.PeerExchangeManager: onDisconnect closeConnectionReason=CloseConnectionReason{sendCloseMessage=false, isIntended=false} SOCKET_TIMEOUT, nodeAddressOpt=Optional[fl3mmribyxgrv63c.onion:8000]
</code></pre>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/bisq/issues/2547">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AkpZtp8HMWWtynlKmOQP5Yp-FUBGwvo8ks5vXZCGgaJpZM4b4HAA">mute the thread</a>.<img src="https://github.com/notifications/beacon/AkpZtu0Cw4q0zdjeCcNv0I-ry4sF3VlEks5vXZCGgaJpZM4b4HAA.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/bisq-network/bisq","title":"bisq-network/bisq","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/bisq-network/bisq"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"Startup problem on slow/degraded networks (the \"3/4\" problem) (#2547)"}],"action":{"name":"View Issue","url":"https://github.com/bisq-network/bisq/issues/2547"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/bisq/issues/2547",
"url": "https://github.com/bisq-network/bisq/issues/2547",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>