171.64.122.139

[bruce]

viewtopic.php?p=95744#p95744 See my reply here.

[bruce]

I have clients that have been waiting more than 12 hours for WU:

Code: Select all

[02:19:53] - Preparing to get new work unit...
[02:19:53] + Attempting to get work packet
[02:19:53] - Connecting to assignment server
[02:19:54] - Successful: assigned to (171.64.122.139).
[02:19:54] + News From Folding@Home: Welcome to Folding@Home
. . .[/quote]

This is posted in the wrong thread.  The title says that assign.stanford.edu is down, but your client successfully connected to the assignment server at [02:19:53] and was assigned to the work server 171.64.122.139.  The fact that the work server didn't assign you a new WU is a problem with the work server, not the assignment server.

I'll move this discussion to a topic discussing server .139.

[bruce]

Since server .139 currently has zero WUs to distribute, the Assignment Server should be sending you to some other server for your next WU. If anybody is still trying to get work from .139, please post a recent segment of FAHlog and we'll see if there is some other problem that can be identified.

Serverstat seems to be saying that nobody is being assigned to .139, so I'll consider the problem closed unless there are any new reports below.

[brityank]

bruce & toTOW -

Just to verify what I believe to be a misperception of the term; -advmethods actually enables the flag, not disables it, much the same as "-local" and "-verbose x" do. Is that not correct?

[bruce]

I don't understand your question. Where is the misperception?

When -advmethods is added, you're signifying that you're willing to accept WUs that are somewhat less stable than just those from fully mature projects. Without that flag, the default condition is accept only mature projects.