Can't upload to 140.163.4.231:80

Moderators: Site Moderators, FAHC Science Team

crossj
Posts: 3
Joined: Sun Apr 05, 2020 4:55 am

Can't upload to 140.163.4.231:80

Post by crossj »

Hi Team,

I currently have a completed work on my GPU that's been stuck for 12 hours+
Finished around 12~1am NZDT last night, but I'm still not being about to upload my work and start on a new WU.
Would you be able to help me out please?

Thanks

Code: Select all

22:27:17:WARNING:WU00: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.
22:38:01:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
22:38:22:WARNING:WU00: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.
22:55:58:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
22:56:19:WARNING:WU00: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.
23:25:02:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
23:25:23:WARNING:WU00: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.
00:11:59:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
00:12:20:WARNING:WU00: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.
01:28:00:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
01:28:21:WARNING:WU00: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.
01:28:57:ERROR:Receive error: 10054: An existing connection was forcibly closed by the remote host.
03:32:01:WARNING:WU00:FS01:Exception: Failed to send results to work server: Transfer failed
PantherX
Site Moderator
Posts: 7020
Joined: Wed Dec 23, 2009 9:33 am
Hardware configuration: V7.6.21 -> Multi-purpose 24/7
Windows 10 64-bit
CPU:2/3/4/6 -> Intel i7-6700K
GPU:1 -> Nvidia GTX 1080 Ti
§
Retired:
2x Nvidia GTX 1070
Nvidia GTX 675M
Nvidia GTX 660 Ti
Nvidia GTX 650 SC
Nvidia GTX 260 896 MB SOC
Nvidia 9600GT 1 GB OC
Nvidia 9500M GS
Nvidia 8800GTS 320 MB

Intel Core i7-860
Intel Core i7-3840QM
Intel i3-3240
Intel Core 2 Duo E8200
Intel Core 2 Duo E6550
Intel Core 2 Duo T8300
Intel Pentium E5500
Intel Pentium E5400
Location: Land Of The Long White Cloud
Contact:

Re: Can't upload to 140.163.4.231:80

Post by PantherX »

Welcome to the F@H Forum crossj,

Please note that due to the significant demand of WUs, the F@H infrastructure is under load (viewtopic.php?f=18&t=33193). There can be few hours of delay in getting a new WU but going 12+ hours might be an issue. May I suggest that you restart your system? Reason is that there's a known bug where if the software is downloading/uploading and it stops (loss of internet connection, etc.), the software will not detect that and hence will be stuck. A quick reboot of your system should resolve that issue if that's the case.
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time

Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
semaphore
Posts: 15
Joined: Sun Apr 05, 2020 8:52 am
Location: Stockholm

Re: Can't upload to 140.163.4.231:80

Post by semaphore »

There are another thread reporting this same server (can not link, due to being a newbie on forum).

But the recommendation from PantherX is maybe not the best.
Just did a restart, and instead my computer reset all the work timers, and my Client is now hammering this server, trying to deliver my finished data.

It will fall back soon, but each re-start of the Client software makes the time-out timers shorter, which in these times of high load is bad for the central servers.

I mean: Even if the upload fails, as long it makes the upload before expiration date, the work should not go to waste. A late upload affects points, yes, but in these times I think that is OK. We are all in the same boat, and in the long run even "chance" should give you a much better server for other WU:s.
PantherX
Site Moderator
Posts: 7020
Joined: Wed Dec 23, 2009 9:33 am
Hardware configuration: V7.6.21 -> Multi-purpose 24/7
Windows 10 64-bit
CPU:2/3/4/6 -> Intel i7-6700K
GPU:1 -> Nvidia GTX 1080 Ti
§
Retired:
2x Nvidia GTX 1070
Nvidia GTX 675M
Nvidia GTX 660 Ti
Nvidia GTX 650 SC
Nvidia GTX 260 896 MB SOC
Nvidia 9600GT 1 GB OC
Nvidia 9500M GS
Nvidia 8800GTS 320 MB

