Walletwasabi: CoinJoin "freezing"

[ghost]

General Description

Sometimes, a few times a day, CoinJoin freezes at "signed" phase. Nothing happens for as long as I keep Wasabi Wallet open - it just stays at "signed"/"signing" and I need to restart.
Not that CoinJoin normally fail for any reason, but my CoinJoin get stuck at "signed" or "signing" and I can wait for maybe hours, nothing will happen until I restart Wasabi Wallet. Once I restart, I see that clock is counting and next coinjoin is in like 10 minutes.

Again, it's not that it fails. It just get to "signed" or "signing" part and it remains like that for a long time.

How To Reproduce?

I can't reproduce. It just happens randomly.

Screenshots

Not sure if screenshot will help, but here it is.

https://imgur.com/a/v0rovEp

So, it just remains like that and nothing happens until I restart.

Operating System

Windows 10

Logs

It looks like there is nothing special in Logs.txt.

This is from last time it happen:

_2020-07-16 20:12:33 INFO Global (605) Transaction Notification (Success): - CoinJoin Completed! - 9409694f6c5b5c158999e423ee9dbe00f09fabf697389a890fb44126bd46e2f8_

Next INFO is when I'm shutting down to restart:

_2020-07-16 20:31:05 INFO ClientState (60) Coin removed from the waiting list: XXXXXXXXX_
...
_2020-07-16 20:31:09 INFO Global (729) Nodes are disposed.
2020-07-16 20:31:09 INFO Global (754) TorManager is stopped._
...
etc...

There is something more in meantime in TorLogs.txt:

_Jul 16 20:20:37.000 [warn] Application request to port 110: this port is commonly used for unencrypted protocols. Please make sure you don't send anything you would mind the rest of the Internet reading!
Jul 16 20:20:37.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
Jul 16 20:20:37.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
Jul 16 20:20:39.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
Jul 16 20:22:11.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $882D5F210B798BA3133B1B69ACD9591DD5FB5B60~Unnamed at 54.38.81.231. Retrying on a new circuit.
Jul 16 20:22:11.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $882D5F210B798BA3133B1B69ACD9591DD5FB5B60~Unnamed at 54.38.81.231. Retrying on a new circuit.
Jul 16 20:22:11.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $882D5F210B798BA3133B1B69ACD9591DD5FB5B60~Unnamed at 54.38.81.231. Retrying on a new circuit.
Jul 16 20:22:12.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $882D5F210B798BA3133B1B69ACD9591DD5FB5B60~Unnamed at 54.38.81.231. Retrying on a new circuit.
Jul 16 20:22:12.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $882D5F210B798BA3133B1B69ACD9591DD5FB5B60~Unnamed at 54.38.81.231. Retrying on a new circuit.
Jul 16 20:22:15.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $882D5F210B798BA3133B1B69ACD9591DD5FB5B60~Unnamed at 54.38.81.231. Retrying on a new circuit.
Jul 16 20:22:17.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $882D5F210B798BA3133B1B69ACD9591DD5FB5B60~Unnamed at 54.38.81.231. Retrying on a new circuit.
Jul 16 20:22:23.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
Jul 16 20:22:25.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
Jul 16 20:22:26.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $204DFD2A2C6A0DC1FA0EACB495218E0B661704FD~HaveHeart at 77.247.181.164. Retrying on a new circuit.
Jul 16 20:22:26.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $204DFD2A2C6A0DC1FA0EACB495218E0B661704FD~HaveHeart at 77.247.181.164. Retrying on a new circuit.
Jul 16 20:22:26.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $204DFD2A2C6A0DC1FA0EACB495218E0B661704FD~HaveHeart at 77.247.181.164. Retrying on a new circuit.
Jul 16 20:22:27.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $204DFD2A2C6A0DC1FA0EACB495218E0B661704FD~HaveHeart at 77.247.181.164. Retrying on a new circuit.
Jul 16 20:22:27.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $204DFD2A2C6A0DC1FA0EACB495218E0B661704FD~HaveHeart at 77.247.181.164. Retrying on a new circuit.
Jul 16 20:22:28.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up._

Wasabi Version

1.1.11.1

[yahiheb]

Have you tried to close the CoinJoin tab and reopen it when that happened?

[ghost]

Have you tried to close the CoinJoin tab and reopen it when that happened?

No, but I'm pretty sure that it wouldn't help, because when it happens I'm not participating in new rounds.

Once it happen, I wasn't at the computer and when I checked, status was "signed" and my last successful coinjoin was over 3 hours ago.

[MaxHillebrand]

Interesting, I can not reproduce.

[RiccardoMasutti]

Can't reproduce

[nopara73]

I've noticed similar behavior 2-3 times in the past year, but I always assumed it's just my eyes tricking me as I don't have a reasonable theory for this behavior. Thanks @Pahadron for posting it at least there's a clue now on how to reproduce it.

[ghost]

I have changed MainNetBackendUriV3 tohttps://wasabiwallet.ioinstead of onion address and for over 24 hours it hasn't happened...yet.. I will see, but it looks like Tor/Onion issue.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, July 18, 2020 1:36 PM, nopara73 [e-mail] wrote:

I've noticed similar behavior 2-3 times in the past year, but I always assumed it's just my eyes tricking me as I don't have a reasonable theory for this behavior. Thanks @Pahadron for posting it at least there's a clue now on how to reproduce it.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[nopara73]

I could not reproduce. I suppose it's more reasonable to replace the whole thing with WabiSabi than spending days of trying to figure out what's going on here.

