Clueless as to why SMP can't get new WU...

[ADay2Long]

Waiting before retry.
[04:24:48] + Attempting to get work packet
[04:24:48] - Connecting to assignment server
[04:24:48] + No appropriate work server was available; will try again in a bit.
[04:24:48] + Couldn't get work instructions.
[04:24:48] - Attempt #4 to get work failed, and no other work to do.
Waiting before retry.

That's all I get over and over again on my 4 VMs. Anything I can do to fix it? It's been like this for the last 3+ days....

Thanks guys!

[Zero82z]

Shut down the client, delete queue.dat, and try again. The servers are up, so it's either a glitch or some kind of connection problem on your end. Also, if you're using Windows Firewall, make sure it isn't blocking F@H.

[ADay2Long]

sorry for my noobness...where can i find the queue.dat file?

[Zero82z]

In the directory that your F@H client is located in.

[_dangtx_]

yeah, if a reboot or so doesnt help.

[LCB001]

This post by Prof. Pande on his blog might be a reason you are having trouble getting WU's;

There have been some questions about the server status for Folding@home. The problem from the donor perspective is that the lack of WUs looks very similar to the servers being down -- the client reports it can't connect to the server. The servers have been up and in good shape since about Feb 25 (see the blog post on that day -- and that was just for the limited case of NVIDIA GPU servers, not FAH-wide). However, we have had a WU shortage now and again over the last week or so, which donors have mistaken as server reliability issues.
To fix this, we have been working to greatly increase the number of WUs, both for classic and SMP clients. There are a very large number of classic WUs that are coming out in new cores: the Protomol B4 core and the new Gromacs A4 core. B4 has rolled out and A4 is coming out in a week or so (maybe sooner). We also have new A3 SMP WUs in the pipeline. There have been some science issues that we have been working out on them.
Right now we are a bit too close, which leads to shortages for certain types of clients. My goal is to have way more WUs than we need so there are never any donor delays in getting WUs and we are pretty close to that, once the last few issues get worked out.

[sswilson]

Yep, same problem here on the one rig that's running a two core linux vmware. Probably going to switch that rig over to the new SMP2 client on my next days off now that I know the issues have been ironed out WRT playing nice in the sandbox with GPU clients.

I'm currently putting out somewhere around 6.5 - 7K PPD on my 955 @ 3.8 without any penalty to quad GPU client PPD so it appears that the initial glitches have been ironed out.

[Zero82z]

Originally Posted by sswilson

Yep, same problem here on the one rig that's running a two core linux vmware. Probably going to switch that rig over to the new SMP2 client on my next days off now that I know the issues have been ironed out WRT playing nice in the sandbox with GPU clients.

I'm currently putting out somewhere around 6.5 - 7K PPD on my 955 @ 3.8 without any penalty to quad GPU client PPD so it appears that the initial glitches have been ironed out.

Those issues have been gone since a few days after the SMP2 rollout when the 2.15 core was released to the public.