Investigate and fix startup issues #7112
Replies: 1 comment
Test run 1Startup sequenceMay-24 21:32:29.211: Starting tor May-24 21:33:01.044: Tor started after 31833 ms May-24 21:33:01.202: We send a PreliminaryGetDataRequest to peer devinsn3xu... May-24 21:33:01.349: We send a PreliminaryGetDataRequest to peer sn3emzy56u... (475.525 kB) May-24 21:33:01.896 Read 411 checkpoints up to time 2024-02-02 May-24 21:33:42.305 Tor hidden service published after 41258 ms. May-24 21:33:51.181 Socket creation to peersNodeAddress sn3emzy56u3mxzsr4geysc52feoq5qt7ja56km6gygwnszkshunn2sid.onion:8000 took 49824 ms May-24 21:33:52.297 May-24 21:35:03.636: Received a GetDataResponse with 5.019 MB from sn3emzy56u.... May-24 21:35:04.629:We send a GetUpdatedDataRequest to peer sn3emzy56u3mxzsr... (634.982 kB) Series of Bitcoinj timeouts (7 nodes) May-24 21:35:54.211 Received a GetDataResponse with 2.377 MB from sn3emzy56u3mxzsr4geys... May-24 21:35:56.500 We send a GetUpdatedDataRequest to peer sn3emzy56u3m... (765.042 kB) May-24 21:36:20.354 We send a GetUpdatedDataRequest to peer sn3emzy56u3m.. (875.037 kB) May-24 21:36:29.214 [JavaFX Application Thread] WARN bisq.core.app.BisqSetup: startupTimeout called -> displays Tor debug window May-24 21:36:35.609 Received a GetDataResponse with 192.045 kB from sn3emzy56u3mxzsr... May-24 21:36:35.651 [JavaFX Application Thread] INFO b.n.p2p.peers.getdata.RequestDataHandler: May-24 21:38:40.520 Received a GetDataResponse with 1.845 kB (all data received) from devinsn3xuzxhj6... After that logs get filled up with BitcoinJ issues... BTC sync stuck at 99% at May-24 22:12 -> more then 35 min after start. Full logs: |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Many users experience issues when starting up Bisq.
Here is an overview, analysis and suggestions how to fix some of the issues.
Test setup:
I will post each test run as a new post to not overload the content here.
Actions:
BitcoinJ
Announcing to emzybtc5bnpb2o6gh54oquiox54o4r7yn4a2wiiwzrjonlouaibm2zid.onion/<unresolved>:8333 as: /bitcoinj:0.15.10.bisq.16/Bisq:1.9.15/./<unresolved>is just a log at InetSocketAddress asaddris null.May-24 22:09:53.384 [PeerGroup Thread] INFO org.bitcoinj.core.PeerGroup: Waiting 78610 ms before next connect attempt to [emzybtc454ewbviqnmgtgx3rgublsgkk23r4onbhidcv36wremue4kqd.onion]:8333logs.rfqmn3qe36uaptkxhdvi74p4hyrzhir6vhmzb2hqryxodig4gue2zbydandazbpsh4arqlm6442wfimy7qr65bmha2zhgjg7wbaji6vvaug53hur2qdseems like having constant issues.P2P network
We start a cleanup timer if the handler has not closed by itself in between 2 minutes.
All reactions