[ghost]

I can confirm the freezing problem. I am running the latest git version and watching the logs. Normally there are at least several "Confirmed connection" log lines per minute. But last couple of days I noticed several times that the logs stopped scrolling. There is no new log line, the registration countdown in GUI keeps going but then it doesn't move onto the next phase so no mixing happens. It never resumes working, the only solution is to restart and re-enqueue. I am using tor. It's as if the program lost connection but didn't notice. Is there no keep-alive/heartbeat check?

I have been mixing for months but never had this problem, this started only a few days ago. It now got to the point that I have to check the logs every hour and when I see that the last log line is older than 1 minute I immediately restart. This is not really optimal for a healthy sleeping.

If it keeps happening I will try the non-tor endpoint too.

I could not reproduce. I suppose it's more reasonable to replace the whole thing with WabiSabi than spending days of trying to figure out what's going on here.

I am afraid I don't understand this suggestion at all. What is "the whole thing" and what is "WabiSabi" and how should we replace one with another?

[nopara73]

New CoinJoin tech we're working on: https://github.com/zkSNACKs/WabiSabi/

[ghost]

So I changed MainNetBackendUriV3 to clearnet and the freezing stopped. There is definitely something going on with the .onion endpoint connectivity, I can connect to it only from 1 of 3 servers I tried:

root@server1:/# telnet wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion 80
Trying 10.216.93.10...
Connected to wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion.
Escape character is '^]'.
GET /swagger HTTP/1.0

Connection closed by foreign host.

root@server2 / # telnet wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion 80
Trying 10.199.109.218...
Connected to wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion.
Escape character is '^]'.
GET /swagger HTTP/1.0

Connection closed by foreign host.

root@server3:~# telnet wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion 80
Trying 10.247.76.203...
Connected to wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion.
Escape character is '^]'.
GET /swagger HTTP/1.0

HTTP/1.1 301 Moved Permanently
Connection: close
Date: Wed, 22 Jul 2020 12:52:17 GMT
Server: Kestrel
Content-Length: 0
Location: swagger/index.html

Connection closed by foreign host.

New CoinJoin tech we're working on: https://github.com/zkSNACKs/WabiSabi/

Looks very cool! I wish you decide to make a CoinJoin-only client, without the GUI, wallet and anything else that's not required for mixing so that we can run it on servers just like Whirlpool's CLI.

[ghost]

So with clearnet backend Wasabi doesn't freeze but it sometimes gives these errors:

2020-07-24 ... ERROR WasabiSynchronizer (337) System.Net.Http.HttpRequestException: Gateway Timeout
<html>
<head><meta name="robots" content="noindex, nofollow" /><meta name="google-site-verification" content="..." /><title>504 Gateway Time-out</title></head>
<body bgcolor="white">
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>nginx</center>
</body>
</html>

at System.Net.Http.HttpResponseMessageExtensions.ThrowRequestExceptionFromContentAsync(HttpResponseMessage me) in WalletWasabi\Extensions\HttpResponseMessageExtensions.cs:line 107
at WalletWasabi.WebClients.Wasabi.WasabiClient.GetSynchronizeAsync(uint256 bestKnownBlockHash, Int32 count, Nullable 1 estimateMode, CancellationToken cancel) in WalletWasabi\WebClients\Wasabi\WasabiClient.cs:line 59
at System.Threading.Tasks.TaskExtensions.WithAwaitCancellationAsync[T](Task 1 me, CancellationToken cancel, Int32 waitForGracefulTerminationMilliseconds) in WalletWasabi\Extensions\TaskExtensions.cs:line 33
at WalletWasabi.Services.WasabiSynchronizer.<>c__DisplayClass60_0.<<Start>b__0>d.MoveNext() in WalletWasabi\Services\WasabiSynchronizer.cs:line 184

and

0-07-23 ... ERROR PeriodicRunner (73) System.Net.Http.HttpRequestException: Bad Gateway
<html>
<head><meta name="robots" content="noindex, nofollow" /><meta name="google-site-verification" content="..." /><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>

at System.Net.Http.HttpResponseMessageExtensions.ThrowRequestExceptionFromContentAsync(HttpResponseMessage me) in WalletWasabi\Extensions\HttpResponseMessageExtensions.cs:line 107
at WalletWasabi.WebClients.Wasabi.WasabiClient.GetVersionsAsync(CancellationToken cancel) in WalletWasabi\WebClients\Wasabi\WasabiClient.cs:line 247
at WalletWasabi.WebClients.Wasabi.WasabiClient.CheckUpdatesAsync(CancellationToken cancel) in WalletWasabi\WebClients\Wasabi\WasabiClient.cs:line 258
at WalletWasabi.Services.UpdateChecker.ActionAsync(CancellationToken cancel) in WalletWasabi\Services\UpdateChecker.cs:line 58
at WalletWasabi.Bases.PeriodicRunner.ExecuteAsync(CancellationToken stoppingToken) in WalletWasabi\Bases\PeriodicRunner.cs:line 53

So neither .onion nor clearnet backend endpoints are always reliably available.

[molnard]

@ghost thx for the report. Tor was updated by the new release from v4.2.5 to v4.3.5. Can you try that?

https://github.com/zkSNACKs/WalletWasabi/releases/tag/v1.1.12

[MaxHillebrand]

As the OP account is deleted, and I would guess the issue is resolved in v1.1.12, I'll close the issue now.

If anyone encounters the issue again, please re-open.