No appropriate work server was available

[rjbelans]

My CPU classic client is stopped and looking for a new wu.

The log file looks like this when client was restarted.

--- Opening Log file [February 20 19:43:51 UTC]


# Windows CPU Systray Edition #################################################
###############################################################################

Folding@Home Client Version 6.23

http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: C:\Users\Owner\AppData\Roaming\Folding@home-cpu 2
Arguments: -verbosity 9

[19:43:51] - Ask before connecting: No
[19:43:51] - User name: Afterburners (Team 111065)
[19:43:51] - User ID: 59B2A25B37819F8A
[19:43:51] - Machine ID: 15
[19:43:51]
[19:43:51] Loaded queue successfully.
[19:43:51] Initialization complete
[19:43:51] - Preparing to get new work unit...
[19:43:51] + Attempting to get work packet
[19:43:51] - Autosending finished units... [February 20 19:43:51 UTC]
[19:43:51] Trying to send all finished work units
[19:43:51] + No unsent completed units remaining.
[19:43:51] - Autosend completed
[19:43:51] - Will indicate memory of 8183 MB
[19:43:51] - Detect CPU. Vendor: GenuineIntel, Family: 6, Model: 14, Stepping: 5
[19:43:51] - Connecting to assignment server
[19:43:51] Connecting to http://assign.stanford.edu:8080/
[19:43:52] Posted data.
[19:43:52] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[19:43:52] + Couldn't get work instructions.
[19:43:52] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[19:44:10] + Attempting to get work packet
[19:44:10] - Will indicate memory of 8183 MB
[19:44:10] - Connecting to assignment server
[19:44:10] Connecting to http://assign.stanford.edu:8080/
[19:44:10] Posted data.
[19:44:10] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[19:44:10] + Couldn't get work instructions.
[19:44:10] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.

And it just keeps repeating.

Is there a new problem with the servers?

(Sorry for the long post. Can't see a way to attach log file)

[Pette Broad]

Multiple machines with no work here. Tried all the usual flag and small, normal, big settings and left it at that. Just had a quick look at the server status and the only 2 servers I've had work from for the last couple of weeks 13 and 111 are both down.


Pete

[rjbelans]

Just took a look at my other setup and the GPUs are getting new work fine for me. I will update the next time another CPU tries to get new work or if this one starts working again.

[7im]

Add the -advmethods flag/setting and see if that helps. Sometimes if the failover settings aren't setup correctly, the assignment server won't roll over to other work users like it should.

[rjbelans]

Add the -advmethods flag/setting and see if that helps. Sometimes if the failover settings aren't setup correctly, the assignment server won't roll over to other work users like it should.

Were you replying to me or Pette?

I am just running classic CPU client with -verbosity 9 flag and has been running fine for 3 months now, until this.

EDIT:

Just got the following in the log.

[20:28:01] + Attempting to get work packet
[20:28:01] - Will indicate memory of 8183 MB
[20:28:01] - Connecting to assignment server
[20:28:01] Connecting to http://assign.stanford.edu:8080/
[20:28:22] - Couldn't send HTTP request to server
[20:28:22] + Could not connect to Assignment Server
[20:28:22] Connecting to http://assign2.stanford.edu:80/
[20:28:23] Posted data.
[20:28:23] Initial: 41AB; - Successful: assigned to (171.65.103.160).
[20:28:23] + News From Folding@Home: Welcome to Folding@Home
[20:28:23] Loaded queue successfully.
[20:28:23] Connecting to http://171.65.103.160:80/
[20:28:23] - Couldn't send HTTP request to server
[20:28:23] (Got status 503)
[20:28:23] + Could not connect to Work Server
[20:28:23] - Attempt #10 to get work failed, and no other work to do.
Waiting before retry.

[7im]

Both.

[rjbelans]

I thought -advmethods was for SMP. Also, my configuration using the GUI allows wu greater than 10MB. Are you suggesting that I need to run -advmethods on CPU clients? I have had as many as 16 running at a given time and never had this problem before.

EDIT:

There are now 2 CPU classic clients with the same thing happening on 2 different machines.

[7im]

With clients sitting idle, why wait to try my suggestion...?

-advmethods is applicable to both CPU clients and SMP clients.

http://fahwiki.net/index.php/How_do_I_k ... they_do%3F

Because -advmethods is a request for late stage beta work units, it sometimes has the affect of requesting different types of work units. And those different WUs would be on a different server. And that different server might just send you a work unit when the previous server wouldn't until someone fixes it.

But if you'd rather wait for a 2nd opinion, be my guest.

[John Naylor]

-advmethods applies to any client. A uniprocessor client running with -advmethods will get prerelease uniprocessor units, just like SMP clients get the prerelease a3 core.

On a side note, I have two clients with this error as well.

[7im]

This error as well, using that switch or not?

[toTOW]

You might also want to change your "WU size" setting too ... if it can't get Big WUs, try Normal or Small ones.

Changing the reported memory size might help too.

[John Naylor]

This error as well, using that switch or not?

Caught me out for being imprecise I'm not using that flag atm, will experiment and see what combinations get me an assignment (if any).

[John Naylor]

Result: at the moment, all six possible combinations (small, normal, big vs advmethods, or released) are failing to get assignments, giving the "no appropriate work server was available" message.

[rjbelans]

Adding -advmethods didn't work.

I am using the systray version. How do I change "big, normal, small" ?

Thanks for the help.

[Pette Broad]

Result: at the moment, all six possible combinations (small, normal, big vs advmethods, or released) are failing to get assignments, giving the "no appropriate work server was available" message.

One of my machines just this minute got a 44xx Gromac. Using normal and without advmethods.

Pete