• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

can't connect to work server?

S

screwallyall

n00b
Joined
Sep 1, 2004
Messages
42
for some reason i've been getting this error ever since i finished my last work unit last night


[15:11:26] + Attempting to get work packet
[15:11:26] - Connecting to assignment server
[15:11:26] - Successful: assigned to (171.64.122.134).
[15:11:26] + News From Folding@Home: Welcome to Folding@Home
[15:11:27] Loaded queue successfully.
[15:11:27] - Couldn't send HTTP request to server
[15:11:27] (Got status 503)
[15:11:27] + Could not connect to Work Server
[15:11:27] - Error: Attempt #10 to get work failed, and no other work to do.
Waiting before retry.


anyone else getting this? i tried restarted the client, which didn't help any. maybe its a problem with stanford?
 
dialup? broadband?

did you recently install a firewall/router/change setttings in either?

If you stop the client and run it with the -sendall flag, does it send/connect?


Keep on Folding!! For the [H]orde!!

 
btw, isn't it the "send all" flag?

i remember trying to use "sendall" and FAH saying "incorrect flag" or some such...
 
maybe.... it's in the sticky :D


Keep on Folding!! For the [H]orde!!

 
hmm. well i just tried using send all, and i just got the "Folding@Home Client Shutdown" message. so then i tried running the client from the command line, and it started up and loaded a work unit normally. i usually have it running from a script that loads when i start up(i'm running the linux client). so the problem is solved, even though i don't know what exactly the problem was in the first place.
 
Well each server is assigned a different project. So what happens is that you download a WU and when done, it wants to send it back to the point of origin. The projects assigned to each server can be found here: http://vspx27.stanford.edu/psummary.html.

 
they do have it set up now, or at least are working on it, so that it doesn't HAVE to go back to the originating server.... Not sure where they are with that now...


Keep on Folding!! For the [H]orde!!

 
I just thought that I would say that I am getting the same error as the original poster. However, I did just install a router, but do not see any setting that would keep it from getting WUs.
 
i was getting the same thing after i turned in a WU earlier this morning. i let it retry for about 30 mins and it finally went. one of their servers must have been down or something.
 
Same here - can't get new WU, will have to run TT's.
 
Had that happen today.
Got up to the tenth attempt as well.

When that happens I tend to shut it down for a minute or two, then restart the client.
The aim is to try a get another server when you restart.
if it work good.
If not, then it another restart when it hits five.
It bogs the servers down more doing that as you send in more requests for a work unit, but you tend to get one quicker.

PS. It not as bad as it has been.

Luck.......... :D
 
Server .133 is having major problems. I started and stopped the service a few times and finally it got assigned to .134, and still that retried a few times. Been checking the stanford forums and alot of people over there are having the same problems, the fix seems to be is to stop FAH, not allow big packets, and restart FAH. I did this to my other machines and they are now chugging along. Slow WU's for a A64 tho, so make sure to change your config back after you get a WU.

 
You must log in or register to reply here.
Back
Top