Moved up to 7.6.9: No WUs available for this configuration

[BertH]

Windows 10 Pro 64-bit i5-3470

Log appended at end of post.

Just moved up to 7.6.9 on my antique i5-3470 Win 10 system and now seeing numerous

Code: Select all

13:19:58:WU00:FS00:Connecting to 65.254.110.245:80
13:19:59:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:80': No WUs available for this configuration

Also very surprised to see

Code: Select all

13:19:57:OpenCL Device 1: Platform:0 Device:1 Bus:NA Slot:NA Compute:1.2 Driver:10.18
13:19:57:  Win32 Service: false

which was never there before.

Nonetheless, I DON'T have a GPU slot configured anyway.

But wait! As I was entering this message, I did get a task assigned and it appears to be running properly. Did it just take a few minutes for things to get settled in, or will there be some long-term problems?

Code: Select all

13:29:29:WU00:FS00:Connecting to 65.254.110.245:80
13:29:29:WU00:FS00:Assigned to work server 69.94.66.7
13:29:29:WU00:FS00:Requesting new work unit for slot 00: READY cpu:4 from 69.94.66.7
13:29:29:WU00:FS00:Connecting to 69.94.66.7:8080
13:29:31:WU00:FS00:Downloading 2.83MiB
13:29:33:WU00:FS00:Download complete
13:29:33:WU00:FS00:Received Unit: id:00 state:DOWNLOAD error:NO_ERROR project:14379 run:586 clone:3 gen:15 core:0xa7 unit:0x00000011455e42075e93309934dbf6ff

Log follows:

Code: Select all

*********************** Log Started 2020-04-22T13:19:57Z ***********************
13:19:57:****************************** FAHClient ******************************
13:19:57:        Version: 7.6.9
13:19:57:         Author: Joseph Coffland <joseph@cauldrondevelopment.com>
13:19:57:      Copyright: 2020 foldingathome.org
13:19:57:       Homepage: https://foldingathome.org/
13:19:57:           Date: Apr 17 2020
13:19:57:           Time: 11:13:06
13:19:57:       Revision: 398c2b17fa535e0cc6c9d10856b2154c32771646
13:19:57:         Branch: master
13:19:57:       Compiler: Visual C++ 2008
13:19:57:        Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
13:19:57:       Platform: win32 10
13:19:57:           Bits: 32
13:19:57:           Mode: Release
13:19:57:           Args: --open-web-control
13:19:57:         Config: C:\Users\rober\AppData\Roaming\FAHClient\config.xml
13:19:57:******************************** CBang ********************************
13:19:57:           Date: Apr 17 2020
13:19:57:           Time: 11:10:09
13:19:57:       Revision: 2fb0be7809c5e45287a122ca5fbc15b5ae859a3b
13:19:57:         Branch: master
13:19:57:       Compiler: Visual C++ 2008
13:19:57:        Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
13:19:57:       Platform: win32 10
13:19:57:           Bits: 32
13:19:57:           Mode: Release
13:19:57:******************************* System ********************************
13:19:57:            CPU: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz
13:19:57:         CPU ID: GenuineIntel Family 6 Model 58 Stepping 9
13:19:57:           CPUs: 4
13:19:57:         Memory: 7.90GiB
13:19:57:    Free Memory: 4.78GiB
13:19:57:        Threads: WINDOWS_THREADS
13:19:57:     OS Version: 6.2
13:19:57:    Has Battery: false
13:19:57:     On Battery: false
13:19:57:     UTC Offset: 0
13:19:57:            PID: 12696
13:19:57:            CWD: C:\Users\rober\AppData\Roaming\FAHClient
13:19:57:             OS: Windows 10 Enterprise
13:19:57:        OS Arch: AMD64
13:19:57:           GPUs: 0
13:19:57:           CUDA: Not detected: Failed to open dynamic library 'nvcuda.dll': The
13:19:57:                 specified module could not be found.
13:19:57:
13:19:57:OpenCL Device 1: Platform:0 Device:1 Bus:NA Slot:NA Compute:1.2 Driver:10.18
13:19:57:  Win32 Service: false
13:19:57:******************************* libFAH ********************************
13:19:57:           Date: Apr 15 2020
13:19:57:           Time: 14:53:14
13:19:57:       Revision: 216968bc7025029c841ed6e36e81a03a316890d3
13:19:57:         Branch: master
13:19:57:       Compiler: Visual C++ 2008
13:19:57:        Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
13:19:57:       Platform: win32 10
13:19:57:           Bits: 32
13:19:57:           Mode: Release
13:19:57:***********************************************************************
13:19:57:<config>
13:19:57:  <!-- Network -->
13:19:57:  <proxy v=':8080'/>
13:19:57:
13:19:57:  <!-- Slot Control -->
13:19:57:  <power v='FULL'/>
13:19:57:
13:19:57:  <!-- User Information -->
13:19:57:  <passkey v='*****'/>
13:19:57:  <team v='134653'/>
13:19:57:  <user v='Bert_Hyman'/>
13:19:57:
13:19:57:  <!-- Folding Slots -->
13:19:57:  <slot id='0' type='CPU'/>
13:19:57:</config>

[ajm]

The message "No WUs available for this configuration" appears when the server, answering the request of your client, doesn't have any job suitable for your computer. It is a very common occurrence these days (albeit not as much for CPU jobs), as FAH now has more donors' capacities than work and/or servers to distribute it. In such a case, your client will send new requests at increasing intervals.
Everything seems to be quite fine.

[JimboPalmer]

13:19:57:OpenCL Device 1: Platform:0 Device:1 Bus:NA Slot:NA Compute:1.2 Driver:10.18
Is an internal Intel GPU, F@H does not fold on Intel.

