Folding Forum

I am having the same problem with 52.224.109.74:80 and 40.114.52.201:80. I plan to stop folding and check every few days whether the fault is corrected before I continue.

alantear wrote:I am having the same problem with 52.224.109.74:80 and 40.114.52.201:80. I plan to stop folding and check every few days whether the fault is corrected before I continue.

Why would you? The faulty servers won't give out new WUs, so every new WU you download now will very likely complete and be uploaded just fine. Just those that were downloaded, but not finished, before the servers failed, will "hang" there until they expire. But everything else should just continue.

I think Neil-B's advice is perfectly sound, as that seems to be exactly what happens:

Neil-B wrote:[...] let your client handle this (it will retry until the server is up and it uploads or until it passes expiration and is dumped by the client) and keeping folding from the servers that are up would be the normal approach (the client is designed to work this way) [...]

I can confirm that all my 6 clients, including the 3 that have "hanging" work-units, continue to download, fold and upload work units as usual, with only that one brief "hiccup". And I did not touch them at all.


Bernd

Just a heads up though ... and not really this thread but relevant under current circumstances:

Server page shows 35 WS in total - 7 are down, 11 are accept only so less than half WS farm is serving out WUs - other threads as indicating that the AS are possibly struggling to find non busy WS to send people to for new assignments - so in this current circumstances people need to be prepared for some possible "no WUs available for this configuration" delays in getting new WUs.

As I said not an answer to this topic as such but something to be prepared for under current situation.

I would attach the log files but can not find the option.
0xa7: Project: 14819 (Run 1842, Clone 0, Gen 219)
project:14819 run:1842 clone:0 gen:219 core:0xa7
Is done but I am stuck with it.

Both servers are down actually.
https://apps.foldingathome.org/serverstats
Your topic is also discussed here:
viewtopic.php?f=108&t=35814

Thanks for the replies. As others have mentioned the new WU are going fine, so no big deal. My OCD doesn't like the stuck WU being there, but I'll manage!

An inquiry... How does the F@H client handle completed WU' results that are waiting to be sent back, as far as expiration time outs/dumping when the CS is down?

Paul

The client will keep trying to send until the expiration deadline is passed at which time it will remove/delete/drop the WU.

Ichbin3 wrote:Both servers are down actually.
https://apps.foldingathome.org/serverstats
Your topic is also discussed here:
viewtopic.php?f=108&t=35814

THX

That's what I thought.... [Expletive] gremlins!! I'd like to be able to fold them up, and return them to the sender (international FedEx/UPS fees due on arrival).

OTOH: Hopefully there will be a progress update, as soon as one of the Project Managers are able to give us one. Till then: Keep folding!!!

Paul

At least the web server part. Because fah4 does ping:

ping 146.94.192.82
PING 146.94.192.82 (146.94.192.82) 56(84) bytes of data.
64 bytes from 146.94.192.82: icmp_seq=1 ttl=57 time=129 ms
64 bytes from 146.94.192.82: icmp_seq=2 ttl=57 time=129 ms
64 bytes from 146.94.192.82: icmp_seq=3 ttl=57 time=129 ms

But it does not respond on ports 80 and 8080:

10:07:11:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
10:07:11:WU01:FS01:Connecting to 52.224.109.74:80
10:07:11:ERROR:WU01:FS01:Exception: Failed to connect to 52.224.109.74:80: Connection refused

Same issue with fah1.eastus.cloudapp.azure.com: pings okay:
PING fah1.eastus.cloudapp.azure.com (40.114.52.201) 56(84) bytes of data.
64 bytes from fah1.eastus.cloudapp.azure.com (40.114.52.201): icmp_seq=1 ttl=45 time=132 ms
64 bytes from fah1.eastus.cloudapp.azure.com (40.114.52.201): icmp_seq=2 ttl=45 time=115 ms

but refuses to connect on 80 or 8080:
10:07:10:WU01:FS01:Connecting to 40.114.52.201:8080
10:07:10:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
10:07:10:WU01:FS01:Connecting to 40.114.52.201:80
10:07:10:WARNING:WU01:FS01:Exception: Failed to send results to work server: Failed to connect to 40.114.52.201:80: Connection refused

A quick check with Firefox confirms: fah1 and fa4 cannot be contacted. They are listed as down on the server stats page, too.
Problems with Azure?

There are a number of threads on this topic ... and the server status page clarifies which servers are down

Ah, I see there was a posting about a larger server down situation, sorry I did not see that (only searched by IP and name...).

Have WUs on two machines that have been trying to upload results to 52.224.109.74 for several days.

Four servers (inc this one) "went down" on Friday 17th - see Last Contact https://apps.foldingathome.org/serverstats.

Whilst there ahs been no formal statement afaik re these it would appear something happened and that the resolution is not a simple one (and there has been a weekend to delay things further) ... Hopefully the servers will come up again soon, but until then it is simply the case of letting you client handle the retry attempts and hoping the WU(s) get a chance to upload before the expiration deadline is reached, at which point the WU(s) will be automatically dumped by the client.