Client not respecting "On Idle" Setting

Moderators: Site Moderators, FAHC Science Team

Client not respecting "On Idle" Setting

Postby wvdude » Sun Apr 12, 2020 9:54 pm

Hello - I have three systems running FAH and just installed it on a fresh new Win 10 Pro system. Nothing to call home to mom about, but figured I'd like to do something with the idle CPU time. Anyways, I have installed eveything just as I have with my other computers and this one does not stop processing when I am using the computer and it is driving me crazy.

I uninstalled and reinstalled twice, once using a 3rd party uninstall app with no luck. Any ideas? Thanks for your help!

My most recent log is below:

Thanks for your help!

Code: Select all
*********************** Log Started 2020-04-12T18:24:49Z ***********************
18:24:49:************************* Folding@home Client *************************
18:24:49:        Website: https://foldingathome.org/
18:24:49:      Copyright: (c) 2009-2018 foldingathome.org
18:24:49:         Author: Joseph Coffland <joseph@cauldrondevelopment.com>
18:24:49:           Args: --open-web-control
18:24:49:         Config: <none>
18:24:49:******************************** Build ********************************
18:24:49:        Version: 7.5.1
18:24:49:           Date: May 11 2018
18:24:49:           Time: 13:06:32
18:24:49:     Repository: Git
18:24:49:       Revision: 4705bf53c635f88b8fe85af7675557e15d491ff0
18:24:49:         Branch: master
18:24:49:       Compiler: Visual C++ 2008
18:24:49:        Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
18:24:49:       Platform: win32 10
18:24:49:           Bits: 32
18:24:49:           Mode: Release
18:24:49:******************************* System ********************************
18:24:49:            CPU: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz
18:24:49:         CPU ID: GenuineIntel Family 6 Model 60 Stepping 3
18:24:49:           CPUs: 4
18:24:49:         Memory: 7.91GiB
18:24:49:    Free Memory: 4.51GiB
18:24:49:        Threads: WINDOWS_THREADS
18:24:49:     OS Version: 6.2
18:24:49:    Has Battery: false
18:24:49:     On Battery: false
18:24:49:     UTC Offset: -4
18:24:49:            PID: 9516
18:24:49:            CWD: C:\Users\karl\AppData\Roaming\FAHClient
18:24:49:             OS: Windows 10 Enterprise
18:24:49:        OS Arch: AMD64
18:24:49:           GPUs: 0
18:24:49:           CUDA: Not detected: Failed to open dynamic library 'nvcuda.dll': The
18:24:49:                 specified module could not be found.
18:24:49:
18:24:49:OpenCL Device 0: Platform:0 Device:0 Bus:NA Slot:NA Compute:1.2 Driver:20.19
18:24:49:  Win32 Service: false
18:24:49:***********************************************************************
18:24:49:<config>
18:24:49:  <!-- Folding Slots -->
18:24:49:</config>
18:24:49:Connecting to assign1.foldingathome.org:8080
18:24:49:Updated GPUs.txt
18:24:49:Read GPUs.txt
18:24:49:Trying to access database...
18:24:50:Successfully acquired database lock
18:24:50:Enabled folding slot 00: PAUSED cpu:3 (not configured)
18:24:52:12:127.0.0.1:New Web connection
18:25:51:Saving configuration to config.xml
18:25:51:<config>
18:25:51:  <!-- Folding Slots -->
18:25:51:  <slot id='0' type='CPU'/>
18:25:51:</config>
18:25:51:Set client configured
18:25:51:WU00:FS00:Connecting to 65.254.110.245:8080
18:25:51:WU00:FS00:Connecting to 65.254.110.245:8080
18:25:51:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
18:25:51:WU00:FS00:Connecting to 18.218.241.186:80
18:25:51:WU00:FS00:Assigned to work server 13.90.152.57
18:25:51:WU00:FS00:Requesting new work unit for slot 00: READY cpu:3 from 13.90.152.57
18:25:51:WU00:FS00:Connecting to 13.90.152.57:8080
18:25:51:ERROR:WU00:FS00:Exception: Server did not assign work unit
18:25:51:WU00:FS00:Connecting to 65.254.110.245:8080
18:25:52:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
18:25:52:WU00:FS00:Connecting to 18.218.241.186:80
18:25:52:WARNING:WU00:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
18:25:52:ERROR:WU00:FS00:Exception: Could not get an assignment
18:26:52:Saving configuration to config.xml
18:26:52:<config>
18:26:52:  <!-- Slot Control -->
18:26:52:  <power v='FULL'/>
18:26:52:
18:26:52:  <!-- User Information -->
18:26:52:  <passkey v='********************************'/>
18:26:52:  <team v='50959'/>
18:26:52:  <user v='wvdude'/>
18:26:52:
18:26:52:  <!-- Folding Slots -->
18:26:52:  <slot id='0' type='CPU'>
18:26:52:    <idle v='true'/>
18:26:52:  </slot>
18:26:52:</config>
18:37:12:WU00:FS00:Connecting to 65.254.110.245:8080
18:37:13:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
18:37:13:WU00:FS00:Connecting to 18.218.241.186:80
18:37:13:WARNING:WU00:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
18:37:13:ERROR:WU00:FS00:Exception: Could not get an assignment
18:38:50:WU00:FS00:Connecting to 65.254.110.245:8080
18:38:50:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
18:38:50:WU00:FS00:Connecting to 18.218.241.186:80
18:38:50:WARNING:WU00:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
18:38:50:ERROR:WU00:FS00:Exception: Could not get an assignment
18:41:27:WU00:FS00:Connecting to 65.254.110.245:8080
18:41:27:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
18:41:27:WU00:FS00:Connecting to 18.218.241.186:80
18:41:27:WARNING:WU00:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
18:41:27:ERROR:WU00:FS00:Exception: Could not get an assignment
18:45:41:WU00:FS00:Connecting to 65.254.110.245:8080
18:45:41:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
18:45:41:WU00:FS00:Connecting to 18.218.241.186:80
18:45:41:WARNING:WU00:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
18:45:41:ERROR:WU00:FS00:Exception: Could not get an assignment
18:52:32:WU00:FS00:Connecting to 65.254.110.245:8080
18:52:32:WU00:FS00:Assigned to work server 155.247.164.214
18:52:32:WU00:FS00:Requesting new work unit for slot 00: READY cpu:4 from 155.247.164.214
18:52:32:WU00:FS00:Connecting to 155.247.164.214:8080
18:52:33:WU00:FS00:Downloading 2.98MiB
18:52:33:WU00:FS00:Download complete
18:52:34:WU00:FS00:Received Unit: id:00 state:DOWNLOAD error:NO_ERROR project:14601 run:29 clone:4 gen:59 core:0xa7 unit:0x000000419bf7a4d65e7b5764cd2fe9fe
18:52:34:WU00:FS00:Downloading core from http://cores.foldingathome.org/v7/win/64bit/avx/Core_a7.fah
18:52:34:WU00:FS00:Connecting to cores.foldingathome.org:80
18:52:34:WU00:FS00:FahCore a7: Downloading 6.71MiB
18:52:35:WU00:FS00:FahCore a7: Download complete
18:52:35:WU00:FS00:Valid core signature
18:52:35:WU00:FS00:Unpacked 19.85MiB to cores/cores.foldingathome.org/v7/win/64bit/avx/Core_a7.fah/FahCore_a7.exe
18:52:35:WU00:FS00:Unpacked 2.64MiB to cores/cores.foldingathome.org/v7/win/64bit/avx/Core_a7.fah/libfftw3f-3.dll
18:52:35:WU00:FS00:Starting
18:52:35:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\Users\karl\AppData\Roaming\FAHClient\cores/cores.foldingathome.org/v7/win/64bit/avx/Core_a7.fah/FahCore_a7.exe -dir 00 -suffix 01 -version 705 -lifeline 9516 -checkpoint 15 -np 4
18:52:35:WU00:FS00:Started FahCore on PID 3092
18:52:36:WU00:FS00:Core PID:5548
18:52:36:WU00:FS00:FahCore 0xa7 started
18:52:37:WU00:FS00:0xa7:*********************** Log Started 2020-04-12T18:52:36Z ***********************
18:52:37:WU00:FS00:0xa7:************************** Gromacs Folding@home Core ***************************
18:52:37:WU00:FS00:0xa7:       Type: 0xa7
18:52:37:WU00:FS00:0xa7:       Core: Gromacs
18:52:37:WU00:FS00:0xa7:       Args: -dir 00 -suffix 01 -version 705 -lifeline 3092 -checkpoint 15 -np 4
18:52:37:WU00:FS00:0xa7:************************************ CBang *************************************
18:52:37:WU00:FS00:0xa7:       Date: Oct 26 2019
18:52:37:WU00:FS00:0xa7:       Time: 01:38:25
18:52:37:WU00:FS00:0xa7:   Revision: c46a1a011a24143739ac7218c5a435f66777f62f
18:52:37:WU00:FS00:0xa7:     Branch: master
18:52:37:WU00:FS00:0xa7:   Compiler: Visual C++ 2008
18:52:37:WU00:FS00:0xa7:    Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
18:52:37:WU00:FS00:0xa7:   Platform: win32 10
18:52:37:WU00:FS00:0xa7:       Bits: 64
18:52:37:WU00:FS00:0xa7:       Mode: Release
18:52:37:WU00:FS00:0xa7:************************************ System ************************************
18:52:37:WU00:FS00:0xa7:        CPU: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz
18:52:37:WU00:FS00:0xa7:     CPU ID: GenuineIntel Family 6 Model 60 Stepping 3
18:52:37:WU00:FS00:0xa7:       CPUs: 4
18:52:37:WU00:FS00:0xa7:     Memory: 7.91GiB
18:52:37:WU00:FS00:0xa7:Free Memory: 5.06GiB
18:52:37:WU00:FS00:0xa7:    Threads: WINDOWS_THREADS
18:52:37:WU00:FS00:0xa7: OS Version: 6.2
18:52:37:WU00:FS00:0xa7:Has Battery: false
18:52:37:WU00:FS00:0xa7: On Battery: false
18:52:37:WU00:FS00:0xa7: UTC Offset: -4
18:52:37:WU00:FS00:0xa7:        PID: 5548
18:52:37:WU00:FS00:0xa7:        CWD: C:\Users\karl\AppData\Roaming\FAHClient\work
18:52:37:WU00:FS00:0xa7:******************************** Build - libFAH ********************************
18:52:37:WU00:FS00:0xa7:    Version: 0.0.18
18:52:37:WU00:FS00:0xa7:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
18:52:37:WU00:FS00:0xa7:  Copyright: 2019 foldingathome.org
18:52:37:WU00:FS00:0xa7:   Homepage: https://foldingathome.org/
18:52:37:WU00:FS00:0xa7:       Date: Oct 26 2019
18:52:37:WU00:FS00:0xa7:       Time: 01:52:30
18:52:37:WU00:FS00:0xa7:   Revision: c1e3513b1bc0c16013668f2173ee969e5995b38e
18:52:37:WU00:FS00:0xa7:     Branch: master
18:52:37:WU00:FS00:0xa7:   Compiler: Visual C++ 2008
18:52:37:WU00:FS00:0xa7:    Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
18:52:37:WU00:FS00:0xa7:   Platform: win32 10
18:52:37:WU00:FS00:0xa7:       Bits: 64
18:52:37:WU00:FS00:0xa7:       Mode: Release
18:52:37:WU00:FS00:0xa7:************************************ Build *************************************
18:52:37:WU00:FS00:0xa7:       SIMD: avx_256
18:52:37:WU00:FS00:0xa7:********************************************************************************
18:52:37:WU00:FS00:0xa7:Project: 14601 (Run 29, Clone 4, Gen 59)
18:52:37:WU00:FS00:0xa7:Unit: 0x000000419bf7a4d65e7b5764cd2fe9fe
18:52:37:WU00:FS00:0xa7:Reading tar file core.xml
18:52:37:WU00:FS00:0xa7:Reading tar file frame59.tpr
18:52:37:WU00:FS00:0xa7:Digital signatures verified
18:52:37:WU00:FS00:0xa7:Calling: mdrun -s frame59.tpr -o frame59.trr -cpt 15 -nt 4
18:52:37:WU00:FS00:0xa7:Steps: first=0 total=250000
18:52:38:WU00:FS00:0xa7:Completed 1 out of 250000 steps (0%)
18:55:14:WU00:FS00:0xa7:Completed 2500 out of 250000 steps (1%)
18:57:48:WU00:FS00:0xa7:Completed 5000 out of 250000 steps (2%)
19:00:22:WU00:FS00:0xa7:Completed 7500 out of 250000 steps (3%)
19:02:57:WU00:FS00:0xa7:Completed 10000 out of 250000 steps (4%)
19:05:31:WU00:FS00:0xa7:Completed 12500 out of 250000 steps (5%)
19:08:05:WU00:FS00:0xa7:Completed 15000 out of 250000 steps (6%)
19:10:39:WU00:FS00:0xa7:Completed 17500 out of 250000 steps (7%)
19:13:13:WU00:FS00:0xa7:Completed 20000 out of 250000 steps (8%)
19:15:48:WU00:FS00:0xa7:Completed 22500 out of 250000 steps (9%)
19:18:22:WU00:FS00:0xa7:Completed 25000 out of 250000 steps (10%)
19:20:56:WU00:FS00:0xa7:Completed 27500 out of 250000 steps (11%)
19:23:31:WU00:FS00:0xa7:Completed 30000 out of 250000 steps (12%)
19:26:05:WU00:FS00:0xa7:Completed 32500 out of 250000 steps (13%)
19:28:39:WU00:FS00:0xa7:Completed 35000 out of 250000 steps (14%)
19:31:14:WU00:FS00:0xa7:Completed 37500 out of 250000 steps (15%)
19:33:48:WU00:FS00:0xa7:Completed 40000 out of 250000 steps (16%)
19:36:22:WU00:FS00:0xa7:Completed 42500 out of 250000 steps (17%)
19:38:57:WU00:FS00:0xa7:Completed 45000 out of 250000 steps (18%)
19:41:32:WU00:FS00:0xa7:Completed 47500 out of 250000 steps (19%)
19:44:06:WU00:FS00:0xa7:Completed 50000 out of 250000 steps (20%)
19:46:42:WU00:FS00:0xa7:Completed 52500 out of 250000 steps (21%)
19:49:19:WU00:FS00:0xa7:Completed 55000 out of 250000 steps (22%)
19:51:55:WU00:FS00:0xa7:Completed 57500 out of 250000 steps (23%)
19:54:32:WU00:FS00:0xa7:Completed 60000 out of 250000 steps (24%)
19:57:08:WU00:FS00:0xa7:Completed 62500 out of 250000 steps (25%)
19:59:44:WU00:FS00:0xa7:Completed 65000 out of 250000 steps (26%)
20:02:22:WU00:FS00:0xa7:Completed 67500 out of 250000 steps (27%)
20:05:00:WU00:FS00:0xa7:Completed 70000 out of 250000 steps (28%)
20:07:37:WU00:FS00:0xa7:Completed 72500 out of 250000 steps (29%)
20:10:15:WU00:FS00:0xa7:Completed 75000 out of 250000 steps (30%)
20:12:52:WU00:FS00:0xa7:Completed 77500 out of 250000 steps (31%)
20:15:29:WU00:FS00:0xa7:Completed 80000 out of 250000 steps (32%)
20:18:05:WU00:FS00:0xa7:Completed 82500 out of 250000 steps (33%)
20:20:41:WU00:FS00:0xa7:Completed 85000 out of 250000 steps (34%)
20:23:17:WU00:FS00:0xa7:Completed 87500 out of 250000 steps (35%)
20:25:52:WU00:FS00:0xa7:Completed 90000 out of 250000 steps (36%)
20:28:26:WU00:FS00:0xa7:Completed 92500 out of 250000 steps (37%)
20:31:02:WU00:FS00:0xa7:Completed 95000 out of 250000 steps (38%)
20:33:37:WU00:FS00:0xa7:Completed 97500 out of 250000 steps (39%)
20:35:05:59:127.0.0.1:New Web connection
20:36:29:WU00:FS00:0xa7:Completed 100000 out of 250000 steps (40%)
20:39:20:WU00:FS00:0xa7:Completed 102500 out of 250000 steps (41%)
20:42:10:WU00:FS00:0xa7:Completed 105000 out of 250000 steps (42%)
20:45:06:WU00:FS00:0xa7:Completed 107500 out of 250000 steps (43%)
20:48:00:WU00:FS00:0xa7:Completed 110000 out of 250000 steps (44%)
20:50:51:WU00:FS00:0xa7:Completed 112500 out of 250000 steps (45%)
wvdude
 
