Open KISBITCOIN opened 4 years ago
@KISBITCOIN Please include the log files. A screenshot of the UI is not useful for debugging this.
bisq.log from here: https://docs.bisq.network/backup-recovery.html#data-directory
I wiped the entire application and app support folder and got it to work.
I've reopened this issue because it has completely stopped my client from working. Logs attached. bisq.log
Related to: #3797 #1023 #3763 #3347 #2549
I have the very same issue when I am on "slower" internet connection.
My hypothesis is:
Plus, it's burning CPU in meatime like crazy.
I have the very same issue when I am on "slower" internet connection.
My hypothesis is:
- Bisq requires 12 nodes to connect.
- On slow connection, it takes "forever" to connect to a node.
- In the meantime, already connected nodes stats to disconnect (visible in UI and in the logs).
- Result: Bisq seems to be stucked on 10/12 (or something like that - depending on connection speed).
Plus, it's burning CPU in meatime like crazy.
This issue is worked on right now: https://github.com/bisq-network/bisq/pull/4233
@chimp1984 has this (and other "3/4" issues) been fixed by #4586 ?
Not entirely. We have seen those issues still happening. Last weeks Tor was quite unstable due the v3 address issues with authority dir dos. So I did not look further what can be the reason for it. I have very slow internet and it happens frequently to me. I assume timeouts on requester or seeds causes it. But would be great if you dig into that.
Also ran into this issue today as well. Bisq started after I've update to the newest version, restarting it several times and finally waited roughly 5min.
OS: Debian/Qubes
@Siproqu Can you try again? There seems to have been some issue with seed nodes.
Today everything went fine.
Since 3 days I have this issue. After some while it tells me about TOR issues but nothing fixes these. TOR browser works from here.
I see in the logs that my BTC node appears to be missing bloom filters but the symptoms are the same when I don't run a local node and the message is that there's an issue with TOR either way.
Looked at your logs. Never saw those issues before. Maybe try to restart your OS. Have a look in your bitcoin core node if you can see bisq as connected peer. It seems there is a conncetion issue to your bitcoin node which is unrelated to tor. You can also try with a new fresh data dir, just to see if it might be related to some corrupted data. If that works but your normal data directory not, try to delete the spv file and resync.
May-10 00:16:13.253 [NioClientManager] INFO o.b.c.PeerGroup: [127.0.0.1]:8333: Peer died (0 connected, 0 pending, 1 max)
May-10 00:16:13.253 [NioClientManager] INFO o.b.c.PeerGroup: Not yet setting download peer because there is no clear candidate.
May-10 00:16:13.253 [PeerGroup Thread] INFO o.b.c.PeerGroup: Waiting 1500 ms before next connect attempt to [127.0.0.1]:8333
May-10 00:16:13.255 [NioClientManager] WARN o.b.n.ConnectionHandler: Error handling SelectionKey: java.nio.channels.CancelledKeyException java.nio.channels.CancelledKeyException: null
at java.base/sun.nio.ch.SelectionKeyImpl.ensureValid(SelectionKeyImpl.java:71)
at java.base/sun.nio.ch.SelectionKeyImpl.readyOps(SelectionKeyImpl.java:130)
I've seen the very same issue. It started while I was on v1.9.14, then upgrading to v1.9.15 made no difference. It can also be seen in GUI Settings -> Network Info. Connected bitcoin node keeps appearing and disappearing.
I have tried all sorts of things, including deleting spv wallet and rebuilding the bitcoin node from scratch. Only way I could fix it was to migrate to a completely new bitcoin wallet.
Hm... weird... @alvasw: Do you have any idea?
I restarted the OS and deleted the SPV files before reporting this issue. I also tried to connect to a different BTC node by not starting my own node but find the information in the UI very limiting and not helpful as to what's going on.
Edit: I don't see "GUI Settings -> Network Info" in Bisq. It's stuck on "Connecting to Bitcoin network". When I start bisq without a local bitcoin node, it's stuck on the startup screen, too. No "GUI Settings" button anywhere.
So ... how can I resume using bisq? Can I down-grade? I think it forced me to up-grade in the first place.
There will be a new version deployed soon. There have been some fixes with tor issues, hope that will have resolved your issue. But it seems some local issue on your side. Might be also some tor ddos protection issue. I had in the past a time where I could not connect anything anymore only when using a VPN it worked again. After 2-3 months it worked normally again. Might have been the ISP as well...
I tried with both my mobile provider and my landline and both look equal.
Have you tries with using a local (unpruned) Bitcoin node? The current Tor ddos affects the connectivity to the provided BTC nodes. See https://github.com/bisq-network/bisq/discussions/7112
My local node is not pruned and I have tried with it, although it's not clear to me if bisq did pick it up or if it connected over tor to some other node anyway.
If you have a localhost node running Bisq use that and for the first time you also see a popup in Bisq. You also see then at your Bitcoin node that Bisq has a connection to it. In Bisq you see that its only 1 BTC node and at Settings/Network you see details.
I'm still lost regarding what to do. I get to stare at this:
for some minutes and then:
and then:
Bisq did work before and to my knowledge, nothing is blocking TOR here in Chile. Above you also see logs.
I'm offering $100 for a comment or patch that actually fixes my problem.
I had a similar issue recently.
The problem seemed to be related to Bisq dropping connections to the provided bitcoin nodes, but I think it can affect people using their own node also.
Something similar to https://groups.google.com/g/bitcoinj/c/R14TzTo-yBI
I think it was the case it was trying to look up too many addresses and therefore failing to connect to the nodes.
I would reccomend loading up Bisq letting it try and connect for 10 mins and then take a look at your most recent log file. See if there are errors when connecting to the nodes.
You can paste here the relevant section or send to me on Matrix: pazza83:matrix.org
Description
Application is stuck on step 3/4.
Version
1.2.4 Mac Os
Steps to reproduce
Expected behaviour
Actual behaviour
Screenshots
Device or machine
Mac Os Mojave 10.14.6