Gimmi work already!

[lay-z-boy]

[16:28:41] + Attempting to get work packet
[16:28:41] - Will indicate memory of 126 MB
[16:28:41] - Connecting to assignment server
[16:28:41] Connecting to http://assign.stanford.edu:8080/
[16:28:42] Posted data.
[16:28:42] Initial: 40AB; - Successful: assigned to (171.64.122.133).
[16:28:42] + News From Folding@Home: Welcome to Folding@Home
[16:28:42] Loaded queue successfully.
[16:28:42] Connecting to http://171.64.122.133:8080/
[16:28:42] Posted data.
[16:28:42] Initial: 0000; + Could not connect to Work Server
[16:28:42] - Error: Attempt #6 to get work failed, and no other work to do.
Waiting before retry.


getting it for 2 other machines too but they are doing large packets with deadlines...
The previous wu did get sent off as well.

Any ideas to solve the problem?

tia

 

[diogenese]

Shadowscotland had someting similar, he got over it by deleting the core related to the dead server and got more work on another core.
http://forums.overclockers.co.uk/showthread.php?t=17606744

edit/ the server is up but has no work availible, the assignment server must be a bit confused http://fah-web.stanford.edu/serverstat.html

 

[rich99million]

well in the case of the one above there is no deadlineless work available - without specifying normal work the client will just keep trying to get work which isn't there


as for the other clients they may be stuck trying to get work from servers with high net loads or you may find that changing the "Use IE Connection Settings" to the opposite of whatever it is now may help
edit: also you can try adding/removing advmethods as that will send it to different servers

 

[diogenese]

Oops, I didn't realise this was for deadlineless woos

 

[lay-z-boy]

thanks for the very quick replys guys, will change as required and report back

*edit* changed it over to small deadlined wu's and it is back, it seemed just restarting the other 2 solved the problem

Thanks.