Posts: 2
Joined: Sun Apr 12, 2020 9:42 pm

Re: Client not respecting "On Idle" Setting

Postby PantherX » Sun Apr 12, 2020 11:04 pm

Welcome to the F@H Forum wvdude,

Please note that the client uses the OS to detect if it is idle or not. For Windows, it is when the screensaver is running. May I suggest that you reboot your system and see what the behavior is? Please post the fresh log after the system reboot (please avoid the Shutdown and then power up method as it isn't the same as restarting your system https://www.howtogeek.com/349114/shutti ... g-it-does/).
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time

Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
User avatar
PantherX
Site Moderator
 
Posts: 6323
Joined: Wed Dec 23, 2009 10:33 am
Location: Land Of The Long White Cloud

Re: Client not respecting "On Idle" Setting

Postby wvdude » Mon Apr 13, 2020 3:19 am

@PantherX - thanks so much for your reply! I think it is working now but will update if it seems to occur again. I've been restarting rather than shutdown anyways and thought that it may have had something to do with the fact that this particular computer has no display and I access it with remote desktop, but a simple restart appears to have worked.
wvdude
 
Posts: 2
Joined: Sun Apr 12, 2020 9:42 pm

Re: Client not respecting "On Idle" Setting

Postby jedcred » Fri Apr 17, 2020 9:20 pm

I'm having a similar issue on Fedora 31 under Gnome 3.34.5. What determines idle on a Linux machine? Things I've tried so far:

* up the logging verbosity to 5 to see if any attempts to go into idle fail, but I don't see any logs to that effect
* increase the priority of F@H with the "Folding Core Priority" setting
* restart the client
* restart the machine

My config is two GPU slots where the second GPU (not connected to my display) is running all the time, and I would prefer the GPU slot connected to the display to only work on idle, since it causes desktop performance degradation (understandably).

Is it an issue with there needing to be the gnome-screensaver or xscreensaver package installed? It seems that gnome no longer offers a screensaver and just blanks the screen after an interval.
jedcred
 
Posts: 2
Joined: Fri Apr 17, 2020 9:15 pm

Re: Client not respecting "On Idle" Setting

Postby Neil-B » Fri Apr 17, 2020 9:51 pm

This may get you in the right direction … https://foldingforum.org/viewtopic.php?f=106&t=34092&hilit=system+idle+linux#p323575 … It seems to confirm it might be your last sentence? … Hopefully someone who is a Linux guru can assist more than I can.

… and Verbosity 5 won't help anyone troubleshoot your logs - backing it back to 3 might be worth it for future.
1: 2x Xeon E5-2697v3@2.60GHz, 512GB DDR4 LRDIMM, SSD Raid, Win10 Ent, Quadro K420 1GB, FAH 7.6.13
2: Xeon E3-1505Mv5@2.80GHz, 32GB DDR4, NVME, Win10 Pro, Quadro M1000M 2GB, FAH 7.6.13
3: i7-960@3.20GHz, 12GB DDR3, SSD, Win10 Pro, GTX 750Ti 2GB, FAH 7.6.13
Neil-B
 
Posts: 1180
Joined: Sun Mar 22, 2020 6:52 pm
Location: UK

Re: Client not respecting "On Idle" Setting

Postby jedcred » Sun Apr 19, 2020 5:44 am

I poked around the FAHClient and found I can send pause and unpause events to a running instance on lock/unlock events in dbus. Wrapped it up in this script, which monitors dbus with gdbus, filters for events with the string "LockedHint," and unpauses when lock is "<true>" and pauses when lock is "<false>". You can run it by passing the string corresponding to the slot you want to pause and unpause, which in my instance is "02". If the script is saved in a file called fah_monitor.sh you may run it like so:

Code: Select all
./fah_monitor.sh "01"


Code: Select all
#!/bin/bash

if [ -z "$1" ]
then
   echo 'Must pass the slot number e.g. "01"'
   exit 1
fi

gdbus monitor -y -d org.freedesktop.login1 | grep "LockedHint" --line-buffered |
    while read line
    do
        case "$line" in
            *"<true>"*)
                echo "unpausing slot $1"
                FAHClient --send-unpause "$1"
            ;;
            *"<false>"*)
                echo "pausing slot $1"
                FAHClient --send-pause "$1"
            ;;
        esac
    done
jedcred
 
Posts: 2
Joined: Fri Apr 17, 2020 9:15 pm


Return to V7.5.1 Public Release Windows/Linux/MacOS X

Who is online

Users browsing this forum: No registered users and 1 guest

cron