Intel Core i7-860
Intel Core i7-3840QM
Intel i3-3240
Intel Core 2 Duo E8200
Intel Core 2 Duo E6550
Intel Core 2 Duo T8300
Intel Pentium E5500
Intel Pentium E5400
Location: Land Of The Long White Cloud
Contact:

Re: Can't upload to 140.163.4.231:80

Post by PantherX »

semaphore wrote:...But the recommendation from PantherX is maybe not the best.
Just did a restart, and instead my computer reset all the work timers, and my Client is now hammering this server, trying to deliver my finished data...
Apologies if my post wasn't clear. Since the issue was around network transfer, there are two common possibilities:
1) Server side -> In this case, the client will exponentially back-off to prevent overloading the servers.
2) Client side (known bug) -> If the WU transfer (upload/download) fails mid-way during transfer, the client will not detect it and simply wait indefinitely until it's manually restarted. The workaround for this is to restart the client/system.

It would be nice if crossj did upload a more recent log file so we can see what the current situation is.
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time

Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
crossj
Posts: 3
Joined: Sun Apr 05, 2020 4:55 am

Re: Can't upload to 140.163.4.231:80

Post by crossj »

PantherX wrote:
semaphore wrote:It would be nice if crossj did upload a more recent log file so we can see what the current situation is.
Hi PantherX,

Sorry for the late reply, just finish off work and dinner.
I've rebooted my PC, technically it was just a shutdown as I just booted my PC, but again still having issues with the upload.
I turned off my VPN and Malwarebytes assuming they might cause some connectivity issues, but my WU is still stuck and can't reach the server, and here's my latest log.

Code: Select all

