Page 1 of 1

assign.stanford.edu no work server available

Posted: Fri Sep 13, 2013 2:49 pm
by autogrog
System has been folding bigadv/bigbeta for a long time successfully. This AM started getting the following error msg. pasting the following line:
http://assign.stanford.edu:8080/

gets the following response:
OK

Any suggestions?

Code: Select all

# Linux SMP Console Edition ###################################################
###############################################################################

                       Folding@Home Client Version 6.34

                          http://folding.stanford.edu

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

Launch directory: /home/me/smp
Executable: /home/me/smp/fah6
Arguments: -smp 24 -bigadv -verbosity 9 

[14:28:38] - Ask before connecting: No
[14:28:38] - User name: AutoGrog (Team 39286)
[14:28:38] - User ID: ===
[14:28:38] - Machine ID: 1
[14:28:38] 
[14:28:38] Loaded queue successfully.
[14:28:38] - Preparing to get new work unit...
[14:28:38] - Autosending finished units... [September 13 14:28:38 UTC]
[14:28:38] Cleaning up work directory
[14:28:38] Trying to send all finished work units
[14:28:38] + No unsent completed units remaining.
[14:28:38] - Autosend completed
[14:28:38] + Attempting to get work packet
[14:28:38] Passkey found
[14:28:38] - Will indicate memory of 16078 MB
[14:28:38] - Connecting to assignment server
[14:28:38] Connecting to http://assign.stanford.edu:8080/
[14:28:39] Posted data.
[14:28:39] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[14:28:39] + Couldn't get work instructions.
[14:28:39] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.


Re: assign.stanford.edu no work server available

Posted: Fri Sep 13, 2013 4:29 pm
by Grandpa_01
Stanford is having network issues, although I am not sure they realize it at this time, I have seen this several times in the last few days (since they did server maintenance a few days back), hopefully they will get it straightened out before it completely crashes. But we shall see sometimes the catch it and other times they do not. I do not believe there is anything you can do about it, I have seen it reported by several others at different teams folding forums recently with greater frequency than normal and as I said I have been seeing it fairly frequently latley which is unusual. At this point in time it is just merely a nuisance and I occasionally get assigned a smp WU on 1 of the bigadv rigs most of the time it works itself out fairly rapidly. It acts like the AS is dropping connection momentarily from time to time then reconnects.

So I would not be pulling my hair out trying to fix the issue on your end, I do believe the only thing you would accomplish by doing that is going bald. :mrgreen:

Re: assign.stanford.edu no work server available

Posted: Fri Sep 13, 2013 4:47 pm
by 7im
The log posted above clearly shows the client having no problem contacting the assignment server on the Stanford network, so not likely a network issue. Also note the work server in question (128.143.231.201 serving BA WUs) is located Virginia, not at Stanford. It's more likely the problem is somewhere between Stanford and Virginia, or even at Virginia.)

The advice to be patient is good.

Re: assign.stanford.edu no work server available

Posted: Fri Sep 13, 2013 6:13 pm
by autogrog
'Patience grasshopper, patience' arg!

Thanks for the info

Re: assign.stanford.edu no work server available

Posted: Fri Sep 13, 2013 6:25 pm
by bruce
Kasson is generally the one who manages the BA assignments. There's a GROMACS workshop in Virginia this weekend and he's likely very busy. I'll notify him, but he's likely to be unable to do anything before Monday (and after that, I offer no prediction). Serverstat does say that 128.143.231.201 has very few WUs to be assigned. Make whatever plans you need to based on those assumptions.

Re: assign.stanford.edu no work server available

Posted: Fri Sep 13, 2013 10:01 pm
by Grandpa_01
It has been an ongoing problem since the server maintnance outage so it may not be an easy fix, we will just have to wait and see.

Re: assign.stanford.edu no work server available

Posted: Thu Sep 26, 2013 1:37 am
by davidbu2005fe
I'm still seeing this:
lynx http://assign.stanford.edu:8080/
gives just:
<html><b>OK</b></html>
(The word OK underlined)
It's been three weeks. All my assignments are invalid 0.0.0.0

FAH log:

[01:22:15] + Attempting to get work packet
[01:22:15] - Will indicate memory of 503 MB
[01:22:15] - Connecting to assignment server
[01:22:15] Connecting to http://assign.stanford.edu:8080/
[01:22:15] Posted data.
[01:22:15] Initial: 0000; - Successful: assigned to (0.0.0.0).
[01:22:15] + News From Folding@Home: Welcome to Folding@Home
[01:22:15] Work Unit has an invalid address.
[01:22:15] - Error: Attempt #3 to get work failed, and no other work to do.

Just commenting on the status.

If the response above is what I should expect to see, please let me know.

Thanks

Re: assign.stanford.edu no work server available

Posted: Thu Sep 26, 2013 2:04 am
by Joe_H
What is your configuration? The original post in this topic was about not being assigned bigadv WU's, from the memory size in your log it appears you do not have a system that would be bigadv eligible. Could you also post a bit more of your log, especially the beginning section which lists version and system information.

Re: assign.stanford.edu no work server available

Posted: Thu Sep 26, 2013 3:17 am
by bruce
Please describe your hardware: what kind of CPU? How much RAM? What kind of GPU (if any)?

What configuration settings did you enter when you set up FAH? (or post the config file)

Re: assign.stanford.edu no work server available

Posted: Thu Sep 26, 2013 4:18 am
by 7im
There is no work currently available for the older CPU Client. The core 78 server is still offline. You'll need client v6.34 or newer running on a multi-cored processor running fah in SMP mode to currently get work on a CPU.