Can't download the next WU

[m_vokhm]

I'm completely new to the Folding@home so I may misunderstand something.
I've installed and run the client about 3 hours ago. It seems to have successfully downloaded and processed the first portion of data, but after finishing it and uploading the results it fails to start the next portion.
The log says:

Code: Select all

11:29:34:WU00:FS00:Sending unit results: id:00 state:SEND error:NO_ERROR project:13862 run:0 clone:355 gen:15 core:0xa7 unit:0x000000140d5a98395e764261702560f6
.......
11:31:40:WU00:FS00:Upload 98.08%
11:31:42:WU00:FS00:Upload complete
11:31:42:WU00:FS00:Server responded WORK_ACK (400)
11:31:42:WU00:FS00:Final credit estimate, 2156.00 points
11:31:42:WU00:FS00:Cleaning up
.......
11:59:35:WU01:FS00:Connecting to 65.254.110.245:8080
11:59:36:WU01:FS00:Assigned to work server 128.252.203.4
11:59:36:WU01:FS00:Requesting new work unit for slot 00: READY cpu:4 from 128.252.203.4
11:59:36:WU01:FS00:Connecting to 128.252.203.4:8080
11:59:37:ERROR:WU01:FS00:Exception: Server did not assign work unit
12:10:41:WU01:FS00:Connecting to 65.254.110.245:8080
12:10:41:WARNING:WU01:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
12:10:41:WU01:FS00:Connecting to 18.218.241.186:80
12:10:42:WARNING:WU01:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
12:10:42:ERROR:WU01:FS00:Exception: Could not get an assignment
12:28:37:WU01:FS00:Connecting to 65.254.110.245:8080
12:28:38:WARNING:WU01:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
12:28:38:WU01:FS00:Connecting to 18.218.241.186:80
12:28:39:WARNING:WU01:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
12:28:39:ERROR:WU01:FS00:Exception: Could not get an assignment

What's the reason of such a behavior?
Is there anything wrong with my client?
I don't think it pertains to my computer, but just in case it's
Windows 2008 R2 Standard,
Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz, 4 kernels, RAM 16 GB, no GPU.
Network connection Ethernet, 60 Mbit/s

[ajm]

When you have delivered a job, the client send a query for the next one, but you only get one if there is one available for your specific hardware, which is not always the case right now, as the servers are not able to generate enough jobs (WUs) for everybody. See: viewtopic.php?f=2&t=33193
Solutions are in the work and everyone hopes that it will get better soon. Until then, please be patient: your client will resume crunching automatically when jobs are available.

[m_vokhm]

I see. Thanks!

[m_vokhm]

Yet I can't comprehend the situation with the client. After restarting, it had downloaded and processed successfully a few WUs, and then it stopped again. It unsuccessfully tried to get an assignment several times, then seems like gave it up and had been standing idle for several hours or half a day, without even trying to get a new assignment. The log says

Code: Select all

08:52:54:WU00:FS00:Upload 98.62%
08:52:58:WU00:FS00:Upload complete
08:52:58:WU00:FS00:Server responded WORK_ACK (400)
08:52:58:WU00:FS00:Final credit estimate, 2154.00 points
08:52:58:WU00:FS00:Cleaning up
08:54:29:WU01:FS00:Connecting to 65.254.110.245:8080
08:54:30:WARNING:WU01:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
08:54:30:WU01:FS00:Connecting to 18.218.241.186:80
08:54:31:WARNING:WU01:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
08:54:31:ERROR:WU01:FS00:Exception: Could not get an assignment
08:58:43:WU01:FS00:Connecting to 65.254.110.245:8080
08:58:44:WARNING:WU01:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
08:58:44:WU01:FS00:Connecting to 18.218.241.186:80
08:58:47:WARNING:WU01:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
08:58:47:ERROR:WU01:FS00:Exception: Could not get an assignment
09:05:35:WU01:FS00:Connecting to 65.254.110.245:8080
09:05:36:WARNING:WU01:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
09:05:36:WU01:FS00:Connecting to 18.218.241.186:80

No new lines after the last one ("Connecting to 18.218.241.186:80") appeared for hours.
I saw no evidence of the client's activity.
After restarting it began to work normally at once.
This makes me doubt that the client can automatically get a new WU and continue working after having been waiting for WUs for several hours. How can I clear up this issue?

[Neil-B]

The client retries are programmed to get longer to not exacerbate the load issues on the server - the behaviour you describe is consistent with that ... Restarting the client restarts the retry timer - but an easier way is to pause the slot (or whole client if you only use one folding slot) wait for a minute or two (the log will should a batch of line showing a configuration refresh) the set the slot back to folding.

The team have ask people not to use the pause/folding too often (you can see the retry time in the advanced control - maybe do this when it gets over an hour) as it just makes the loading on the servers ... If you use the forum search function you will find many discussions and better/clearer explanations ... but the upshot is there are times when the severs are too overloaded to hand your system a WU and this is what you are seeing.

[m_vokhm]

I got it, thank you!