WSA code 10053, 10054
Perfy opened this issue · 6 comments
Perfy commented
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 commented
The problem appeared after update from 2.1.4.giga26 to 2.3.0.giga36, before that everything worked fine
madMAx43v3r commented
Did you update the remote compute server as well? It's required.
Perfy commented
Yes.
madMAx43v3r commented
On all machines? Can you try without the proxy?
Perfy commented
On all.
Without the proxy works great.
madMAx43v3r commented
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