171.67.108.22 Could not connect to Work Server

[thegrub]

This is the server for the 268Xs. No problem downloading A3s if I take off the -bigadv. "Do This First" brings up the serverstats page. http://fah-web.stanford.edu/serverstat.html seems to show no problem but the WUs AVAIL has not changed at all seemingly since yesterday.

[13:06:59] + Attempting to get work packet
[13:06:59] Passkey found
[13:06:59] - Will indicate memory of 15613 MB
[13:06:59] - Connecting to assignment server
[13:06:59] Connecting to http://assign.stanford.edu:8080/
[13:07:00] Posted data.
[13:07:00] Initial: 43AB; - Successful: assigned to (171.67.108.22).
[13:07:00] + News From Folding@Home: Welcome to Folding@Home
[13:07:00] Loaded queue successfully.
[13:07:00] Sent data
[13:07:00] Connecting to http://171.67.108.22:8080/
[13:07:01] Posted data.
[13:07:01] Initial: 0000; + Could not connect to Work Server
[13:07:01] - Attempt #11 to get work failed, and no other work to do.
Waiting before retry.

[PantherX]

Please read this: http://foldingforum.org/viewtopic.php?f ... 72#p150471

[thegrub]

Read this: http://foldingforum.org/viewtopic.php?f ... 72#p150471

Yes, while I was composing he posted, my apologies. But why is the server status page still showing the 1275 units available and why is the assignment server assigning the work server if it is out of units? (no answer required)

[bruce]

It's out of a specific type of units but not all types. See Kasson's later post.

One of the questions inherent in the assignment structure is that when a server has WUs of more than one type and it has to tell the Assignment Server a single number of WUs Avail, which number should it use? Answer: Count only the least restrictive type of WUs.

Fixing the bug that he's discovered should reduce the 1275 number to nearly zero under the current conditions which will cause the Assignme3nt Server to redirect you to another server. That will also suspend the assignment of the other ~1200 WUs from being sent to those who could process them.

Question 2: What if the WUs are disjoint classes so that neither one is "less restrictive"?

Considering all of the data that the assignment process has to evaluate, I think that you'll find that it's a very complex process that goes mostly unnoticed. In my years here, I've seen a few bugs, and they generally get fixed without any public notice.