[Stel2112]

I see a lot of people asking about this. Maybe "WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:80': No WUs available for this configuration" should be worded a little clearer that this is not in fact a problem with the client?

Something like:

"WARNING:WU00:FS00:The server at '65.254.110.245:80' currently does not have work available (the client will keep trying until it does)."

[WTS]

I see a lot of people asking about this. Maybe "WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:80': No WUs available for this configuration" should be worded a little clearer that this is not in fact a problem with the client?

Something like:

"WARNING:WU00:FS00:The server at '65.254.110.245:80' currently does not have work available (the client will keep trying until it does)."

A very excellent suggestion! Most F@H users aren't experts in computers. This phrasing makes clear what is actually happening and would avoid
a _lot_ of confusion when confusion is the last thing we need.

[Neil-B]

Unfortunately it is not that simple .. That is just one of the "meanings" of the message you are seeing … and to be honest before the current overloads most folders would not have seen that message for years … Messages especially ones that are rarely used can tend towards generalisations and shorthand and cover a variety of possible issues/causes … Whilst I am sure when there is the opportunity to improve on some of these they will be - it may be the case that this message becomes redundant as any future recoding/re-architecture of the system happens having taken on board "lessons learnt" during the recent massive increase in compute resource/folders.

Traditionally most Folders were enthusiasts who where happy to dig around in the software/kit, search around forums for answers to questions … The recent increase has brought with it a very significant different set of mindsets and I have no doubt if this level of interest is sustained then improvements to many areas of the system including messaging will happen not least because it will hopefully sustain a greater level of development resource which has until now for the most part been the heroic efforts of very few individuals.

[WTS]

Unfortunately it is not that simple .. That is just one of the "meanings" of the message you are seeing … and to be honest before the current overloads most folders would not have seen that message for years … Messages especially ones that are rarely used can tend towards generalisations and shorthand and cover a variety of possible issues/causes … Whilst I am sure when there is the opportunity to improve on some of these they will be - it may be the case that this message becomes redundant as any future recoding/re-architecture of the system happens having taken on board "lessons learnt" during the recent massive increase in compute resource/folders.

Traditionally most Folders were enthusiasts who where happy to dig around in the software/kit, search around forums for answers to questions … The recent increase has brought with it a very significant different set of mindsets and I have no doubt if this level of interest is sustained then improvements to many areas of the system including messaging will happen not least because it will hopefully sustain a greater level of development resource which has until now for the most part been the heroic efforts of very few individuals.

Thanks. And thanks for the heroic efforts of those few scientists!!! When this Pandemic is over, I feel sure that F@H and its scientists will have made a major contribution to both the vaccine and the treatment. I hope and pray all of them stay safe and healthy during this crisis. Good scientists just don't grow on trees.

[DmitryKo]

Spent 5 hours today without WU assignment... looks like assignment servers are overloaded, and that's when my Radeon RX 5700 XT arrives next week

Code: Select all

19:02:20:WU00:FS01:Connecting to assign1.foldingathome.org:80
19:02:21:WARNING:WU00:FS01:Failed to get assignment from 'assign1.foldingathome.org:80': No WUs available for this configuration
19:02:21:WU00:FS01:Connecting to assign2.foldingathome.org:80
19:02:21:WARNING:WU00:FS01:Failed to get assignment from 'assign2.foldingathome.org:80': No WUs available for this configuration
19:02:21:WU00:FS01:Connecting to assign3.foldingathome.org:80
19:02:22:WARNING:WU00:FS01:Failed to get assignment from 'assign3.foldingathome.org:80': No WUs available for this configuration
19:02:22:WU00:FS01:Connecting to assign4.foldingathome.org:80
19:02:22:WU00:FS01:Assigned to work server 128.252.203.10
19:02:22:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:Baffin XT [Radeon RX 460] from 128.252.203.10
19:02:22:WU00:FS01:Connecting to 128.252.203.10:8080
19:02:36:ERROR:WU00:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0

19:03:57:WU00:FS01:Connecting to assign1.foldingathome.org:80
19:03:58:WARNING:WU00:FS01:Failed to get assignment from 'assign1.foldingathome.org:80': No WUs available for this configuration
19:03:58:WU00:FS01:Connecting to assign2.foldingathome.org:80
19:03:58:WARNING:WU00:FS01:Failed to get assignment from 'assign2.foldingathome.org:80': No WUs available for this configuration
19:03:58:WU00:FS01:Connecting to assign3.foldingathome.org:80
19:03:59:WARNING:WU00:FS01:Failed to get assignment from 'assign3.foldingathome.org:80': No WUs available for this configuration
19:03:59:WU00:FS01:Connecting to assign4.foldingathome.org:80
19:04:00:WARNING:WU00:FS01:Failed to get assignment from 'assign4.foldingathome.org:80': No WUs available for this configuration
19:04:00:ERROR:WU00:FS01:Exception: Could not get an assignment

[PaulMpls]

I've installed FAH on two clients about a week ago, one on Windows 10 and another on MacOS. I don't ever see the 'No WUs available for this configuration' on Windows, but that's all I see on Mac. I don't think my Mac client has processed any work since installing, but my Windows client has processed many (40+ wu's). Is it possible there is a configuration/installation issue with my Mac client that is causing this error?

[PantherX]

Welcome to the F@H Forum PaulMpls

...Is it possible there is a configuration/installation issue with my Mac client that is causing this error?

Can you please start a new topic in this Forum and post the log file for us to look into? Guidance on how to do that is provided here: viewtopic.php?f=108&t=26036

[PaulMpls]

Done - viewtopic.php?f=61&t=34859

Thanks