Can't upload to 140.163.4.231:80

[DOMiNiON79]

still same here: meanwhile i have 2 WUs, that i can´t upload to
140.163.4.231 (since 2020-04-03!) and
140.163.4.241 (since 2020-04-07T05:02:50Z)

[Acorn444]

I have the exactly the same problem.
I have been unable to upload for almost a week. I just keep getting the same recurring log due to being unable to upload. In this time, I've restarted my system multiple times when I switch my system off at the end of the day. I've completed multiple other WU on the same GPU and these have all been uploaded without an issue.

See Code below for log related to the WU in question.

Code: Select all

*********************** Log Started 2020-04-07T07:53:39Z ***********************
07:53:40:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:4298 gen:0 core:0x22 unit:0x000000088ca304e75e6a7fdbc0e71982
07:53:40:WU01:FS01:Uploading 21.92MiB to 140.163.4.231
07:53:40:WU01:FS01:Connecting to 140.163.4.231:8080
07:54:01:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
07:54:01:WU01:FS01:Connecting to 140.163.4.231:80
07:54:23:WARNING:WU01:FS01:Exception: Failed to send results to work server: Failed to connect to 140.163.4.231: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.
07:54:23:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:4298 gen:0 core:0x22 unit:0x000000088ca304e75e6a7fdbc0e71982
07:54:23:WU01:FS01:Uploading 21.92MiB to 140.163.4.231
07:54:23:WU01:FS01:Connecting to 140.163.4.231:8080
07:54:44:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
07:54:44:WU01:FS01:Connecting to 140.163.4.231:80
07:54:45:WU01:FS01:Upload 0.29%
07:56:00:WU01:FS01:Upload 0.57%
07:56:00:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
07:56:01:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:4298 gen:0 core:0x22 unit:0x000000088ca304e75e6a7fdbc0e71982
07:56:01:WU01:FS01:Uploading 21.92MiB to 140.163.4.231
07:56:01:WU01:FS01:Connecting to 140.163.4.231:8080
07:56:22:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
07:56:22:WU01:FS01:Connecting to 140.163.4.231:80
07:56:43:WARNING:WU01:FS01:Exception: Failed to send results to work server: Failed to connect to 140.163.4.231: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.
07:57:38:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:4298 gen:0 core:0x22 unit:0x000000088ca304e75e6a7fdbc0e71982
07:57:38:WU01:FS01:Uploading 21.92MiB to 140.163.4.231
07:57:38:WU01:FS01:Connecting to 140.163.4.231:8080
07:57:59:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
07:57:59:WU01:FS01:Connecting to 140.163.4.231:80
07:58:20:WARNING:WU01:FS01:Exception: Failed to send results to work server: Failed to connect to 140.163.4.231: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.
08:00:15:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:4298 gen:0 core:0x22 unit:0x000000088ca304e75e6a7fdbc0e71982
08:00:15:WU01:FS01:Uploading 21.92MiB to 140.163.4.231
08:00:15:WU01:FS01:Connecting to 140.163.4.231:8080
08:00:36:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
08:00:36:WU01:FS01:Connecting to 140.163.4.231:80
08:00:44:WU01:FS01:Upload 0.29%
08:01:52:WU01:FS01:Upload 0.57%
08:01:52:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
08:04:29:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:4298 gen:0 core:0x22 unit:0x000000088ca304e75e6a7fdbc0e71982
08:04:29:WU01:FS01:Uploading 21.92MiB to 140.163.4.231
08:04:29:WU01:FS01:Connecting to 140.163.4.231:8080
08:04:36:WU01:FS01:Upload 0.29%
08:05:49:WU01:FS01:Upload 0.57%
08:05:49:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
08:11:21:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:4298 gen:0 core:0x22 unit:0x000000088ca304e75e6a7fdbc0e71982
08:11:21:WU01:FS01:Uploading 21.92MiB to 140.163.4.231
08:11:21:WU01:FS01:Connecting to 140.163.4.231:8080
08:11:42:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
08:11:42:WU01:FS01:Connecting to 140.163.4.231:80
08:12:03:WARNING:WU01:FS01:Exception: Failed to send results to work server: Failed to connect to 140.163.4.231: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.
08:22:26:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:4298 gen:0 core:0x22 unit:0x000000088ca304e75e6a7fdbc0e71982
08:22:26:WU01:FS01:Uploading 21.92MiB to 140.163.4.231
08:22:26:WU01:FS01:Connecting to 140.163.4.231:8080
08:24:06:WU01:FS01:Upload 0.57%
08:24:06:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
08:40:23:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:4298 gen:0 core:0x22 unit:0x000000088ca304e75e6a7fdbc0e71982
08:40:23:WU01:FS01:Uploading 21.92MiB to 140.163.4.231
08:40:23:WU01:FS01:Connecting to 140.163.4.231:8080
08:40:44:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
08:40:44:WU01:FS01:Connecting to 140.163.4.231:80
08:41:05:WARNING:WU01:FS01:Exception: Failed to send results to work server: Failed to connect to 140.163.4.231: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.
09:09:25:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:4298 gen:0 core:0x22 unit:0x000000088ca304e75e6a7fdbc0e71982
09:09:25:WU01:FS01:Uploading 21.92MiB to 140.163.4.231
09:09:25:WU01:FS01:Connecting to 140.163.4.231:8080
09:09:46:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
09:09:46:WU01:FS01:Connecting to 140.163.4.231:80
09:10:08:WARNING:WU01:FS01:Exception: Failed to send results to work server: Failed to connect to 140.163.4.231: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.
09:56:24:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:4298 gen:0 core:0x22 unit:0x000000088ca304e75e6a7fdbc0e71982
09:56:24:WU01:FS01:Uploading 21.92MiB to 140.163.4.231
09:56:24:WU01:FS01:Connecting to 140.163.4.231:8080
09:56:45:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
09:56:45:WU01:FS01:Connecting to 140.163.4.231:80
09:57:06:WARNING:WU01:FS01:Exception: Failed to send results to work server: Failed to connect to 140.163.4.231: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.
11:12:25:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:4298 gen:0 core:0x22 unit:0x000000088ca304e75e6a7fdbc0e71982
11:12:25:WU01:FS01:Uploading 21.92MiB to 140.163.4.231
11:12:25:WU01:FS01:Connecting to 140.163.4.231:8080
11:12:46:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
11:12:46:WU01:FS01:Connecting to 140.163.4.231:80
11:13:07:WARNING:WU01:FS01:Exception: Failed to send results to work server: Failed to connect to 140.163.4.231: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.
13:15:25:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:4298 gen:0 core:0x22 unit:0x000000088ca304e75e6a7fdbc0e71982
13:15:25:WU01:FS01:Uploading 21.92MiB to 140.163.4.231
13:15:25:WU01:FS01:Connecting to 140.163.4.231:8080
13:15:46:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
13:15:46:WU01:FS01:Connecting to 140.163.4.231:80
13:16:07:WARNING:WU01:FS01:Exception: Failed to send results to work server: Failed to connect to 140.163.4.231: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.
******************************* Date: 2020-04-07 *******************************

