Page 1 of 1

Client V7.6.21 Won't send finished work unit

Posted: Thu Nov 10, 2022 6:16 pm
by MusicParoyds
As I stated in the subject, the client tries and fails to send the work unit. I reinstalled the client, and turned off my anti-virus to no avail.
Thanks for your help.
Below is a the log:

Code: Select all

18:06:19:ERROR:WU00:FS02:Exception: 10002: Received short response, expected 512 bytes, got 0
18:06:19:WU00:FS02:Sending unit results: id:00 state:SEND error:NO_ERROR project:18447 run:2 clone:367 gen:79 core:0x22 unit:0x0000016f0000004f0000480f00000002
18:06:19:WU00:FS02:Uploading 21.05MiB to 129.32.209.202
18:06:19:WU00:FS02:Connecting to 129.32.209.202:8080
18:06:50:WARNING:WU00:FS02:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
18:06:50:WU00:FS02:Trying to send results to collection server
18:06:50:WU00:FS02:Uploading 21.05MiB to 129.32.209.201
18:06:50:WU00:FS02:Connecting to 129.32.209.201:8080
18:07:20:ERROR:WU00:FS02:Exception: 10002: Received short response, expected 512 bytes, got 0
18:07:57:WU00:FS02:Sending unit results: id:00 state:SEND error:NO_ERROR project:18447 run:2 clone:367 gen:79 core:0x22 unit:0x0000016f0000004f0000480f00000002
18:07:57:WU00:FS02:Uploading 21.05MiB to 129.32.209.202
18:07:57:WU00:FS02:Connecting to 129.32.209.202:8080
18:08:27:WARNING:WU00:FS02:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
18:08:27:WU00:FS02:Trying to send results to collection server
18:08:27:WU00:FS02:Uploading 21.05MiB to 129.32.209.201
18:08:27:WU00:FS02:Connecting to 129.32.209.201:8080
18:08:57:ERROR:WU00:FS02:Exception: 10002: Received short response, expected 512 bytes, got 0
18:09:51:WU03:FS00:0xa8:Completed 800000 out of 10000000 steps (8%)
18:10:34:WU00:FS02:Sending unit results: id:00 state:SEND error:NO_ERROR project:18447 run:2 clone:367 gen:79 core:0x22 unit:0x0000016f0000004f0000480f00000002
18:10:34:WU00:FS02:Uploading 21.05MiB to 129.32.209.202
18:10:34:WU00:FS02:Connecting to 129.32.209.202:8080
18:11:04:WARNING:WU00:FS02:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
18:11:04:WU00:FS02:Trying to send results to collection server
18:11:04:WU00:FS02:Uploading 21.05MiB to 129.32.209.201
18:11:04:WU00:FS02:Connecting to 129.32.209.201:8080
18:11:34:ERROR:WU00:FS02:Exception: 10002: Received short response, expected 512 bytes, got 0
18:14:48:WU00:FS02:Sending unit results: id:00 state:SEND error:NO_ERROR project:18447 run:2 clone:367 gen:79 core:0x22 unit:0x0000016f0000004f0000480f00000002
18:14:48:WU00:FS02:Uploading 21.05MiB to 129.32.209.202
18:14:48:WU00:FS02:Connecting to 129.32.209.202:8080
18:15:18:WARNING:WU00:FS02:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
18:15:18:WU00:FS02:Trying to send results to collection server
18:15:18:WU00:FS02:Uploading 21.05MiB to 129.32.209.201
18:15:18:WU00:FS02:Connecting to 129.32.209.201:8080

Re: Client V7.6.21 Won't send finished work unit

Posted: Thu Nov 10, 2022 10:12 pm
by Joe_H
If this is you, then the WU already has uploaded:
Hi Music (team 0), Your WU (P18447 R2 C367 G79) was added to the stats database on Invalid Date for 165454 points of credit.
This can happen when the acknowledgement packet after a successful upload is either blocked or dropped between the server and your system. This can be from router settings, either yours or your ISP's. Sometimes resetting your connection will clear this up from happening.

The other possibility is settings on your system for anti-malware or firewall protection. These can also be the cause of the exception messages, "10002: Received short response, expected 512 bytes, got 0". These indicate an expected packet from the server is not being received with content in response to your system connecting to the server. Instead the content has been blocked.

Re: Client V7.6.21 Won't send finished work unit

Posted: Fri Nov 11, 2022 1:06 pm
by MusicParoyds
Thanks!
While I was sleeping it confirmed.
If the problem reappears I'd have to check my provider's settings.