Page 1 of 1

Unable to get SMP work

Posted: Tue Apr 13, 2010 7:40 pm
by Kenelm
I now have 5 computers with this same message. Have been unable to get work for 3 days now.

Code: Select all

[08:02:27] - Connecting to assignment server
[08:02:27] Connecting to http://assign.stanford.edu:8080/
[08:02:27] Posted data.
[08:02:27] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[08:02:27] + Couldn't get work instructions.
[08:02:27] - Attempt #29  to get work failed, and no other work to do.
Waiting before retry.
[08:50:32] + Attempting to get work packet
[08:50:32] Passkey found
[08:50:32] - Will indicate memory of 3069 MB
[08:50:32] - Connecting to assignment server
[08:50:32] Connecting to http://assign.stanford.edu:8080/
[08:50:33] Posted data.
[08:50:33] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[08:50:33] + Couldn't get work instructions.
[08:50:33] - Attempt #30  to get work failed, and no other work to do.
Waiting before retry.
[09:38:40] + Attempting to get work packet
[09:38:40] Passkey found
[09:38:40] - Will indicate memory of 3069 MB
[09:38:40] - Connecting to assignment server
[09:38:40] Connecting to http://assign.stanford.edu:8080/
[09:38:40] Posted data.
[09:38:40] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[09:38:40] + Couldn't get work instructions.
[09:38:40] - Attempt #31  to get work failed, and no other work to do.
Waiting before retry.
[10:26:45] + Attempting to get work packet
[10:26:45] Passkey found
[10:26:45] - Will indicate memory of 3069 MB
[10:26:45] - Connecting to assignment server
[10:26:45] Connecting to http://assign.stanford.edu:8080/
[10:26:46] Posted data.
[10:26:46] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[10:26:46] + Couldn't get work instructions.
[10:26:46] - Attempt #32  to get work failed, and no other work to do.
Waiting before retry.
[11:14:50] + Attempting to get work packet
[11:14:50] Passkey found
[11:14:50] - Will indicate memory of 3069 MB
[11:14:50] - Connecting to assignment server
[11:14:50] Connecting to http://assign.stanford.edu:8080/
[11:14:51] Posted data.
[11:14:51] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[11:14:51] + Couldn't get work instructions.
[11:14:51] - Attempt #33  to get work failed, and no other work to do.
Waiting before retry.
[12:02:53] + Attempting to get work packet
[12:02:53] Passkey found
[12:02:53] - Will indicate memory of 3069 MB
[12:02:53] - Connecting to assignment server
[12:02:53] Connecting to http://assign.stanford.edu:8080/
[12:02:53] Posted data.
[12:02:53] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[12:02:53] + Couldn't get work instructions.
[12:02:53] - Attempt #34  to get work failed, and no other work to do.
Waiting before retry.
[12:19:11] - Autosending finished units... [April 13 12:19:11 UTC]
[12:19:11] Trying to send all finished work units
[12:19:11] + No unsent completed units remaining.
[12:19:11] - Autosend completed
[12:51:05] + Attempting to get work packet
[12:51:05] Passkey found
[12:51:05] - Will indicate memory of 3069 MB
[12:51:05] - Connecting to assignment server
[12:51:05] Connecting to http://assign.stanford.edu:8080/
[12:51:05] Posted data.
[12:51:05] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[12:51:05] + Couldn't get work instructions.
[12:51:05] - Attempt #35  to get work failed, and no other work to do.
Waiting before retry.
[13:39:10] + Attempting to get work packet
[13:39:10] Passkey found
[13:39:10] - Will indicate memory of 3069 MB
[13:39:10] - Connecting to assignment server
[13:39:10] Connecting to http://assign.stanford.edu:8080/
[13:39:11] Posted data.
[13:39:11] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[13:39:11] + Couldn't get work instructions.
[13:39:11] - Attempt #36  to get work failed, and no other work to do.
Waiting before retry.
[14:27:20] + Attempting to get work packet
[14:27:20] Passkey found
[14:27:20] - Will indicate memory of 3069 MB
[14:27:20] - Connecting to assignment server
[14:27:20] Connecting to http://assign.stanford.edu:8080/
[14:27:21] Posted data.
[14:27:21] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[14:27:21] + Couldn't get work instructions.
[14:27:21] - Attempt #37  to get work failed, and no other work to do.
Waiting before retry.
[15:15:24] + Attempting to get work packet
[15:15:24] Passkey found
[15:15:24] - Will indicate memory of 3069 MB
[15:15:24] - Connecting to assignment server
[15:15:24] Connecting to http://assign.stanford.edu:8080/
[15:15:25] Posted data.
[15:15:25] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[15:15:25] + Couldn't get work instructions.
[15:15:25] - Attempt #38  to get work failed, and no other work to do.
Waiting before retry.
[16:03:33] + Attempting to get work packet
[16:03:33] Passkey found
[16:03:33] - Will indicate memory of 3069 MB
[16:03:33] - Connecting to assignment server
[16:03:33] Connecting to http://assign.stanford.edu:8080/
[16:03:34] Posted data.
[16:03:34] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[16:03:34] + Couldn't get work instructions.
[16:03:34] - Attempt #39  to get work failed, and no other work to do.
Waiting before retry.
[16:51:35] + Attempting to get work packet
[16:51:35] Passkey found
[16:51:35] - Will indicate memory of 3069 MB
[16:51:35] - Connecting to assignment server
[16:51:35] Connecting to http://assign.stanford.edu:8080/
[16:51:35] Posted data.
[16:51:35] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[16:51:35] + Couldn't get work instructions.
[16:51:35] - Attempt #40  to get work failed, and no other work to do.
Waiting before retry.
[17:39:40] + Attempting to get work packet
[17:39:40] Passkey found
[17:39:40] - Will indicate memory of 3069 MB
[17:39:40] - Connecting to assignment server
[17:39:40] Connecting to http://assign.stanford.edu:8080/
[17:39:40] Posted data.
[17:39:40] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[17:39:40] + Couldn't get work instructions.
[17:39:40] - Attempt #41  to get work failed, and no other work to do.
Waiting before retry.
[18:19:11] - Autosending finished units... [April 13 18:19:11 UTC]
[18:19:11] Trying to send all finished work units
[18:19:11] + No unsent completed units remaining.
[18:19:11] - Autosend completed
[18:27:40] + Attempting to get work packet
[18:27:40] Passkey found
[18:27:40] - Will indicate memory of 3069 MB
[18:27:40] - Connecting to assignment server
[18:27:40] Connecting to http://assign.stanford.edu:8080/
[18:27:41] Posted data.
[18:27:41] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[18:27:41] + Couldn't get work instructions.
[18:27:41] - Attempt #42  to get work failed, and no other work to do.
Waiting before retry.
[19:15:42] + Attempting to get work packet
[19:15:42] Passkey found
[19:15:42] - Will indicate memory of 3069 MB
[19:15:42] - Connecting to assignment server
[19:15:42] Connecting to http://assign.stanford.edu:8080/
[19:15:43] Posted data.
[19:15:43] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[19:15:43] + Couldn't get work instructions.
[19:15:43] - Attempt #43  to get work failed, and no other work to do.
Waiting before retry.