Mod Edit: Added Code Tags - PantherX

[Lothromas]

I currently Have 5 WU that are not sending back to various servers. Are several servers out of space that we are stuck holding these files. Uploads just wont return even after 6 days of trying. One of mine although being finished will most likely not return in time as the clock expires in .2 days and its is 4 hours till the next attempted upload. Several more will expire tomorrow. Took all of 45 minutes to do the fold out of the six days i had to get it back.

[semaphore]

140.163.4.231 is now working since about 1hour

Right click your F@H icon, next to the clock (on windows desktop), and choose "Quit"
Then start up your client again by searching for "Folding@home", and press enter.

The client should now start up again, but with lower timeouts for the now working Work Server (140.163.4.231:80)

[Acorn444]

I can confirm that 140.163.4.231 is now working, literally 1 hour after I posted my above message.

Glad it's finally got through and not just sitting there collecting dust and all our data potentially being overlooked.

[bruce]

Ok, without any access to historic information except the reports above, I'm willing to GUESS that the server was in the process of becoming outfitted to be a CS (like maybe installing a revised version for the server code or something like that. Even though the server had previously been operating properly, your WUs believe it was an operational Collection Server, which it had been but the FAH code wasn't actually running when your client tried to use it.

Not necessarily factual, but at least plausible.

[terrorhai]

Yep, was able to upload my files yesterday.
But the server seems to be very inconsistent, now it's not reachable again.
Isn't there anyone monitoring if all servers are working properly?
I know the actual workload is very high with all the additional folders, but we can't help if the infrastructure is fragile

[konyak_ad]

I can confirm that 140.163.4.231 is now working, literally 1 hour after I posted my above message.

Glad it's finally got through and not just sitting there collecting dust and all our data potentially being overlooked.

It really worked for a while, my client uploaded the WU after 4 or 5 days but I have completed a new WU assigned to this server and it is stuck again since yesterday. (Failed to send results to work server, unit:0x0000002e8ca304e75e6bbb3d63cf4dc1)

[iceman1992]

Yeah me too, as I reported here viewtopic.php?f=18&t=34116, still hasn't successfully uploaded after so many hours

[konyak_ad]

Code: Select all

07:24:33:WU01:FS01:Uploading 14.66MiB to 140.163.4.231
07:24:33:WU01:FS01:Connecting to 140.163.4.231:8080
07:24:33:WU00:FS01:Starting
(...)
07:25:31:WU01:FS01:Upload complete
07:25:31:WU01:FS01:Server responded WORK_QUIT (404)
07:25:31:WARNING:WU01:FS01:Server did not like results, dumping

Great.

[iceman1992]

Code: Select all

07:24:33:WU01:FS01:Uploading 14.66MiB to 140.163.4.231
07:24:33:WU01:FS01:Connecting to 140.163.4.231:8080
07:24:33:WU00:FS01:Starting
(...)
07:25:31:WU01:FS01:Upload complete
07:25:31:WU01:FS01:Server responded WORK_QUIT (404)
07:25:31:WARNING:WU01:FS01:Server did not like results, dumping

Great.

Yep! Same thing happened to me > viewtopic.php?f=18&t=34195