Folding Forum

Bruce,

I have been seeing a pattern of systems not able to get work for about a month now. Both for myself and for people like the OP of this thread. I have no choice but to believe there is some anomalous bug in the Assignment Server.

My system that got stuck today is an Intel quad core running Client v6.34 on Windows 7 Ultimate 32-bit. The machine is not overclocked and has been Folding for months without issues.
I have a dozen other Folding machines at the same location that did not have the "No appropriate work server was available" issue today so I have to assume that it is not a network problem on my end.
I have the size of work units set to 'big', assigned 1800MB of memory to Folding, have set the -advmethods and -smp flags. This system is just using the Microsoft firewall along with AVG Free 2013. And if it helps diagnostically, I am located in NY.

The machine had just completed and sent back Project 6981 (using the a3 core) when it got 'stuck' for most of an hour with the "No appropriate work server was available" error. After running the Fix listed below, I restarted the client and got Project 6973 - also an a3 core work unit.


For anyone having this specific problem, the fix I found has worked for me 100% of the time.

First I make sure that I have shut down Folding - in my case CTRL+C to close the DOS window.

Find your FAH folder and Delete the unitinfo.txt, the queue.dat and the work folder.

Restart Folding.


Perhaps we can start to figure out if any one of the above listed specs match a majority of the people having the " No appropriate work server was available" issue?

There is no need to configure a memory setting. Please remove it. It will only limit your WU assignments and provide no benefit.

7im wrote:There is no need to configure a memory setting. Please remove it. It will only limit your WU assignments and provide no benefit.

Uhm, and how are you going to accomplish this, without deleting the config-file, or manually edit it with the possibility of screwing-up something?

bruce wrote:

artoar_11 wrote:Can anyone give an explanation why this is happening?

The Assignment Server is searching for any Work Server that has WUs that fit your requirements.

From your end, the requirements include OS, Hardware, Client(slot)-type, Proxy/firewall settings, Parameters which express donor requests, etc. as well as all of the information shown on the serverstat page. Without ALL of that information, there's no obvious answer.

You can answer your own question if you can explain to me how your system is different from other similar systems which are getting assignments.

Do you see a work server that has assignments that match your request?

The problem is not in the network. Both computers are in the office. Two adjacent computers on a common switch. When the (1) PC already had this problem, the (2) PC receives/return WUs.
The first time I messed up in this situation. I thought that the problem is with the server - 128.143.199.96. A few days later the same problem came on the second computer.

As wrote Gary480six:

First I make sure that I have shut down Folding - in my case CTRL+C to close the DOS window.

Find your FAH folder and Delete the unitinfo.txt, the queue.dat and the work folder.

Restart Folding.

File client.cfg no need to change in this situation.

Only my assumption:
This happens immediately after the successful return of the WU. In some file I guess something changed (or deletes, removes in this moment), then the client fails to download a new WU.

Rattledagger wrote:

7im wrote:There is no need to configure a memory setting. Please remove it. It will only limit your WU assignments and provide no benefit.

Uhm, and how are you going to accomplish this, without deleting the config-file, or manually edit it with the possibility of screwing-up something?

RTFah v6 install guide. The -config or -configonly switches work well for updating the client settings without manually editing the config file.