Re: Unable to get SMP work

Posted: Tue Apr 13, 2010 7:45 pm
by 7im
What client version? What client type? Configured for BigWus?

Re: Unable to get SMP work

Posted: Tue Apr 13, 2010 8:41 pm
by klasseng
I've got 4 mac mini's waiting too. Console client. V6.29, can't do BigWus on a Core 2 Duo eh?

Re: Unable to get SMP work

Posted: Tue Apr 13, 2010 9:04 pm
by Kenelm
# Windows SMP Console Edition #################################################
###############################################################################

Folding@Home Client Version 6.29

http://folding.stanford.edu

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

Launch directory: C:\FoldingSMP
Executable: C:\FoldingSMP\FAH6.exe
Arguments: -smp -verbosity 9

[settings]
asknet=no
machineid=1
local=78
bigpackets=normal
extra_parms=-smp -verbosity 9

[http]
active=no
host=localhost
port=8080
usereg=no

[core]
checkpoint=30
addr=

[clienttype]
type=0

Re: Unable to get SMP work

Posted: Tue Apr 13, 2010 9:08 pm
by Kenelm
Also having trouble on a non SMP:

Code: Select all

# Windows Graphical Edition ###################################################
###############################################################################

                       Folding@Home Client Version 5.03

                          http://folding.stanford.edu

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

Launch directory: C:\Folding At Home

Config:

[settings]
asknet=no
bigpackets=yes
machineid=1
local=82

