13:13:42:WU01:FS01:0x18:Folding@home Core Shutdown: FINISHED_UNIT
13:13:43:WU01:FS01:FahCore returned: FINISHED_UNIT (100 = 0x64)
13:13:43:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:10478 run:1 clone:57 gen:33 core:0x18 unit:0x00000038538b3dba548f6ea1a8da5122
13:13:43:WU01:FS01:Uploading 8.70MiB to 140.163.4.234
13:13:43:WU01:FS01:Connecting to 140.163.4.234:8080
13:16:04:WU01:FS01:Upload 7.18%
13:16:05:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
13:16:05:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:10478 run:1 clone:57 gen:33 core:0x18 unit:0x00000038538b3dba548f6ea1a8da5122
13:16:05:WU01:FS01:Uploading 8.70MiB to 140.163.4.234
13:16:05:WU01:FS01:Connecting to 140.163.4.234:8080
13:18:27:WU01:FS01:Upload 7.18%
13:18:27:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
13:18:27:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:10478 run:1 clone:57 gen:33 core:0x18 unit:0x00000038538b3dba548f6ea1a8da5122
13:18:27:WU01:FS01:Uploading 8.70MiB to 140.163.4.234
13:18:27:WU01:FS01:Connecting to 140.163.4.234:8080
13:20:56:WU01:FS01:Upload 7.18%
13:20:56:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
13:20:56:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:10478 run:1 clone:57 gen:33 core:0x18 unit:0x00000038538b3dba548f6ea1a8da5122
13:20:56:WU01:FS01:Uploading 8.70MiB to 140.163.4.234
13:20:56:WU01:FS01:Connecting to 140.163.4.234:8080
13:23:18:WU01:FS01:Upload 7.18%
13:23:18:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
13:23:34:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:10478 run:1 clone:57 gen:33 core:0x18 unit:0x00000038538b3dba548f6ea1a8da5122
13:23:34:WU01:FS01:Uploading 8.70MiB to 140.163.4.234
13:23:34:WU01:FS01:Connecting to 140.163.4.234:8080
13:25:55:WU01:FS01:Upload 7.18%
13:25:56:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
13:27:48:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:10478 run:1 clone:57 gen:33 core:0x18 unit:0x00000038538b3dba548f6ea1a8da5122
13:27:48:WU01:FS01:Uploading 8.70MiB to 140.163.4.234
13:27:48:WU01:FS01:Connecting to 140.163.4.234:8080
13:30:16:WU01:FS01:Upload 7.18%
13:30:16:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected
The server that your client is trying to return the WU to is up and receiving WU's from others. The message in your log "Received short response, expected 512 bytes, got 0" usually indicates a problem in the connection between your system and the server. Usually this is caused by anti-malware software, firewall settings or filtering of messages by ISP's.
Has any antivirus or other malware protection software been recently updated on your system? Any updates that might have changed firewall settings? Or has your ISP changed any firewall setups or filtering on your router.
Local to your own system, the FAHClient does need to be allowed to make incoming and outgoing connections by either firewall or anti-malware software. A symptom that can point to this is if you can connect to the server address in a browser, but the client fails to connect. There can be other causes at the ISP level or on your router.
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
dschief wrote:Going on to 7 hours now & still no response from that server!. Really!!, Someone upstream must have a clue as to a fix
You'll have to be the one to figure out if it's a setting on your router or a setting in you anti-malware software (or even a proxy setting, if you have one) or maybe even some kind of a local corruption of that result. I can safely say that the server is not the problem.