Hi, I am running this on my main laptop and this error keeps coming up saying the connection is online but inactive when it was perfectly working yesterday.
*********************** Log Started 2019-08-14T20:37:22Z ***********************
20:37:22:************************* Folding@home Client *************************
20:37:22: Website: https://foldingathome.org/
20:37:22: Copyright: (c) 2009-2018 foldingathome.org
20:37:22: Author: Joseph Coffland <[email protected]>
20:37:22: Args: --open-web-control
20:37:22: Config: C:\Users\jmck3\AppData\Roaming\FAHClient\config.xml
20:37:22:******************************** Build ********************************
20:37:22: Version: 7.5.1
20:37:22: Date: May 11 2018
20:37:22: Time: 13:06:32
20:37:22: Repository: Git
20:37:22: Revision: 4705bf53c635f88b8fe85af7675557e15d491ff0
20:37:22: Branch: master
20:37:22: Compiler: Visual C++ 2008
20:37:22: Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
20:37:22: Platform: win32 10
20:37:22: Bits: 32
20:37:22: Mode: Release
20:37:22:******************************* System ********************************
20:37:22: CPU: Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz
20:37:22: CPU ID: GenuineIntel Family 6 Model 69 Stepping 1
20:37:22: CPUs: 4
20:37:22: Memory: 7.91GiB
20:37:22: Free Memory: 2.12GiB
20:37:22: Threads: WINDOWS_THREADS
20:37:22: OS Version: 6.2
20:37:22: Has Battery: true
20:37:22: On Battery: false
20:37:22: UTC Offset: -4
20:37:22: PID: 12620
20:37:22: CWD: C:\Users\jmck3\AppData\Roaming\FAHClient
20:37:22: OS: Windows 10 Enterprise
20:37:22: OS Arch: AMD64
20:37:22: GPUs: 0
20:37:22: CUDA: Not detected: Failed to open dynamic library 'nvcuda.dll': The
20:37:22: specified module could not be found.
20:37:22:
20:37:22:OpenCL Device 0: Platform:0 Device:0 Bus:NA Slot:NA Compute:1.2 Driver:20.19
20:37:22: Win32 Service: false
20:37:22:***********************************************************************
20:37:22:<config>
20:37:22: <!-- Folding Slot Configuration -->
20:37:22: <cause v='ALZHEIMERS'/>
20:37:22:
20:37:22: <!-- Slot Control -->
20:37:22: <power v='medium'/>
20:37:22:
20:37:22: <!-- User Information -->
20:37:22: <passkey v='********************************'/>
20:37:22: <team v='234980'/>
20:37:22: <user v='qg927umi4cw1'/>
20:37:22:
20:37:22: <!-- Folding Slots -->
20:37:22: <slot id='0' type='CPU'/>
20:37:22:</config>
20:37:22:Trying to access database...
20:37:22:Successfully acquired database lock
20:37:22:Enabled folding slot 00: READY cpu:3
20:37:22:WU00:FS00:Connecting to 65.254.110.245:8080
20:37:23:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
20:37:23:WU00:FS00:Connecting to 18.218.241.186:80
20:37:23:WARNING:WU00:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
20:37:23:ERROR:WU00:FS00:Exception: Could not get an assignment
20:37:24:WU00:FS00:Connecting to 65.254.110.245:8080
20:37:24:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
20:37:24:WU00:FS00:Connecting to 18.218.241.186:80
20:37:24:WARNING:WU00:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
20:37:24:ERROR:WU00:FS00:Exception: Could not get an assignment
20:37:44:Saving configuration to config.xml
20:37:44:<config>
20:37:44: <!-- Folding Slot Configuration -->
20:37:44: <cause v='ALZHEIMERS'/>
20:37:44:
20:37:44: <!-- Network -->
20:37:44: <proxy v=':8080'/>
20:37:44:
20:37:44: <!-- Slot Control -->
20:37:44: <power v='medium'/>
20:37:44:
20:37:44: <!-- User Information -->
20:37:44: <passkey v='********************************'/>
20:37:44: <team v='234980'/>
20:37:44: <user v='qg927umi4cw1'/>
20:37:44:
20:37:44: <!-- Folding Slots -->
20:37:44: <slot id='0' type='CPU'/>
20:37:44:</config>
20:38:23:Saving configuration to config.xml
20:38:23:<config>
20:38:23: <!-- Folding Slot Configuration -->
20:38:23: <cause v='ALZHEIMERS'/>
20:38:23:
20:38:23: <!-- Network -->
20:38:23: <proxy v=':8080'/>
20:38:23:
20:38:23: <!-- Slot Control -->
20:38:23: <power v='medium'/>
20:38:23:
20:38:23: <!-- User Information -->
20:38:23: <passkey v='********************************'/>
20:38:23: <team v='234980'/>
20:38:23: <user v='qg927umi4cw1'/>
20:38:23:
20:38:23: <!-- Folding Slots -->
20:38:23: <slot id='0' type='CPU'/>
20:38:23:</config>
20:38:24:WU00:FS00:Connecting to 65.254.110.245:8080
20:38:24:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
20:38:24:WU00:FS00:Connecting to 18.218.241.186:80
20:38:24:WARNING:WU00:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
20:38:24:ERROR:WU00:FS00:Exception: Could not get an assignment
20:40:01:WU00:FS00:Connecting to 65.254.110.245:8080
20:40:01:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
20:40:01:WU00:FS00:Connecting to 18.218.241.186:80
20:40:01:WARNING:WU00:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
20:40:01:ERROR:WU00:FS00:Exception: Could not get an assignment
20:42:38:WU00:FS00:Connecting to 65.254.110.245:8080
20:42:38:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
20:42:38:WU00:FS00:Connecting to 18.218.241.186:80
20:42:38:WARNING:WU00:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
20:42:38:ERROR:WU00:FS00:Exception: Could not get an assignment
toTOW wrote:I guess there's no work for a 3 threads configuration ... try to set Folding Power slider to Full to request work for a 4 threads configuration.
Most of my CPU folders were stuck with this issue today (various number of threads per slot - 3 to 24). This happens occasionally, and the problem can usually be 'fixed' by deleting the slot and recreating it. Note that you may end up with an extra entry in the work queue from the slot you delete. Restarting the client usually purges that.
One key work server has been taken off-line temporarily. It has been making a large percentage of CPU assignments and the other servers with CPU projects are struggling to keep up. Temporarily there is a shortage of CPU assignments but there's nothing you can do about it but wait it out.
New projects are coming on-line on a regular basis ... moving from Beta to Advanced to full FAH does take some time. Severs are gradually being updated to new versions of the WS code and in most cases that takes many, many days because the server must be drained and then rebuilt. (If you happen to be the last person with a WU from the old server, you'll be thankful that they're waiting for you to return that WU for credit -- even though the rest of us are getting increasingly frustrated.)
My CPU slot is also stuck at, 'ready', however for some reason this situation is making my i7-4790 run hot and slow my machine to a crawl. Ubuntu 16.04.3. , client 7.3.6
Yes It's and old client version, but it's a long client reporting issue and I don't think pertinent to my current problem
Post your log file for the time period you see the client stuck at ready. Bruce's first post on this page has a link to directions to do that in his sig. Also useful is the first 100 or so lines of the log that show the system info and folding configuration.
Also, the output of top or another utility showing which processes are consuming CPU would more useful than the sar and mpstat info you have provided.
.
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
I have 2 systems that started failing/stalling folding after years of stable running (all aother applications continue to function). This is a sample folding log. Any help would be appreciated.
Thanks
Your distribution requires an update to be able to run A7 core. It's very likely a glibc incompatibility ... for instance, Ubuntu older than 16.04 won't be able to run A7 core.
If you try to run /home/me/smpv7/cores/cores.foldingathome.org/Linux/AMD64/Core_a7.fah/FahCore_a7 from a terminal, you'll have more details about the error.
Folding@Home beta tester since 2002. Folding Forum moderator since July 2008.