[http]
active=no
host=localhost
port=8080
usereg=no
proxy_name=
proxy_passwd=

[graphics]
subtitle=Distributed Computing    -    http://folding.stanford.edu
drawgap=125
drawtitle=0
saver_mode_enabled=0
saver_runs_core=0
saver_idle_minutes=1
drawlogos=0
logourl=
drawmode=1

[core]
priority=0
cpuusage=100
disableassembly=no
checkpoint=15
ignoredeadlines=no

[power]
battery=no






Re: Unable to get SMP work

Posted: Tue Apr 13, 2010 9:28 pm
by PantherX
Kenelm @ I would recommend that you upgrade the Uni Client to 6,23 if possible and you can use this flag:
-advmethods
For your SMP, you may want to change the packet size to big and use the same flag as above so that you can get the a3 WUs. Also use a passkey so you can take advantage of the bonus points system once you qualify.

klasseng @ you need at least 8 cores, the lowest model on Intel is i7-860 with HT enabled and that too it should be folding 24/7 to meet the deadline.

Re: Unable to get SMP work

Posted: Tue Apr 13, 2010 9:37 pm
by Kenelm
I use passkey, just cleared it out. I can do A3s they give less points then A1s, for some reason they run really slow on my machines.

Re: Unable to get SMP work

Posted: Tue Apr 13, 2010 9:48 pm
by PantherX
a3 lesser points than a1??? That's the first time I have heard it. In nearly every case, a3 gives way more points than a1 could ever get you, Why don't you use -smp X where X is one number less than the number of cores that your system have. a3 waits for the slowest core to catch up which may be causing this problem. eg, I have Core i7-860 so I have to use -smp 7 so that i get the maximum use of the SMP Client. The other free core is used for GPU Client and other Window tasks.

Re: Unable to get SMP work

Posted: Tue Apr 13, 2010 9:52 pm
by Kenelm
"Cant do A3s..."

Re: Unable to get SMP work

Posted: Tue Apr 13, 2010 10:02 pm
by Kenelm
PantherX wrote:a3 lesser points than a1??? That's the first time I have heard it. In nearly every case, a3 gives way more points than a1 could ever get you, Why don't you use -smp X where X is one number less than the number of cores that your system have. a3 waits for the slowest core to catch up which may be causing this problem. eg, I have Core i7-860 so I have to use -smp 7 so that i get the maximum use of the SMP Client. The other free core is used for GPU Client and other Window tasks.
Ill try that but its all moot if i cant get a work packet.

Re: Unable to get SMP work

Posted: Tue Apr 13, 2010 11:19 pm
by P5-133XL
Kenelm wrote:I use passkey, just cleared it out. I can do A3s they give less points then A1s, for some reason they run really slow on my machines.
Kenelm wrote:"Cant do A3s..."


I'm confused.

I'm not sure how you are judging less points and I'm not sure how you are judging really slow. If you are using FAHMon, may I suggest that you switch to HMF.net. they operate very similarly, but HFM.net includes bonus point calculations and FAHMon does not.

The base point value of the A3's is small compared to A1's giving less points. To compensate, Stanford institued a new points structure tied to the passkey giving bonus points for early return. See: Points system for SMP2 work units. Now you have to qualify for those bonus points by returning 10 A2/A3 WU's and maintain at least an 80% successful return rate. That will inevitably mean a drop in PPD until you have qualified for the bonus.

If the A3's are running slow, the first thing I would ask is if there are other processes using a significant portion of the CPU. The A3's really don't like a core being hogged by some other application like gaming or even GPU folding. They tend to start syncing to the slowest core and that can do real bad things to frame times. Even with the ATI GPU client can be a real drain and I found that I got better total PPD running just A3's than running A3's with my ATI 3870 GPU folding in addition. So I quit GPU folding on those cards. The slowdown is not linear so a 7% external CPU usage can produce a 30% drop in A3 PPD. Some people use the -smp # with the # being 1 less than the number of cores on the machine (including hyper-threaded simulated cores) to allow other processes to run without slowing down the A3 core more than linearly. Do note that dedicating one core out of four will still drop your A3 PPD very significantly. It is better with HT where you can drop one HT'ed core rather than a real core and then it will be 1/8th rather than 1/4th.

Does this help explain what is going on?

Now if you just outright can't run A3's I need more details as to what is going on. Things like a copy of the log file might help.