Folding Forum

OK. Some people consult serverstat and understand a lot about what it says -- others do not. It's not required.

FACT: a lot of work servers went off-line earlier today. I don't know why, nor can I predict when they might be fixed but it's an unusual situation which may be contributing to your problem.

Ok... I'll just give it a few days and see if it fixes itself. My Mac Pro at home is still finishing up a work unit from a while back (because the client quit working after an OS X reinstall), so it's not attempting to get a new one now. Hopefully things will be resolved by the time it needs a new one.

You can also try to connect just via Safari to "171.67.108.200:8080" and get back a simple " OK"; that might help to check if there is a problem with network/firewall.

That doesn't work, but the port 80 ones occasionally give me an OK.

I'd be a little worried about the word "occasionally" as perhaps indicating some kind of a local problem.

I meant that I seem to be getting access denied throughout the day. They'll give me an OK consistently, then two hours later be denied consistently.

Hi aardWolf,

Something you might consider or look into:

16:59:09:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: Operation timed out

The fact that this one "timed out" sounds correct for your description of the ports being blocked or really just dead.


16:59:09:WU00:FS00:Connecting to 171.64.65.121:80
16:59:09:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.121:80': Failed to connect to 171.64.65.121:80: Connection refused

The fact that this one "Connection refused" usually means a firewall or other security software refused to allow the connection. You might want to look a the local machine firewall, security software, anti-virus/internet security packages on your machine. It might be blocking the app and not the port.

Just an idea to help you investigate.

I thought maybe the server blocked me temporarily because of all of the connections with no work units available.

aardWolf wrote:...I also chose Alzheimer's research specifically...

Please note that currently, this feature isn't fully implemented. The Clients support this but the Servers don't. Once the Servers support this (no ETAs), your preference will be taken into account.

aardWolf wrote:I thought maybe the server blocked me temporarily because of all of the connections with no work units available.

AFAIK, this hasn't happened to any F@H Donors yet. Assuming you leave the software running, the time taken between each retry increases so you wouldn't be overloading the servers with your connection requests. Occasionally, you could restart the Client to make it try again (or Pause/Fold the Slots) if you are aware that the situation is resolved and the next attempt will be in a few hours. Do note that the Next Attempt is displayed in Advanced Control (AKA FAHControl).

I checked on it this morning, and the past few connections just got an empty work server assignment. My (slightly older) Mac Pro at home is set to use 12 threads, and it successfully got work last night. I set my work Mac Pro to 12 threads, and it got another empty work server assignment on its most recent attempt.

Alright... this must be network related. I attempted using my Ethernet and Wifi connections to work. I got timeouts on port 8080, and "no work units available" on port 80. I just tethered to my iPhone, and got a 23 core work unit on the first attempt to 8080.

I've set it to use a free http proxy server using port 80, so we'll see how that works the next time it needs an update.

None of the proxy servers I've used are working, so I've given up on that for now.

Interesting side note... The client has been able to upload results to 171.64.65.124 with absolutely no trouble. It's still failing to get an assignment from 171.64.65.121:80.

Is it possible that the :80 servers don't have any jobs for my machine? Or that the :80 servers aren't functioning properly? Most people wouldn't even use them unless the :8080 server failed for some reason.

You're looking in the wrong place for a solution to your problem.

For a list of work servers that are reported available through port 80, check column "80" of the serverstat page. As of right now, it matches the list of work servers available to port 8080. Many servers are not functioning normally, but at least at the server level, it's not associated with a port 80 / port 8080 problem. Almost all of the same servers that are non-functional on port 80 are showing as REJECT to all connections.

Exceptions:
128.143.199.96
143.89.28.72 (currently has too few WUs to be assigning to anyone)
155.247.166.219

Have you had any recent successful download from those two servers?

I have had zero successful downloads that didn't come from tethering my Mac to my phone. I just searched through my logs, but I didn't see any of those IPs in them.

Just out of interests: could you install
A) a virtual Linux under VM Fusion and see if you get that one folding, to exclude local Mac OSX issues
B) install the NaCl client as they use complete different server (to my understanding);
Of course same donor ID, ..., and passkey for both options