Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WSA code 10053, 10054 #328

Open
Perfy opened this issue Jun 18, 2024 · 6 comments
Open

WSA code 10053, 10054 #328

Perfy opened this issue Jun 18, 2024 · 6 comments

Comments

@Perfy
Copy link

Perfy commented Jun 18, 2024

Strange effects on one of the harvesters in recompute proxy.
What could be the reason?
(Windows 10, LTSC, Firewall disabled)

Output:

Node 192.168.2.111 failed with: recv() failed with: WSA code 10053
[1718710515867] Request from 127.0.0.1 forwarded to node 192.168.2.111
[1718710515869] Request from 127.0.0.1 forwarded to node 192.168.2.102
Node 192.168.2.111 failed with: recv() failed with: WSA code 10053
Node 192.168.2.102 failed with: send() failed with: WSA code 10054
[1718710747770] Request from 127.0.0.1 forwarded to node 192.168.2.111
Node 192.168.2.111 failed with: send() failed with: WSA code 10053
[1718710757496] Request from 127.0.0.1 forwarded to node 192.168.2.102
Node 192.168.2.102 failed with: send() failed with: WSA code 10053
[1718710766095] Request from 127.0.0.1 forwarded to node 192.168.2.111
[1718710796058] Request from 127.0.0.1 forwarded to node 192.168.2.111
[1718710796059] Request from 127.0.0.1 forwarded to node 192.168.2.102
[1718710796060] Request from 127.0.0.1 forwarded to node 192.168.2.81
Node 192.168.2.81 failed with: send() failed with: WSA code 10053
Node 192.168.2.102 failed with: send() failed with: WSA code 10054
[1718710840837] Request from 127.0.0.1 forwarded to node 192.168.2.111
[1718710840838] Request from 127.0.0.1 forwarded to node 192.168.2.102
[1718710841226] Request from 127.0.0.1 forwarded to node 192.168.2.111
[1718710858496] Request from 127.0.0.1 forwarded to node 192.168.2.111
[1718710858498] Request from 127.0.0.1 forwarded to node 192.168.2.102
[1718710858500] Request from 127.0.0.1 forwarded to node 192.168.2.81
Node 192.168.2.81 failed with: recv() failed with: EOF
[1718710876149] Request from 127.0.0.1 forwarded to node 192.168.2.111
[1718710945871] Request from 127.0.0.1 forwarded to node 192.168.2.111
Node 192.168.2.111 failed with: recv() failed with: WSA code 10053
[1718710953741] Request from 127.0.0.1 forwarded to node 192.168.2.102
[1718710953744] Request from 127.0.0.1 forwarded to node 192.168.2.81
[1718710953746] Request from 127.0.0.1 forwarded to node 192.168.2.102
[1718710953748] Request from 127.0.0.1 forwarded to node 192.168.2.81
[1718710953750] Request from 127.0.0.1 forwarded to node 192.168.2.102
Node 192.168.2.102 failed with: send() failed with: WSA code 10054
Node 192.168.2.81 failed with: recv() failed with: EOF
[1718711121384] Request from 127.0.0.1 forwarded to node 192.168.2.111
Node 192.168.2.111 failed with: recv() failed with: WSA code 10053
[1718711178957] Request from 127.0.0.1 forwarded to node 192.168.2.111
[1718711178960] Request from 127.0.0.1 forwarded to node 192.168.2.102
Node 192.168.2.102 failed with: send() failed with: WSA code 10054
[1718711190566] Request from 127.0.0.1 forwarded to node 192.168.2.111
[1718711206265] Request from 127.0.0.1 forwarded to node 192.168.2.111
[1718711336921] Request from 127.0.0.1 forwarded to node 192.168.2.111
Node 192.168.2.111 failed with: recv() failed with: EOF
@Perfy
Copy link
Author

Perfy commented Jun 19, 2024

The problem appeared after update from 2.1.4.giga26 to 2.3.0.giga36, before that everything worked fine

@madMAx43v3r
Copy link
Owner

Did you update the remote compute server as well? It's required.

@Perfy
Copy link
Author

Perfy commented Jun 20, 2024

Yes.

@madMAx43v3r
Copy link
Owner

On all machines? Can you try without the proxy?

@Perfy
Copy link
Author

Perfy commented Jun 20, 2024

On all.
Without the proxy works great.

@madMAx43v3r
Copy link
Owner

I never tested the old proxy with the new code... maybe it's obsolete now.

You can try the new HTTP proxy, just use port 11988:

export CHIAPOS_RECOMPUTE_HOST=proxy.ip:11988

And start HTTP proxy via:

./chia_recompute_proxy_http

And specify proxy on compute server side:

./chia_recompute_server -u proxy.ip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants