Stuck trying to send job for 3 days

[unwiredmedic]

Relatively new to folding here (since April 2, 2020). I upped my logging level and this is what I came up with. I will have to try again tomorrow, but I only have a little over 2 more days before this expires. TIA for any help.

06:35:34:WARNING:WU00:FS00:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
06:35:34:WU00:FS00:Trying to send results to collection server
06:35:34:WU00:FS00:Uploading 6.49MiB to 155.247.166.219
06:35:34:WU00:FS00:Connecting to 155.247.166.219:8080
06:36:47:ERROR:WU00:FS00:Exception: 10002: Received short response, expected 512 bytes, got 0
06:36:47:WU00:FS00:Sending unit results: id:00 state:SEND error:NO_ERROR project:14365 run:312 clone:1 gen:41 core:0xa7 unit:0x0000002b9bf7a4d55e81239c84eb8cc6
06:36:47:WU00:FS00:Uploading 6.49MiB to 155.247.164.213
06:36:47:WU00:FS00:Connecting to 155.247.164.213:8080
06:37:08:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
06:37:08:WU00:FS00:Connecting to 155.247.164.213:80
06:37:29:WARNING:WU00:FS00:Exception: Failed to send results to work server: Failed to connect to 155.247.164.213:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
06:37:29:WU00:FS00:Trying to send results to collection server
06:37:30:WU00:FS00:Uploading 6.49MiB to 155.247.166.219
06:37:30:WU00:FS00:Connecting to 155.247.166.219:8080
06:38:21:ERROR:WU00:FS00:Exception: 10002: Received short response, expected 512 bytes, got 0
06:38:21:WU00:FS00:Sending unit results: id:00 state:SEND error:NO_ERROR project:14365 run:312 clone:1 gen:41 core:0xa7 unit:0x0000002b9bf7a4d55e81239c84eb8cc6
06:38:21:WU00:FS00:Uploading 6.49MiB to 155.247.164.213
06:38:21:WU00:FS00:Connecting to 155.247.164.213:8080
06:38:42:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
06:38:42:WU00:FS00:Connecting to 155.247.164.213:80
06:39:04:WARNING:WU00:FS00:Exception: Failed to send results to work server: Failed to connect to 155.247.164.213:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
06:39:04:WU00:FS00:Trying to send results to collection server
06:39:04:WU00:FS00:Uploading 6.49MiB to 155.247.166.219
06:39:04:WU00:FS00:Connecting to 155.247.166.219:8080
06:41:41:ERROR:WU00:FS00:Exception: 10002: Received short response, expected 512 bytes, got 0
06:41:41:WU00:FS00:Sending unit results: id:00 state:SEND error:NO_ERROR project:14365 run:312 clone:1 gen:41 core:0xa7 unit:0x0000002b9bf7a4d55e81239c84eb8cc6
06:41:41:WU00:FS00:Uploading 6.49MiB to 155.247.164.213
06:41:41:WU00:FS00:Connecting to 155.247.164.213:8080

Things I have tried:
- app restarts
- pause folding
- restart my workstation
- I shut down for the night for several hours at a time and resume the next day (generates A LOT of heat! )
- my Spectrum cable modem and my WiFi router are reset every day in the wee hours
- verified my connection to the interwebz and I have bandwidth to spare

[PantherX]

Welcome to the F@H Forum unwiredmedic,

Please note that due to bandwidth issues, the Sever is overloaded. May I suggest that you leave the client running at night but pause them? In theory, it should try to upload the completed WUs but not generate any heat.

Furthermore, please ensure that the verbosity level is set at 3 since any high will hinder us in troubleshooting.

[unwiredmedic]

I'll give it a shot. I was hoping the server was just extraordinarily busy. Thanks.

[astronomyrat]

I have my the same problem, and the PC is running 24/24h, I have now 2 WU waiting to be send since days is there a way to avoid WU from 155.247.164.213 as it seems it upload server isn't able to accept all the processed WU.

[PantherX]

Welcome to the F@H Forum astronomyrat,

Unfortunately, there's no way to block the Work Server from the Client side. There's a massive load on the Work Server bandwidth/resource limitations and work is being done to elevate it so in the meantime, please leave the client running and it will automatically handle the WUs

[tomc001]

I have 4 to send from 155.247.164.213. Just a moment ago it was 5 to send but one finally made it back home. The oldest one in the send queue is two days old now. My computer is always on.

Does anyone know if the send requests use an Ethernet like exponential backoff time algorithm between attempts in an effort to reduce collisions? Obviously the time constants would need to be much longer than the microseconds used with Ethernet.

[Joe_H]

Yes, the client usually backs off the sending of WUs. In the log you would be able to see an increasing time between return attempts for each WU.

[unwiredmedic]

OKay, so it didn't send for the fourth day. I'll keep trying and hope it goes through before it expires.

[tomc001]

There is a real problem with at least one server receiving results. Here are the 5 currently stuck for me. The oldest is 5 days old. What's the point of assigning work units if the results are never received?

[Jan]

The staff is aware of this situation. Projects are being redistributed to additional servers. Should see a noticable difference within the next 3-4 days.