*********************** Log Started 2020-04-06T06:50:56Z ***********************
06:50:56:WU00:FS01:Sending unit results: id:00 state:SEND error:NO_ERROR project:11749 run:0 clone:1992 gen:11 core:0x22 unit:0x0000001b8ca304e75e6a8006939381ba
06:50:56:WU00:FS01:Uploading 12.57MiB to 140.163.4.231
06:50:56:WU00:FS01:Connecting to 140.163.4.231:8080
06:51:18:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
06:51:18:WU00:FS01:Connecting to 140.163.4.231:80
06:51:21:WU00:FS01:Upload 0.50%
06:52:29:WU00:FS01:Upload 0.99%
06:52:29:WARNING:WU00:FS01:Exception: Failed to send results to work server: Transfer failed
06:52:29:WU00:FS01:Sending unit results: id:00 state:SEND error:NO_ERROR project:11749 run:0 clone:1992 gen:11 core:0x22 unit:0x0000001b8ca304e75e6a8006939381ba
06:52:29:WU00:FS01:Uploading 12.57MiB to 140.163.4.231
06:52:29:WU00:FS01:Connecting to 140.163.4.231:8080
06:52:50:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
06:52:50:WU00:FS01:Connecting to 140.163.4.231:80
06:53:11:WARNING:WU00: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.
06:53:29:WU00:FS01:Sending unit results: id:00 state:SEND error:NO_ERROR project:11749 run:0 clone:1992 gen:11 core:0x22 unit:0x0000001b8ca304e75e6a8006939381ba
06:53:29:WU00:FS01:Uploading 12.57MiB to 140.163.4.231
06:53:29:WU00:FS01:Connecting to 140.163.4.231:8080
06:53:50:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
06:53:50:WU00:FS01:Connecting to 140.163.4.231:80
06:54:11:WARNING:WU00: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.
06:55:07:WU00:FS01:Sending unit results: id:00 state:SEND error:NO_ERROR project:11749 run:0 clone:1992 gen:11 core:0x22 unit:0x0000001b8ca304e75e6a8006939381ba
06:55:07:WU00:FS01:Uploading 12.57MiB to 140.163.4.231
06:55:07:WU00:FS01:Connecting to 140.163.4.231:8080
06:55:28:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
06:55:28:WU00:FS01:Connecting to 140.163.4.231:80
06:55:49:WARNING:WU00: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.
06:57:44:WU00:FS01:Sending unit results: id:00 state:SEND error:NO_ERROR project:11749 run:0 clone:1992 gen:11 core:0x22 unit:0x0000001b8ca304e75e6a8006939381ba
06:57:44:WU00:FS01:Uploading 12.57MiB to 140.163.4.231
06:57:44:WU00:FS01:Connecting to 140.163.4.231:8080
06:58:05:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
06:58:05:WU00:FS01:Connecting to 140.163.4.231:80
06:58:14:WU00:FS01:Upload 0.50%
06:59:22:WU00:FS01:Upload 0.99%
06:59:22:WARNING:WU00:FS01:Exception: Failed to send results to work server: Transfer failed
07:01:58:WU00:FS01:Sending unit results: id:00 state:SEND error:NO_ERROR project:11749 run:0 clone:1992 gen:11 core:0x22 unit:0x0000001b8ca304e75e6a8006939381ba
07:01:58:WU00:FS01:Uploading 12.57MiB to 140.163.4.231
07:01:58:WU00:FS01:Connecting to 140.163.4.231:8080
07:03:14:WU00:FS01:Upload 0.99%
07:03:14:WARNING:WU00:FS01:Exception: Failed to send results to work server: Transfer failed
07:08:49:WU00:FS01:Sending unit results: id:00 state:SEND error:NO_ERROR project:11749 run:0 clone:1992 gen:11 core:0x22 unit:0x0000001b8ca304e75e6a8006939381ba
07:08:49:WU00:FS01:Uploading 12.57MiB to 140.163.4.231
07:08:49:WU00:FS01:Connecting to 140.163.4.231:8080
07:09:10:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
07:09:10:WU00:FS01:Connecting to 140.163.4.231:80
07:09:31:WARNING:WU00: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:19:55:WU00:FS01:Sending unit results: id:00 state:SEND error:NO_ERROR project:11749 run:0 clone:1992 gen:11 core:0x22 unit:0x0000001b8ca304e75e6a8006939381ba
07:19:55:WU00:FS01:Uploading 12.57MiB to 140.163.4.231
07:19:55:WU00:FS01:Connecting to 140.163.4.231:8080
07:20:16:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
07:20:16:WU00:FS01:Connecting to 140.163.4.231:80
07:20:37:WARNING:WU00: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:37:52:WU00:FS01:Sending unit results: id:00 state:SEND error:NO_ERROR project:11749 run:0 clone:1992 gen:11 core:0x22 unit:0x0000001b8ca304e75e6a8006939381ba
07:37:52:WU00:FS01:Uploading 12.57MiB to 140.163.4.231
07:37:52:WU00:FS01:Connecting to 140.163.4.231:8080
07:38:13:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
07:38:13:WU00:FS01:Connecting to 140.163.4.231:80
07:38:34:WARNING:WU00: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.
Hope this can clear things up.
So I think in total this work has been stuck like 2 days?

Thanks
PantherX
Site Moderator
Posts: 7020
Joined: Wed Dec 23, 2009 9:33 am
Hardware configuration: V7.6.21 -> Multi-purpose 24/7
Windows 10 64-bit
CPU:2/3/4/6 -> Intel i7-6700K
GPU:1 -> Nvidia GTX 1080 Ti
§
Retired:
2x Nvidia GTX 1070
Nvidia GTX 675M
Nvidia GTX 660 Ti
Nvidia GTX 650 SC
Nvidia GTX 260 896 MB SOC
Nvidia 9600GT 1 GB OC
Nvidia 9500M GS
Nvidia 8800GTS 320 MB

Intel Core i7-860
Intel Core i7-3840QM
Intel i3-3240
Intel Core 2 Duo E8200
Intel Core 2 Duo E6550
Intel Core 2 Duo T8300
Intel Pentium E5500
Intel Pentium E5400
Location: Land Of The Long White Cloud
Contact:

Re: Can't upload to 140.163.4.231:80

Post by PantherX »

Humm, I checked the Server Status (https://apps.foldingathome.org/serverstats) and I can't see anything wrong with it. However, you're not along in this (viewtopic.php?f=18&t=33905). I am sure that the F@H Team will look into this soon.

FYI, if you're using Windows 10, there's a difference between Shutdown and Reboot. If you're attempting to troubleshoot an issue, perform a reboot as that will reload the kernel. Doing a shutdown and then power up doesn't do that (https://www.howtogeek.com/349114/shutti ... g-it-does/). In this case, I don't think it will make a difference as the issue seems to be Server side.
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time

Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
terrorhai
Posts: 2
Joined: Mon Apr 06, 2020 7:56 am

Re: Can't upload to 140.163.4.231:80

Post by terrorhai »

I got the same problem with this server.
There is no secondary collection server, so it always tries to send it to this one.
If you look into the serverstats, you will see, that there is no collection server connected.
How can we fix that?
PantherX
Site Moderator
Posts: 7020
Joined: Wed Dec 23, 2009 9:33 am
Hardware configuration: V7.6.21 -> Multi-purpose 24/7
Windows 10 64-bit
CPU:2/3/4/6 -> Intel i7-6700K
GPU:1 -> Nvidia GTX 1080 Ti
§
Retired:
2x Nvidia GTX 1070
Nvidia GTX 675M
Nvidia GTX 660 Ti
Nvidia GTX 650 SC
Nvidia GTX 260 896 MB SOC
Nvidia 9600GT 1 GB OC
Nvidia 9500M GS
Nvidia 8800GTS 320 MB

Intel Core i7-860
Intel Core i7-3840QM
Intel i3-3240
Intel Core 2 Duo E8200
Intel Core 2 Duo E6550
Intel Core 2 Duo T8300
Intel Pentium E5500
Intel Pentium E5400
Location: Land Of The Long White Cloud
Contact:

Re: Can't upload to 140.163.4.231:80

Post by PantherX »

terrorhai wrote:...There is no secondary collection server, so it always tries to send it to this one.
If you look into the serverstats, you will see, that there is no collection server connected.
How can we fix that?
Welcome to the F@H Forum terrorhai,

The configuration of a CS (Collection Server) is optional and not mandatory. That is decided by the F@H team when they are configuring servers and projects. Given that most of the F@H team is located in USA, it will be few hours before it's Monday morning for them and given the pandemic situation, additional time might be required to investigate and resolve it.
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time

Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
crossj
Posts: 3
Joined: Sun Apr 05, 2020 4:55 am

Re: Can't upload to 140.163.4.231:80

Post by crossj »

PantherX wrote:Humm, I checked the Server Status (https://apps.foldingathome.org/serverstats) and I can't see anything wrong with it. However, you're not along in this (viewtopic.php?f=18&t=33905). I am sure that the F@H Team will look into this soon.

FYI, if you're using Windows 10, there's a difference between Shutdown and Reboot. If you're attempting to troubleshoot an issue, perform a reboot as that will reload the kernel. Doing a shutdown and then power up doesn't do that (https://www.howtogeek.com/349114/shutti ... g-it-does/). In this case, I don't think it will make a difference as the issue seems to be Server side.
Thanks for getting back :)
And yup, looks like you're totally correct on the reboot probably making no difference. I did it just in case but sadly looks like we're still stuck :(

Code: Select all

*********************** Log Started 2020-04-06T08:05:09Z ***********************
08:05:09:WU00:FS01:Sending unit results: id:00 state:SEND error:NO_ERROR project:11749 run:0 clone:1992 gen:11 core:0x22 unit:0x0000001b8ca304e75e6a8006939381ba
08:05:09:WU00:FS01:Uploading 12.57MiB to 140.163.4.231
08:05:09:WU00:FS01:Connecting to 140.163.4.231:8080
08:05:31:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
08:05:31:WU00:FS01:Connecting to 140.163.4.231:80
08:05:52:WARNING:WU00: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:05:52:WU00:FS01:Sending unit results: id:00 state:SEND error:NO_ERROR project:11749 run:0 clone:1992 gen:11 core:0x22 unit:0x0000001b8ca304e75e6a8006939381ba
08:05:52:WU00:FS01:Uploading 12.57MiB to 140.163.4.231
08:05:52:WU00:FS01:Connecting to 140.163.4.231:8080
08:06:13:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
08:06:13:WU00:FS01:Connecting to 140.163.4.231:80
08:06:22:WU00:FS01:Upload 0.50%
08:07:37:WU00:FS01:Upload 0.99%
08:07:37:WARNING:WU00:FS01:Exception: Failed to send results to work server: Transfer failed
08:07:38:WU00:FS01:Sending unit results: id:00 state:SEND error:NO_ERROR project:11749 run:0 clone:1992 gen:11 core:0x22 unit:0x0000001b8ca304e75e6a8006939381ba
08:07:38:WU00:FS01:Uploading 12.57MiB to 140.163.4.231
08:07:38:WU00:FS01:Connecting to 140.163.4.231:8080
08:07:59:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
08:07:59:WU00:FS01:Connecting to 140.163.4.231:80
08:08:20:WARNING:WU00: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:09:15:WU00:FS01:Sending unit results: id:00 state:SEND error:NO_ERROR project:11749 run:0 clone:1992 gen:11 core:0x22 unit:0x0000001b8ca304e75e6a8006939381ba
08:09:15:WU00:FS01:Uploading 12.57MiB to 140.163.4.231
08:09:15:WU00:FS01:Connecting to 140.163.4.231:8080
08:09:36:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
08:09:36:WU00:FS01:Connecting to 140.163.4.231:80
08:09:57:WARNING:WU00: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.
Fingers crossed the F@H team will look into it sooner than later. For me it's not really the points that matter I'd just like to help out as much as I'd be able to ;)

Thanks
boarder2k7
Posts: 1
Joined: Mon Apr 06, 2020 1:20 pm

Re: Can't upload to 140.163.4.231:80

Post by boarder2k7 »

I'm having this same issue with this server, I've been attempting a return for three days now. I'm honestly about ready to reinstall the client just to dump this bad WU. Last seen on this server is 2020-04-01T20:11:10Z
konyak_ad
Posts: 3
Joined: Tue Apr 07, 2020 5:47 am

Re: Can't upload to 140.163.4.231:80

Post by konyak_ad »

I'm having the same issue too, the client cannot connect to the server or fails uploading at 0.57%, this WU was completed 4 days ago.

Code: Select all

05:37:52:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:465 gen:13 core:0x22 unit:0x000000258ca304e75e6a7fc752bbff71
05:37:52:WU01:FS01:Uploading 21.92MiB to 140.163.4.231
05:37:52:WU01:FS01:Connecting to 140.163.4.231:8080
05:38:13:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
05:38:13:WU01:FS01:Connecting to 140.163.4.231:80
05:38:34:WARNING:WU01:FS01:Exception: Failed to send results to work server: Failed to connect to 140.163.4.231:80: A kapcsolódási kísérlet nem sikerült, mert a kapcsolódó partner nem válaszolt a megadott időn belül, vagy a létrehozott kapcsolatban hiba történt, mert a kapcsolódó partner nem volt képes válaszolni.
05:40:29:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:465 gen:13 core:0x22 unit:0x000000258ca304e75e6a7fc752bbff71
05:40:29:WU01:FS01:Uploading 21.92MiB to 140.163.4.231
05:40:29:WU01:FS01:Connecting to 140.163.4.231:8080
05:41:43:WU01:FS01:Upload 0.57%
05:41:43:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
TheySaidNo
Posts: 1
Joined: Tue Apr 07, 2020 7:15 am

Re: Can't upload to 140.163.4.231:80

Post by TheySaidNo »

Having the same issue with WU completed few days ago.
Not too critical, at least for me, since I've got other WUs for my gpu done and sent after that one got stuck for some reason.

Code: Select all

*********************** Log Started 2020-04-06T06:55:14Z ***********************
06:55:14:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
06:55:14:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
06:55:14:WU01:FS01:Connecting to 140.163.4.231:8080
06:55:35:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
06:55:35:WU01:FS01:Connecting to 140.163.4.231:80
06:55:56: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.
06:55:57:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
06:55:57:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
06:55:57:WU01:FS01:Connecting to 140.163.4.231:8080
06:56:18:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
06:56:18:WU01:FS01:Connecting to 140.163.4.231:80
06:56:39: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.
06:57:34:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
06:57:34:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
06:57:34:WU01:FS01:Connecting to 140.163.4.231:8080
06:58:02:WU01:FS01:Upload 0.57%
06:58:02:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
07:00:11:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
07:00:11:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
07:00:11:WU01:FS01:Connecting to 140.163.4.231:8080
07:00:32:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
07:00:32:WU01:FS01:Connecting to 140.163.4.231:80
07:00:33:WU01:FS01:Upload 0.28%
07:00:59:WU01:FS01:Upload 0.57%
07:00:59:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
07:04:25:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
07:04:25:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
07:04:25:WU01:FS01:Connecting to 140.163.4.231:8080
07:04:47:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
07:04:47:WU01:FS01:Connecting to 140.163.4.231:80
07:04:50:WU01:FS01:Upload 0.28%
07:05:58:WU01:FS01:Upload 0.57%
07:05:58:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
07:11:17:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
07:11:17:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
07:11:17:WU01:FS01:Connecting to 140.163.4.231:8080
07:11:43:WU01:FS01:Upload 0.57%
07:11:43:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
07:22:22:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
07:22:22:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
07:22:22:WU01:FS01:Connecting to 140.163.4.231:8080
07:22:43:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
07:22:43:WU01:FS01:Connecting to 140.163.4.231:80
07:23:04: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:40:19:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
07:40:19:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
07:40:19:WU01:FS01:Connecting to 140.163.4.231:8080
07:40:26:WU01:FS01:Upload 0.28%
07:42:03:WU01:FS01:Upload 0.57%
07:42:03:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
08:09:21:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
08:09:21:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
08:09:21:WU01:FS01:Connecting to 140.163.4.231:8080
08:09:47:WU01:FS01:Upload 0.57%
08:09:47:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
08:56:20:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
08:56:20:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
08:56:20:WU01:FS01:Connecting to 140.163.4.231:8080
08:58:00:WU01:FS01:Upload 0.57%
08:58:00:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
10:12:21:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
10:12:21:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
10:12:21:WU01:FS01:Connecting to 140.163.4.231:8080
10:12:42:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
10:12:42:WU01:FS01:Connecting to 140.163.4.231:80
10:13: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.
12:15:20:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
12:15:20:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
12:15:20:WU01:FS01:Connecting to 140.163.4.231:8080
12:17:00:WU01:FS01:Upload 0.57%
12:17:00:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
******************************* Date: 2020-04-06 *******************************
15:34:21:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
15:34:21:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
15:34:21:WU01:FS01:Connecting to 140.163.4.231:8080
15:34:42:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
15:34:42:WU01:FS01:Connecting to 140.163.4.231:80
15:35: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.
15:35:21:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
15:35:21:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
15:35:21:WU01:FS01:Connecting to 140.163.4.231:8080
15:35:42:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
15:35:42:WU01:FS01:Connecting to 140.163.4.231:80
15:36: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.
15:36:58:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
15:36:58:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
15:36:58:WU01:FS01:Connecting to 140.163.4.231:8080
15:37:19:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
15:37:19:WU01:FS01:Connecting to 140.163.4.231:80
15:37:40: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.
15:39:35:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
15:39:35:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
15:39:35:WU01:FS01:Connecting to 140.163.4.231:8080
15:39:56:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
15:39:56:WU01:FS01:Connecting to 140.163.4.231:80
15:40:18: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.
15:43:50:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
15:43:50:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
15:43:50:WU01:FS01:Connecting to 140.163.4.231:8080
15:45:05:WU01:FS01:Upload 0.57%
15:45:05:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
15:50:41:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
15:50:41:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
15:50:41:WU01:FS01:Connecting to 140.163.4.231:8080
15:51:02:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
15:51:02:WU01:FS01:Connecting to 140.163.4.231:80
15:51: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.
16:01:46:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
16:01:47:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
16:01:47:WU01:FS01:Connecting to 140.163.4.231:8080
16:01:54:WU01:FS01:Upload 0.28%
16:03:30:WU01:FS01:Upload 0.57%
16:03:31:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
16:19:43:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
16:19:43:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
16:19:43:WU01:FS01:Connecting to 140.163.4.231:8080
16:20:05:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
16:20:05:WU01:FS01:Connecting to 140.163.4.231:80
16:20:06:WU01:FS01:Upload 0.28%
16:21:14:WU01:FS01:Upload 0.57%
16:21:14:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
16:48:45:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
16:48:46:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
16:48:46:WU01:FS01:Connecting to 140.163.4.231:8080
16:49:07:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
16:49:07:WU01:FS01:Connecting to 140.163.4.231:80
16:49:28: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.
17:35:44:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
17:35:44:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
17:35:44:WU01:FS01:Connecting to 140.163.4.231:8080
17:36:05:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
17:36:05:WU01:FS01:Connecting to 140.163.4.231:80
17:36:08:WU01:FS01:Upload 0.28%
17:37:17:WU01:FS01:Upload 0.57%
17:37:17:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
18:51:45:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
18:51:45:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
18:51:45:WU01:FS01:Connecting to 140.163.4.231:8080
18:52:06:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
18:52:06:WU01:FS01:Connecting to 140.163.4.231:80
18:52:27: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-06 *******************************
******************************* Date: 2020-04-07 *******************************
06:26:52:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
06:26:58:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
06:26:58:WU01:FS01:Connecting to 140.163.4.231:8080
06:28:37:WU01:FS01:Upload 0.57%
06:28:38:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
06:28:38:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
06:28:38:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
06:28:38:WU01:FS01:Connecting to 140.163.4.231:8080
06:28:59:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
06:28:59:WU01:FS01:Connecting to 140.163.4.231:80
06:29:00:WU01:FS01:Upload 0.28%
06:30:58:WU01:FS01:Upload 0.57%
06:30:58:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
06:30:58:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
06:30:58:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
06:30:58:WU01:FS01:Connecting to 140.163.4.231:8080
06:31:19:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
06:31:19:WU01:FS01:Connecting to 140.163.4.231:80
06:31:20:WU01:FS01:Upload 0.28%
06:33:18:WU01:FS01:Upload 0.57%
06:33:18:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
06:33:35:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
06:33:35:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
06:33:35:WU01:FS01:Connecting to 140.163.4.231:8080
06:33:56:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
06:33:56:WU01:FS01:Connecting to 140.163.4.231:80
06:33:57:WU01:FS01:Upload 0.28%
06:35:05:WU01:FS01:Upload 0.57%
06:35:06:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
06:37:49:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
06:37:49:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
06:37:49:WU01:FS01:Connecting to 140.163.4.231:8080
06:37:57:WU01:FS01:Upload 0.28%
06:39:33:WU01:FS01:Upload 0.57%
06:39:33:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
06:44:41:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
06:44:41:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
06:44:41:WU01:FS01:Connecting to 140.163.4.231:8080
06:45:02:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
06:45:02:WU01:FS01:Connecting to 140.163.4.231:80
06:45: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.
06:55:46:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
06:55:46:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
06:55:46:WU01:FS01:Connecting to 140.163.4.231:8080
06:56:08:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
06:56:08:WU01:FS01:Connecting to 140.163.4.231:80
06:56:23:WU01:FS01:Upload 0.28%
06:57:31:WU01:FS01:Upload 0.57%
06:57:31:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed
07:13:43:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11747 run:0 clone:774 gen:15 core:0x22 unit:0x000000218ca304e75e6a7fc807cb0b4f
07:13:43:WU01:FS01:Uploading 21.93MiB to 140.163.4.231
07:13:43:WU01:FS01:Connecting to 140.163.4.231:8080
07:14:04:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
07:14:04:WU01:FS01:Connecting to 140.163.4.231:80
07:14:12:WU01:FS01:Upload 0.28%
07:15:20:WU01:FS01:Upload 0.57%
07:15:20:WARNING:WU01:FS01:Exception: Failed to send results to work server: Transfer failed

Manfred.Knick
Posts: 36
Joined: Wed Mar 25, 2020 10:21 am
Hardware configuration: Multiple XEON + GTX
Location: Germany

Re: Can't upload to 140.163.4.231:80

Post by Manfred.Knick »

For this server, https://apps.foldingathome.org/serverstats states:

- 1 Warning: collection server not connected
- has CS: No (fah4.eastus.cloudapp.azure.com)
PantherX
Site Moderator
Posts: 7020
Joined: Wed Dec 23, 2009 9:33 am
Hardware configuration: V7.6.21 -> Multi-purpose 24/7
Windows 10 64-bit
CPU:2/3/4/6 -> Intel i7-6700K
GPU:1 -> Nvidia GTX 1080 Ti
§
Retired:
2x Nvidia GTX 1070
Nvidia GTX 675M
Nvidia GTX 660 Ti
Nvidia GTX 650 SC
Nvidia GTX 260 896 MB SOC
Nvidia 9600GT 1 GB OC
Nvidia 9500M GS
Nvidia 8800GTS 320 MB

Intel Core i7-860
Intel Core i7-3840QM
Intel i3-3240
Intel Core 2 Duo E8200
Intel Core 2 Duo E6550
Intel Core 2 Duo T8300
Intel Pentium E5500
Intel Pentium E5400
Location: Land Of The Long White Cloud
Contact:

Re: Can't upload to 140.163.4.231:80

Post by PantherX »

Manfred.Knick wrote:For this server, https://apps.foldingathome.org/serverstats states:

- 1 Warning: collection server not connected
- has CS: No (fah4.eastus.cloudapp.azure.com)
Unfortunately, that isn't the cause of this issue since configuring a CS is optional and not required for the successful upload of completed WUs.
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time

Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
Manfred.Knick
Posts: 36
Joined: Wed Mar 25, 2020 10:21 am
Hardware configuration: Multiple XEON + GTX
Location: Germany

Re: Can't upload to 140.163.4.231:80

Post by Manfred.Knick »

Observations:

Currently, all (WS) servers of Chodera lab // MSKCC
- 140.163.4.231 = plfah1-1.mskcc.org (Accept)
- 140.163.4.241 = plfah2-1.mskcc.org (Accept) (*)
- 140.163.4.233 = plfah1-3.mskcc.org (Down)
seem to be affected.

(*) Reference: "140.163.4.241 low disk space"
viewtopic.php?f=18&t=34058

WHOIS:
- CIDR: 140.163.0.0/16
- Organization: Memorial Sloan Kettering (MSK-1)

For the referenced Collection server 52.224.109.74 = fah4.eastus.cloudapp.azure.com,
https://apps.foldingathome.org/serverstats states:
- 1 Warnings: No collection servers
- Has CS: No

Fortunately, my client(s) (*) re-try bravely and reliably,
so the WU results computed should not get lost -
at least as long as EOL allows.
Post Reply