Folding Forum

Community driven support forum for Folding@home
https://foldingforum.org/

Ability to abort/cancel a workunit?

https://foldingforum.org/viewtopic.php?t=37755

Page 2 of 4

Re: Ability to abort/cancel a workunit?

Posted: Fri Feb 18, 2022 5:07 pm
by aetch
I'm done.

Your computers are fine but you want to dump work units because they take too long.
You want the client to do things it's not designed to do.
We try to help you, all we get is pushback.

Re: Ability to abort/cancel a workunit?

Posted: Fri Feb 18, 2022 5:22 pm
by Neil-B
@Peter_Hucker ... If you feel that way then maybe tbh using Boinc might reduce stress levels? ... FaH software is what it is - for many it works perfectly well and allows folders to contribute effortlessly, but it does have known limitations that are being worked on ... Setup can be a challenge, various OS and legacy software issues can make certain kit combinations hard to configure and some pretty much impossible ... Individual donors are obviously at liberty to decide whether the effort required to maintain their setups is worth it - some do and some decide it is too much effort ... FaH is working on improving and updating the user experience but for now it simply is what it is ... Support in these forums is from volunteer folders who try to assist new/other folders as/where they can.

Re: Ability to abort/cancel a workunit?

Posted: Sat Feb 19, 2022 9:15 am
by Peter_Hucker
aetch wrote:I'm done.

Your computers are fine but you want to dump work units because they take too long.
You want the client to do things it's not designed to do.
We try to help you, all we get is pushback.
Excuse me? I don't understand your attitude. I'm trying to run FAH on several computers, and some are not able to complete the workunits in time. There is no way this is my or my computer's fault. I'm being sent workunits that are too long for the power of the processors. One of you has already told me the server is supposed to know how fast each CPU model is and send out an appropriately sized workunit. This is clearly not happening. Here's a log from my slowest machine, and it will take just over 2 days to complete a workunit with a 1 day deadline. I should not have been given this workunit. Something needs to be fixed at the FAH end.

Code: Select all

*********************** Log Started 2022-02-19T06:12:46Z ***********************
06:12:46:******************************* libFAH ********************************
06:12:46:           Date: Oct 20 2020
06:12:46:           Time: 13:36:55
06:12:46:       Revision: 5ca109d295a6245e2a2f590b3d0085ad5e567aeb
06:12:46:         Branch: master
06:12:46:       Compiler: Visual C++ 2015
06:12:46:        Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
06:12:46:       Platform: win32 10
06:12:46:           Bits: 32
06:12:46:           Mode: Release
06:12:46:****************************** FAHClient ******************************
06:12:46:        Version: 7.6.21
06:12:46:         Author: Joseph Coffland <joseph@cauldrondevelopment.com>
06:12:46:      Copyright: 2020 foldingathome.org
06:12:46:       Homepage: https://foldingathome.org/
06:12:46:           Date: Oct 20 2020
06:12:46:           Time: 13:41:04
06:12:46:       Revision: 6efbf0e138e22d3963e6a291f78dcb9c6422a278
06:12:46:         Branch: master
06:12:46:       Compiler: Visual C++ 2015
06:12:46:        Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
06:12:46:       Platform: win32 10
06:12:46:           Bits: 32
06:12:46:           Mode: Release
06:12:46:           Args: --open-web-control
06:12:46:******************************** CBang ********************************
06:12:46:           Date: Oct 20 2020
06:12:46:           Time: 11:36:18
06:12:46:       Revision: 7e4ce85225d7eaeb775e87c31740181ca603de60
06:12:46:         Branch: master
06:12:46:       Compiler: Visual C++ 2015
06:12:46:        Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
06:12:46:       Platform: win32 10
06:12:46:           Bits: 32
06:12:46:           Mode: Release
06:12:46:******************************* System ********************************
06:12:46:            CPU: Intel(R) Pentium(R) CPU N3700 @ 1.60GHz
06:12:46:         CPU ID: GenuineIntel Family 6 Model 76 Stepping 3
06:12:46:           CPUs: 4
06:12:46:         Memory: 7.92GiB
06:12:46:    Free Memory: 4.24GiB
06:12:46:        Threads: WINDOWS_THREADS
06:12:46:     OS Version: 6.2
06:12:46:    Has Battery: false
06:12:46:     On Battery: false
06:12:46:     UTC Offset: 0
06:12:46:            PID: 1844
06:12:46:            CWD: C:\ProgramData\FAHClient
06:12:46:  Win32 Service: false
06:12:46:             OS: Windows 10 Home
06:12:46:        OS Arch: AMD64
06:12:46:           GPUs: 1
06:12:46:          GPU 0: Bus:1 Slot:0 Func:0 AMD:5 Tahiti XT [Radeon R9 200/HD
06:12:46:                 7900/8970]
06:12:46:           CUDA: Not detected: Failed to open dynamic library 'nvcuda.dll': The
06:12:46:                 specified module could not be found.
06:12:46:
06:12:46:OpenCL Device 0: Platform:0 Device:0 Bus:1 Slot:0 Compute:1.2 Driver:3240.6
06:12:46:***********************************************************************
06:12:46:<config>
06:12:46:  <!-- Folding Slots -->
06:12:46:</config>
06:12:46:Trying to access database...
06:12:46:Successfully acquired database lock
06:12:46:FS00:Initialized folding slot 00: cpu:2
06:12:46:FS01:Initialized folding slot 01: gpu:1:0 Tahiti XT [Radeon R9 200/HD 7900/8970]
06:13:15:3:127.0.0.1:New Web session
06:13:47:Saving configuration to config.xml
06:13:47:<config>
06:13:47:  <!-- Folding Slots -->
06:13:47:  <slot id='0' type='CPU'/>
06:13:47:  <slot id='1' type='GPU'>
06:13:47:    <pci-bus v='1'/>
06:13:47:    <pci-slot v='0'/>
06:13:47:  </slot>
06:13:47:</config>
06:13:47:Set client configured
06:13:47:WU00:FS00:Connecting to assign1.foldingathome.org:80
06:13:47:WU01:FS01:Connecting to assign1.foldingathome.org:80
06:13:48:WU00:FS00:Connecting to assign1.foldingathome.org:80
06:13:48:WU01:FS01:Connecting to assign1.foldingathome.org:80
06:13:48:WU01:FS01:Assigned to work server 34.72.228.44
06:13:48:WU01:FS01:Requesting new work unit for slot 01: gpu:1:0 Tahiti XT [Radeon R9 200/HD 7900/8970] from 34.72.228.44
06:13:48:WU00:FS00:Assigned to work server 128.252.203.2
06:13:48:WU01:FS01:Connecting to 34.72.228.44:8080
06:13:48:WU00:FS00:Requesting new work unit for slot 00: cpu:2 from 128.252.203.2
06:13:48:WU00:FS00:Connecting to 128.252.203.2:8080
06:13:48:WU00:FS00:Downloading 3.24MiB
06:13:48:WU01:FS01:Downloading 8.26MiB
06:13:51:WU00:FS00:Download complete
06:13:51:WU00:FS00:Received Unit: id:00 state:DOWNLOAD error:NO_ERROR project:17255 run:2342 clone:2 gen:16 core:0xa8 unit:0x00000002000000100000436700000926
06:13:51:WU00:FS00:Downloading core from http://cores.foldingathome.org/win/64bit-sse2/a8-0.0.12/Core_a8.fah
06:13:51:WU00:FS00:Connecting to cores.foldingathome.org:80
06:13:51:WU00:FS00:FahCore a8: Downloading 7.44MiB
06:13:54:WU01:FS01:Download 72.60%
06:13:57:WU00:FS00:FahCore a8: 97.43%
06:13:57:WU00:FS00:FahCore a8: Download complete
06:13:57:WU00:FS00:Valid core signature
06:13:57:WU00:FS00:Unpacked 19.33MiB to cores/cores.foldingathome.org/win/64bit-sse2/a8-0.0.12/Core_a8.fah/FahCore_a8.exe
06:13:57:WU00:FS00:Unpacked 2.64MiB to cores/cores.foldingathome.org/win/64bit-sse2/a8-0.0.12/Core_a8.fah/libfftw3f-3.dll
06:13:57:WU00:FS00:Unpacked 172.88KiB to cores/cores.foldingathome.org/win/64bit-sse2/a8-0.0.12/Core_a8.fah/vcomp140.dll
06:13:57:WU00:FS00:Starting
06:13:57:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\ProgramData\FAHClient\cores/cores.foldingathome.org/win/64bit-sse2/a8-0.0.12/Core_a8.fah/FahCore_a8.exe -dir 00 -suffix 01 -version 706 -lifeline 1844 -checkpoint 15 -np 2
06:13:58:WU01:FS01:Download complete
06:13:58:WU00:FS00:Started FahCore on PID 36072
06:14:00:WU00:FS00:Core PID:64528
06:14:00:WU00:FS00:FahCore 0xa8 started
06:14:00:WU00:FS00:0xa8:*********************** Log Started 2022-02-19T06:14:00Z ***********************
06:14:00:WU00:FS00:0xa8:************************** Gromacs Folding@home Core ***************************
06:14:00:WU00:FS00:0xa8:       Core: Gromacs
06:14:00:WU00:FS00:0xa8:       Type: 0xa8
06:14:00:WU00:FS00:0xa8:    Version: 0.0.12
06:14:00:WU00:FS00:0xa8:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
06:14:00:WU00:FS00:0xa8:  Copyright: 2020 foldingathome.org
06:14:00:WU00:FS00:0xa8:   Homepage: https://foldingathome.org/
06:14:00:WU00:FS00:0xa8:       Date: Jan 16 2021
06:14:00:WU00:FS00:0xa8:       Time: 11:25:04
06:14:00:WU00:FS00:0xa8:   Revision: c5816759c404e4b65f9f364c3d1ef554a67c4225
06:14:00:WU00:FS00:0xa8:     Branch: master
06:14:00:WU00:FS00:0xa8:   Compiler: Visual C++ 2019 16.7
06:14:00:WU00:FS00:0xa8:    Options: /TP /std:c++14 /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
06:14:01:WU00:FS00:0xa8:   Platform: win32 10
06:14:01:WU00:FS00:0xa8:       Bits: 64
06:14:01:WU00:FS00:0xa8:       Mode: Release
06:14:01:WU00:FS00:0xa8:       SIMD: sse2
06:14:01:WU00:FS00:0xa8:     OpenMP: ON
06:14:01:WU00:FS00:0xa8:       CUDA: OFF
06:14:01:WU00:FS00:0xa8:       Args: -dir 00 -suffix 01 -version 706 -lifeline 36072 -checkpoint 15 -np
06:14:01:WU00:FS00:0xa8:             2
06:14:01:WU00:FS00:0xa8:************************************ libFAH ************************************
06:14:01:WU00:FS00:0xa8:       Date: Jan 16 2021
06:14:01:WU00:FS00:0xa8:       Time: 11:24:13
06:14:01:WU00:FS00:0xa8:   Revision: c5816759c404e4b65f9f364c3d1ef554a67c4225
06:14:01:WU00:FS00:0xa8:     Branch: master
06:14:01:WU00:FS00:0xa8:   Compiler: Visual C++ 2019 16.7
06:14:01:WU00:FS00:0xa8:    Options: /TP /std:c++14 /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
06:14:01:WU00:FS00:0xa8:   Platform: win32 10
06:14:01:WU00:FS00:0xa8:       Bits: 64
06:14:01:WU00:FS00:0xa8:       Mode: Release
06:14:01:WU00:FS00:0xa8:************************************ CBang *************************************
06:14:01:WU00:FS00:0xa8:       Date: Jan 16 2021
06:14:01:WU00:FS00:0xa8:       Time: 11:23:53
06:14:01:WU00:FS00:0xa8:   Revision: c5816759c404e4b65f9f364c3d1ef554a67c4225
06:14:01:WU00:FS00:0xa8:     Branch: master
06:14:01:WU00:FS00:0xa8:   Compiler: Visual C++ 2019 16.7
06:14:01:WU00:FS00:0xa8:    Options: /TP /std:c++14 /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
06:14:01:WU00:FS00:0xa8:   Platform: win32 10
06:14:01:WU00:FS00:0xa8:       Bits: 64
06:14:01:WU00:FS00:0xa8:       Mode: Release
06:14:01:WU00:FS00:0xa8:************************************ System ************************************
06:14:01:WU00:FS00:0xa8:        CPU: Intel(R) Pentium(R) CPU N3700 @ 1.60GHz
06:14:01:WU00:FS00:0xa8:     CPU ID: GenuineIntel Family 6 Model 76 Stepping 3
06:14:01:WU00:FS00:0xa8:       CPUs: 4
06:14:01:WU00:FS00:0xa8:     Memory: 7.92GiB
06:14:01:WU00:FS00:0xa8:Free Memory: 3.52GiB
06:14:01:WU00:FS00:0xa8:    Threads: WINDOWS_THREADS
06:14:01:WU00:FS00:0xa8: OS Version: 6.2
06:14:01:WU00:FS00:0xa8:Has Battery: false
06:14:01:WU00:FS00:0xa8: On Battery: false
06:14:01:WU00:FS00:0xa8: UTC Offset: 0
06:14:01:WU00:FS00:0xa8:        PID: 64528
06:14:01:WU00:FS00:0xa8:        CWD: C:\ProgramData\FAHClient\work
06:14:01:WU00:FS00:0xa8:********************************************************************************
06:14:01:WU00:FS00:0xa8:Project: 17255 (Run 2342, Clone 2, Gen 16)
06:14:01:WU00:FS00:0xa8:Unit: 0x00000000000000000000000000000000
06:14:01:WU00:FS00:0xa8:Reading tar file core.xml
06:14:01:WU00:FS00:0xa8:Reading tar file frame16.tpr
06:14:01:WU00:FS00:0xa8:Digital signatures verified
06:14:01:WU01:FS01:Received Unit: id:01 state:DOWNLOAD error:NO_ERROR project:18021 run:62 clone:7 gen:198 core:0x22 unit:0x00000007000000c6000046650000003e
06:14:01:WU00:FS00:0xa8:Calling: mdrun -c frame16.gro -s frame16.tpr -x frame16.xtc -cpt 15 -nt 2 -ntmpi 1
06:14:01:WU01:FS01:Downloading core from http://cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah
06:14:01:WU00:FS00:0xa8:Steps: first=4000000 total=4250000
06:14:01:WU01:FS01:Connecting to cores.foldingathome.org:80
06:14:02:WU01:FS01:FahCore 22: Downloading 156.61MiB
06:14:08:WU01:FS01:FahCore 22: 9.74%
06:14:14:WU01:FS01:FahCore 22: 20.91%
06:14:20:WU01:FS01:FahCore 22: 30.97%
06:14:20:WU00:FS00:0xa8:Completed 1 out of 250000 steps (0%)
06:14:23:FS00:Shutting core down
06:14:23:WU00:FS00:0xa8:WARNING:Console control signal 1 on PID 64528
06:14:23:WU00:FS00:0xa8:Exiting, please wait. . .
06:14:26:WU01:FS01:FahCore 22: 41.66%
06:14:32:WU01:FS01:FahCore 22: 54.51%
06:14:38:WU01:FS01:FahCore 22: 67.09%
06:14:44:WU01:FS01:FahCore 22: 79.46%
06:14:48:Saving configuration to config.xml
06:14:48:<config>
06:14:48:  <!-- Slot Control -->
06:14:48:  <power v='FULL'/>
06:14:48:
06:14:48:  <!-- User Information -->
06:14:48:  <passkey v='*****'/>
06:14:48:  <team v='224497'/>
06:14:48:  <user v='PeterHucker_1HK9mWMp2xTK3f7fjowi1mCCbczu2EgFyR'/>
06:14:48:
06:14:48:  <!-- Folding Slots -->
06:14:48:  <slot id='0' type='CPU'/>
06:14:48:  <slot id='1' type='GPU'>
06:14:48:    <pci-bus v='1'/>
06:14:48:    <pci-slot v='0'/>
06:14:48:  </slot>
06:14:48:</config>
06:14:50:WU01:FS01:FahCore 22: 90.35%
06:14:51:WU00:FS00:FahCore returned: INTERRUPTED (102 = 0x66)
06:14:51:WU00:FS00:Starting
06:14:51:WARNING:WU00:FS00:Changed SMP threads from 2 to 3 this can cause some work units to fail
06:14:51:WARNING:WU00:FS00:AS lowered CPUs from 3 to 2
06:14:51:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\ProgramData\FAHClient\cores/cores.foldingathome.org/win/64bit-sse2/a8-0.0.12/Core_a8.fah/FahCore_a8.exe -dir 00 -suffix 01 -version 706 -lifeline 1844 -checkpoint 15 -np 2
06:14:52:WU00:FS00:Started FahCore on PID 30924
06:14:52:WU00:FS00:Core PID:11532
06:14:52:WU00:FS00:FahCore 0xa8 started
06:14:53:WU00:FS00:0xa8:*********************** Log Started 2022-02-19T06:14:53Z ***********************
06:14:53:WU00:FS00:0xa8:************************** Gromacs Folding@home Core ***************************
06:14:53:WU00:FS00:0xa8:       Core: Gromacs
06:14:53:WU00:FS00:0xa8:       Type: 0xa8
06:14:53:WU00:FS00:0xa8:    Version: 0.0.12
06:14:53:WU00:FS00:0xa8:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
06:14:53:WU00:FS00:0xa8:  Copyright: 2020 foldingathome.org
06:14:53:WU00:FS00:0xa8:   Homepage: https://foldingathome.org/
06:14:53:WU00:FS00:0xa8:       Date: Jan 16 2021
06:14:53:WU00:FS00:0xa8:       Time: 11:25:04
06:14:53:WU00:FS00:0xa8:   Revision: c5816759c404e4b65f9f364c3d1ef554a67c4225
06:14:53:WU00:FS00:0xa8:     Branch: master
06:14:53:WU00:FS00:0xa8:   Compiler: Visual C++ 2019 16.7
06:14:53:WU00:FS00:0xa8:    Options: /TP /std:c++14 /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
06:14:53:WU00:FS00:0xa8:   Platform: win32 10
06:14:53:WU00:FS00:0xa8:       Bits: 64
06:14:53:WU00:FS00:0xa8:       Mode: Release
06:14:53:WU00:FS00:0xa8:       SIMD: sse2
06:14:53:WU00:FS00:0xa8:     OpenMP: ON
06:14:53:WU00:FS00:0xa8:       CUDA: OFF
06:14:53:WU00:FS00:0xa8:       Args: -dir 00 -suffix 01 -version 706 -lifeline 30924 -checkpoint 15 -np
06:14:53:WU00:FS00:0xa8:             2
06:14:53:WU00:FS00:0xa8:************************************ libFAH ************************************
06:14:53:WU00:FS00:0xa8:       Date: Jan 16 2021
06:14:53:WU00:FS00:0xa8:       Time: 11:24:13
06:14:53:WU00:FS00:0xa8:   Revision: c5816759c404e4b65f9f364c3d1ef554a67c4225
06:14:53:WU00:FS00:0xa8:     Branch: master
06:14:53:WU00:FS00:0xa8:   Compiler: Visual C++ 2019 16.7
06:14:53:WU00:FS00:0xa8:    Options: /TP /std:c++14 /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
06:14:53:WU00:FS00:0xa8:   Platform: win32 10
06:14:53:WU00:FS00:0xa8:       Bits: 64
06:14:53:WU00:FS00:0xa8:       Mode: Release
06:14:53:WU00:FS00:0xa8:************************************ CBang *************************************
06:14:53:WU00:FS00:0xa8:       Date: Jan 16 2021
06:14:53:WU00:FS00:0xa8:       Time: 11:23:53
06:14:53:WU00:FS00:0xa8:   Revision: c5816759c404e4b65f9f364c3d1ef554a67c4225
06:14:53:WU00:FS00:0xa8:     Branch: master
06:14:53:WU00:FS00:0xa8:   Compiler: Visual C++ 2019 16.7
06:14:53:WU00:FS00:0xa8:    Options: /TP /std:c++14 /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
06:14:53:WU00:FS00:0xa8:   Platform: win32 10
06:14:53:WU00:FS00:0xa8:       Bits: 64
06:14:53:WU00:FS00:0xa8:       Mode: Release
06:14:53:WU00:FS00:0xa8:************************************ System ************************************
06:14:53:WU00:FS00:0xa8:        CPU: Intel(R) Pentium(R) CPU N3700 @ 1.60GHz
06:14:53:WU00:FS00:0xa8:     CPU ID: GenuineIntel Family 6 Model 76 Stepping 3
06:14:53:WU00:FS00:0xa8:       CPUs: 4
06:14:53:WU00:FS00:0xa8:     Memory: 7.92GiB
06:14:53:WU00:FS00:0xa8:Free Memory: 3.32GiB
06:14:53:WU00:FS00:0xa8:    Threads: WINDOWS_THREADS
06:14:53:WU00:FS00:0xa8: OS Version: 6.2
06:14:53:WU00:FS00:0xa8:Has Battery: false
06:14:53:WU00:FS00:0xa8: On Battery: false
06:14:53:WU00:FS00:0xa8: UTC Offset: 0
06:14:53:WU00:FS00:0xa8:        PID: 11532
06:14:53:WU00:FS00:0xa8:        CWD: C:\ProgramData\FAHClient\work
06:14:53:WU00:FS00:0xa8:********************************************************************************
06:14:53:WU00:FS00:0xa8:Project: 17255 (Run 2342, Clone 2, Gen 16)
06:14:53:WU00:FS00:0xa8:Unit: 0x00000000000000000000000000000000
06:14:53:WU00:FS00:0xa8:Digital signatures verified
06:14:53:WU00:FS00:0xa8:Calling: mdrun -c frame16.gro -s frame16.tpr -x frame16.xtc -cpi state.cpt -cpt 15 -nt 2 -ntmpi 1
06:14:54:WU00:FS00:0xa8:Steps: first=4000000 total=4250000
06:14:54:WU01:FS01:FahCore 22: Download complete
06:14:55:WU01:FS01:Valid core signature
06:14:55:WU01:FS01:Unpacked 5.52MiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/FahCore_22.exe
06:14:55:WU01:FS01:Unpacked 24.45KiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/api-ms-win-crt-runtime-l1-1-0.dll
06:14:57:WU01:FS01:Unpacked 179.58MiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/cufft64_10.dll
06:15:02:WU01:FS01:Unpacked 3.25MiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/libcrypto-1_1-x64.dll
06:15:02:WU01:FS01:Unpacked 667.00KiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/libssl-1_1-x64.dll
06:15:02:WU01:FS01:Unpacked 552.38KiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/msvcp140.dll
06:15:02:WU01:FS01:Unpacked 23.38KiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/msvcp140_1.dll
06:15:02:WU01:FS01:Unpacked 181.38KiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/msvcp140_2.dll
06:15:02:WU01:FS01:Unpacked 54.88KiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/msvcp140_atomic_wait.dll
06:15:02:WU01:FS01:Unpacked 19.88KiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/msvcp140_codecvt_ids.dll
06:15:02:WU01:FS01:Unpacked 5.29MiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/nvrtc-builtins64_112.dll
06:15:02:WU01:FS01:Unpacked 30.51MiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/nvrtc64_112_0.dll
06:15:02:WU01:FS01:Unpacked 2.81MiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/OpenMM.dll
06:15:02:WU01:FS01:Unpacked 302.00KiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/OpenMMAmoeba.dll
06:15:02:WU01:FS01:Unpacked 1.04MiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/OpenMMAmoebaCUDA.dll
06:15:02:WU01:FS01:Unpacked 952.00KiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/OpenMMAmoebaOpenCL.dll
06:15:02:WU01:FS01:Unpacked 458.50KiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/OpenMMAmoebaReference.dll
06:15:02:WU01:FS01:Unpacked 517.50KiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/OpenMMCPU.dll
06:15:02:WU01:FS01:Unpacked 1.78MiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/OpenMMCUDA.dll
06:15:02:WU01:FS01:Unpacked 60.50KiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/OpenMMCudaCompiler.dll
06:15:02:WU01:FS01:Unpacked 99.50KiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/OpenMMDrude.dll
06:15:03:WU01:FS01:Unpacked 118.00KiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/OpenMMDrudeCUDA.dll
06:15:03:WU01:FS01:Unpacked 118.00KiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/OpenMMDrudeOpenCL.dll
06:15:03:WU01:FS01:Unpacked 87.00KiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/OpenMMDrudeReference.dll
06:15:03:WU01:FS01:Unpacked 1.81MiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/OpenMMOpenCL.dll
06:15:03:WU01:FS01:Unpacked 61.00KiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/OpenMMPME.dll
06:15:03:WU01:FS01:Unpacked 57.00KiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/OpenMMRPMD.dll
06:15:03:WU01:FS01:Unpacked 138.50KiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/OpenMMRPMDCUDA.dll
06:15:03:WU01:FS01:Unpacked 138.50KiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/OpenMMRPMDOpenCL.dll
06:15:03:WU01:FS01:Unpacked 75.50KiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/OpenMMRPMDReference.dll
06:15:03:WU01:FS01:Unpacked 94.88KiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/vcruntime140.dll
06:15:03:WU01:FS01:Unpacked 36.38KiB to cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/vcruntime140_1.dll
06:15:03:WU01:FS01:Starting
06:15:03:WU01:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\ProgramData\FAHClient\cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/FahCore_22.exe -dir 01 -suffix 01 -version 706 -lifeline 1844 -checkpoint 15 -opencl-platform 0 -opencl-device 0 -gpu-vendor amd -gpu 0 -gpu-usage 100
06:15:03:WU01:FS01:Started FahCore on PID 45816
06:15:03:WU01:FS01:Core PID:60136
06:15:03:WU01:FS01:FahCore 0x22 started
06:15:04:WU00:FS00:0xa8:Completed 12 out of 250000 steps (0%)
06:15:04:WU01:FS01:0x22:*********************** Log Started 2022-02-19T06:15:04Z ***********************
06:15:05:WU01:FS01:0x22:*************************** Core22 Folding@home Core ***************************
06:15:05:WU01:FS01:0x22:       Core: Core22
06:15:05:WU01:FS01:0x22:       Type: 0x22
06:15:05:WU01:FS01:0x22:    Version: 0.0.20
06:15:05:WU01:FS01:0x22:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
06:15:05:WU01:FS01:0x22:  Copyright: 2020 foldingathome.org
06:15:05:WU01:FS01:0x22:   Homepage: https://foldingathome.org/
06:15:05:WU01:FS01:0x22:       Date: Jan 20 2022
06:15:05:WU01:FS01:0x22:       Time: 01:15:36
06:15:05:WU01:FS01:0x22:   Revision: 3f211b8a4346514edbff34e3cb1c0e0ec951373c
06:15:05:WU01:FS01:0x22:     Branch: HEAD
06:15:05:WU01:FS01:0x22:   Compiler: Visual C++
06:15:05:WU01:FS01:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
06:15:05:WU01:FS01:0x22:             -DOPENMM_VERSION="\"7.7.0\""
06:15:05:WU01:FS01:0x22:   Platform: win32 10
06:15:05:WU01:FS01:0x22:       Bits: 64
06:15:05:WU01:FS01:0x22:       Mode: Release
06:15:05:WU01:FS01:0x22:Maintainers: John Chodera <john.chodera@choderalab.org> and Peter Eastman
06:15:05:WU01:FS01:0x22:             <peastman@stanford.edu>
06:15:05:WU01:FS01:0x22:       Args: -dir 01 -suffix 01 -version 706 -lifeline 45816 -checkpoint 15
06:15:05:WU01:FS01:0x22:             -opencl-platform 0 -opencl-device 0 -gpu-vendor amd -gpu 0
06:15:05:WU01:FS01:0x22:             -gpu-usage 100
06:15:05:WU01:FS01:0x22:************************************ libFAH ************************************
06:15:05:WU01:FS01:0x22:       Date: Jan 20 2022
06:15:05:WU01:FS01:0x22:       Time: 01:14:17
06:15:05:WU01:FS01:0x22:   Revision: 9f4ad694e75c2350d4bb6b8b5b769ba27e483a2f
06:15:05:WU01:FS01:0x22:     Branch: HEAD
06:15:05:WU01:FS01:0x22:   Compiler: Visual C++
06:15:05:WU01:FS01:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
06:15:05:WU01:FS01:0x22:   Platform: win32 10
06:15:05:WU01:FS01:0x22:       Bits: 64
06:15:05:WU01:FS01:0x22:       Mode: Release
06:15:05:WU01:FS01:0x22:************************************ CBang *************************************
06:15:05:WU01:FS01:0x22:       Date: Jan 20 2022
06:15:05:WU01:FS01:0x22:       Time: 01:13:20
06:15:05:WU01:FS01:0x22:   Revision: ab023d155b446906d55b0f6c9a1eedeea04f7a1a
06:15:05:WU01:FS01:0x22:     Branch: HEAD
06:15:05:WU01:FS01:0x22:   Compiler: Visual C++
06:15:05:WU01:FS01:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
06:15:05:WU01:FS01:0x22:   Platform: win32 10
06:15:05:WU01:FS01:0x22:       Bits: 64
06:15:05:WU01:FS01:0x22:       Mode: Release
06:15:05:WU01:FS01:0x22:************************************ System ************************************
06:15:05:WU01:FS01:0x22:        CPU: Intel(R) Pentium(R) CPU N3700 @ 1.60GHz
06:15:05:WU01:FS01:0x22:     CPU ID: GenuineIntel Family 6 Model 76 Stepping 3
06:15:05:WU01:FS01:0x22:       CPUs: 4
06:15:05:WU01:FS01:0x22:     Memory: 7.92GiB
06:15:05:WU01:FS01:0x22:Free Memory: 3.33GiB
06:15:05:WU01:FS01:0x22:    Threads: WINDOWS_THREADS
06:15:05:WU01:FS01:0x22: OS Version: 6.2
06:15:05:WU01:FS01:0x22:Has Battery: false
06:15:05:WU01:FS01:0x22: On Battery: false
06:15:05:WU01:FS01:0x22: UTC Offset: 0
06:15:05:WU01:FS01:0x22:        PID: 60136
06:15:05:WU01:FS01:0x22:        CWD: C:\ProgramData\FAHClient\work
06:15:05:WU01:FS01:0x22:************************************ OpenMM ************************************
06:15:05:WU01:FS01:0x22:    Version: 7.7.0
06:15:05:WU01:FS01:0x22:********************************************************************************
06:15:05:WU01:FS01:0x22:Project: 18021 (Run 62, Clone 7, Gen 198)
06:15:05:WU01:FS01:0x22:Reading tar file core.xml
06:15:05:WU01:FS01:0x22:Reading tar file integrator.xml.bz2
06:15:05:WU01:FS01:0x22:Reading tar file state.xml.bz2
06:15:05:WU01:FS01:0x22:Reading tar file system.xml.bz2
06:15:05:WU01:FS01:0x22:Digital signatures verified
06:15:05:WU01:FS01:0x22:Folding@home GPU Core22 Folding@home Core
06:15:05:WU01:FS01:0x22:Version 0.0.20
06:15:08:WU01:FS01:0x22:  Checkpoint write interval: 125000 steps (5%) [20 total]
06:15:08:WU01:FS01:0x22:  JSON viewer frame write interval: 25000 steps (1%) [100 total]
06:15:08:WU01:FS01:0x22:  XTC frame write interval: 250000 steps (10%) [10 total]
06:15:08:WU01:FS01:0x22:  Global context and integrator variables write interval: disabled
06:15:08:WU01:FS01:0x22:There are 3 platforms available.
06:15:08:WU01:FS01:0x22:Platform 0: Reference
06:15:08:WU01:FS01:0x22:Platform 1: CPU
06:15:08:WU01:FS01:0x22:Platform 2: OpenCL
06:15:08:WU01:FS01:0x22:  opencl-device 0 specified
06:16:00:WU01:FS01:0x22:Attempting to create OpenCL context:
06:16:00:WU01:FS01:0x22:  Configuring platform OpenCL
06:16:29:WU01:FS01:0x22:  Using OpenCL on platformId 0 and gpu 0
06:16:29:WU01:FS01:0x22:Completed 0 out of 2500000 steps (0%)
06:16:32:WU01:FS01:0x22:Checkpoint completed at step 0
06:18:37:FS00:Shutting core down
06:18:37:FS01:Shutting core down
06:18:37:WU01:FS01:0x22:WARNING:Console control signal 1 on PID 60136
06:18:37:WU00:FS00:0xa8:WARNING:Console control signal 1 on PID 11532
06:18:37:WU01:FS01:0x22:Exiting, please wait. . .
06:18:37:WU00:FS00:0xa8:Exiting, please wait. . .
06:18:37:WU01:FS01:0x22:Folding@home Core Shutdown: INTERRUPTED
06:18:42:Clean exit

Re: Ability to abort/cancel a workunit?

Posted: Sat Feb 19, 2022 9:17 am
by Peter_Hucker
Neil-B wrote:@Peter_Hucker ... If you feel that way then maybe tbh using Boinc might reduce stress levels? ... FaH software is what it is - for many it works perfectly well and allows folders to contribute effortlessly, but it does have known limitations that are being worked on ... Setup can be a challenge, various OS and legacy software issues can make certain kit combinations hard to configure and some pretty much impossible ... Individual donors are obviously at liberty to decide whether the effort required to maintain their setups is worth it - some do and some decide it is too much effort ... FaH is working on improving and updating the user experience but for now it simply is what it is ... Support in these forums is from volunteer folders who try to assist new/other folders as/where they can.
FAH has been running for 22 years and you're telling me they're still ironing out bugs?

Re: Ability to abort/cancel a workunit?

Posted: Sat Feb 19, 2022 10:05 am
by Neil-B
Peter_Hucker wrote:FAH has been running for 22 years and you're telling me thley're still ironing out bugs?
Simply put "Yes"

A bit of the history of FaH (in naive format, as I understand it) may help you understand this:

FaH has evolved slowly with minimal developer effort (academic funding tends to be for researchers not for software devs) ... as the science has advanced the software (server side and client side) has adapted as essentially necessary (and at minimal cost/dev time) to deliver what is needed by the researchers ... the existence of this forum and the volunteer basis it runs on was basically driven by the enthusiasts who wanted to help FaH deliver for the researchers as is indicative of the ongoing development state of the softeware over the years ... much of the dev effort has been focused on the server side and the delivery of the science - UX has been low priority in the funding - relatively minimal effort has been expended - and to be honest given the pretty much solo developer nature of the past support the system has coped surprisingly well ... recently a little more developer effort has been available and work is underway for a major revision of the client which may well make the whole folder experience much more pleasant - this was being worked on before the surge that hit the servers at the start of covid meant the dev needed to support the server/system expansion.

Given the history of FaH it has come a long way and has delivered huge benefits to the research community - during the surge it peaked well into the exascale compute level ... but it is far from a perfect, polished, commercial product ... It would be great if it was but it isn't.

As to cpu speeds (again as I understand it) the assignment server has no information as to the capability on cpus simply the number of core/threads assigned to the cpu slot - with the type of projects in the past and the amount of folding resource available this wasn't an issue, but with more urgent projects and a much greater pool of resource the need to differentiate has perhaps outstripped the way the software is architected ... a four core slot based on a 10 year old cpu with little/no extensions and at minimal cliock speeds will perform far worse than a four core slot on a current cpu with avx2 extensions and fast clock speeds - in this case I believe you are using a two core slot of a seven year old cpu that wasn't particularly powerful when first released with no performance extensions and low clock/tdp which would put it at at less than 25% of the performance of my 2 year old 10850k on a two core slot comparison (I actually run an 18core slot when I cpu fold on that machine - my older servers actually run higher clocks/tdps than your cpu and I use 32 and 24 core slots) ... this issue with cpu assignments may be something that will be addressed with the next version of the client software with assignments to cpu slots being much more flexible however this would also required a recode of the server software to match and whether it will happen is yet to be seen.

The way FaH is architected is based on single releases of wus (no duplicate release like some other approaches) and the science advances best if wus are returned quickly hence the existence of the Timeout and Expiry deadlines ... in the past when projects were less urgent and ran for longer and where there was much more work to be done than resource available to do it the deadlines were longer and fewer cpus were unable to cope with them ... but the last couple of years have changed that and it is quite possible now that some of the older/weaker cpus may simply not be able to return wus within deadlines it should not be used for folding (obviously this can also be impacted by folding patterns) - currently that is a manual/folder managed process - maybe in the future this will be managed for cpus in a similar fashion to gpus where kit that cannot meet deadlines (or haven't the required capabilities) are simply not assigned any wus.

I do understand your frustration with assignments - yes all folders would prefer their kit to be assigned the best projects for their kit (or at least ones that work/can complete) - but the reality is that is not where the FaH software/capability is at this time.

Re: Ability to abort/cancel a workunit?

Posted: Sat Feb 19, 2022 4:06 pm
by Joe_H
Peter_Hucker wrote:One of you has already told me the server is supposed to know how fast each CPU model is and send out an appropriately sized workunit.
Where did you see that posted? I only see that being said about GPUs, not CPUs. What has been posted about CPUs is that the servers only get information abut how many threads are being requested for a CPU WU, nothing about speed of the processor itself.

You finally posted the beginning section of the log which had been requested several times in the topics you have posted. Finally we get to see what your system configuration is on this system. You have a 7 year old low power Pentium N3700 @ 1.6 GHz that is thermally limited to 6 W TDP. It supports SSE up to 4.2, but does not have AVX support.

Basically this is a borderline CPU, enough to handle the CPU side of GPU processing but will not complete all CPU WUs within deadlines. Without AVX the CPU folding core uses SSE2 instructions and runs somewhat slower than on a system with AVX available. On a faster processor this is good enough, I ran folding on a 12 year old processor that only supported SSE until its PS failed, and never ran into problems completing WUs within their deadlines.

Re: Ability to abort/cancel a workunit?

Posted: Sat Feb 19, 2022 5:30 pm
by aetch
@Peter_Hucker - Thank You for finally posting a full log.
My suggestion would be to pause and delete the CPU slot.

When the CPU is too low powered or overworked it impacts the performance of any connected GPUs, sometime severely.
Each GPU in a folding system requires a free thread/core on the CPU and bare minimum PCIe x4 (x8 recommended) slot.
Personally, I normally also recommend leaving a free thread/core for the operating system to run in.

On your Windows rigs I would also recommend adding the FAHClient working folders and program files to the exclusions list of your internet security. This is to prevent your internet security from falsely flagging the work units and components of FAH as malware, especially the folding cores as these are updated reasonably regularly to take advantage of new technologies in graphics cards and processors and/or to implement optimisations in their code.
Folders to add:-
"C:\ProgramData\FAHClient" - FAH recommendation (https://foldingathome.org/support/faq/i ... ts/?lng=en see notes at bottom of page)
"C:\Program Files (x86)\FAHClient" - My recommendation
If adding to Windows Defender - Start ->Settings -> Update & Security -> Windows Security -> Open Windows Security -> Virus & Threat Protection (opens new window)
Scroll down to "Virus & threat protection settings" -> Manage settings -> Add or remove exclusions -> Add an exclusion (see above folders to add)

Other may be able to help you with the location of this list in 3rd party internet security applications.

We sometimes get people with mining rigs which typically have very weak processors and are connected to many GPUs through x1 PCIe riser cables. Our advice is to basically rebuild the rigs.

Re: Ability to abort/cancel a workunit?

Posted: Sat Feb 19, 2022 5:43 pm
by Peter_Hucker
Neil-B wrote:The way FaH is architected is based on single releases of wus (no duplicate release like some other approaches) and the science advances best if wus are returned quickly hence the existence of the Timeout and Expiry deadlines
Thanks for your extensive explanation, just one thing to clear up, I can't work out what these mean. AFAIK if I pass the first deadline, the task is sent to somebody else. So what's the second deadline for? Why should my computer keep going after the first one, knowing someone else has it that will probably get it done, so I'd just be duplicating the answer.

Re: Ability to abort/cancel a workunit?

Posted: Sat Feb 19, 2022 5:46 pm
by Peter_Hucker
Joe_H wrote:Where did you see that posted? I only see that being said about GPU
Ah ok, I misremembered. Or assumed it would be done for both. Odd they implemented it for GPU but not CPU, both have a wide range of speeds. Is there a way to fool FAH server into thinking my CPU is 1 core, so I get tiny jobs, but then run them on 4 cores and get them done in time?

Re: Ability to abort/cancel a workunit?

Posted: Sat Feb 19, 2022 5:50 pm
by Peter_Hucker
aetch wrote:@Peter_Hucker - Thank You for finally posting a full log.
It was difficult to do so since I was constantly playing around with the machines, so it was difficult to find what went wrong when.
aetch wrote:My suggestion would be to pause and delete the CPU slot.
Won't it come back on reboot? That happened when I deleted a GPU slot. Rather annoying as a computer I don't want to fold on GPU I have to leave the slot there and paused, and sometimes it unpauses after a reboot too!
aetch wrote:We sometimes get people with mining rigs which typically have very weak processors and are connected to many GPUs through x1 PCIe riser cables. Our advice is to basically rebuild the rigs.
I don't have that currently, but I have done that in the past using Boinc. It didn't cause any problems. Does FAH transmit data more regularly across PCI-Express than Boinc?

Re: Ability to abort/cancel a workunit?

Posted: Sat Feb 19, 2022 6:03 pm
by Neil-B
No cpu slots won't come back .. there is a setting that can be set to stop gpu slots being auto generated if you want to know more search the forums or ask .. I know nothing about boinc but can confirm that FaH has PCI-E requirements that exceed mining rigs x1 risers - how much depends on the gpu and the generation of PCI-E

Re: Ability to abort/cancel a workunit?

Posted: Sat Feb 19, 2022 6:20 pm
by Peter_Hucker
The only setting I found disables GPUs altogether. No use if I want to turn one off but not the other. For now I'll just use pause on GPUs.

At the moment I have enough PCs to put one GPU in each. But I am out of slots now, so the next GPU will have to be on a riser. Mind you, it's possible to use a 16 lane ribbon if I can get the GPU to sit close enough. Otherwise I guess extended ones just go to Boinc. Unfortunately there's no biology GPU projects on Boinc for AMD cards.

Re: Ability to abort/cancel a workunit?

Posted: Sat Feb 19, 2022 6:28 pm
by aetch
Peter_Hucker wrote:Won't it come back on reboot?
No, that only happens with GPUs.
The only time the client will only automatically add CPU slots is when there are no slots configured.

To stop it automatically re-adding the GPUs you can add the following entry to the "Extra client options" on the "Expert" tab of the configuration
name: gpu
value: false

This will not add or remove GPU slots, it just means you are manually adding them.

In the same location you can also add the entry
name: pause-on-start
value: true
this will ensure when the computer boots it will pause all slots until you manually start them.
aetch wrote:Does FAH transmit data more regularly across PCI-Express than Boinc?
Sorry, I really don't know anything about boinc other than the name.
FAH is constantly shuffling data back and forth to the GPUs, which is why it has such high bandwidth requirements.

Re: Ability to abort/cancel a workunit?

Posted: Sat Feb 19, 2022 6:39 pm
by Peter_Hucker
aetch wrote:To stop it automatically re-adding the GPUs you can add the following entry to the "Extra client options" on the "Expert" tab of the configuration
name: gpu
value: false
Thanks, I've noted that down.

Re: Ability to abort/cancel a workunit?

Posted: Sat Feb 19, 2022 7:55 pm
by aetch
Peter_Hucker wrote:Thanks for your extensive explanation, just one thing to clear up, I can't work out what these mean. AFAIK if I pass the first deadline, the task is sent to somebody else. So what's the second deadline for? Why should my computer keep going after the first one, knowing someone else has it that will probably get it done, so I'd just be duplicating the answer.
FAH is like a relay race. The next leg cannot start until the current leg has been completed.
For the most part only one copy of each work unit is sent out, most folders return it before the timeout triggers. This is about using limited resources wisely.
The timeout triggers a second copy of your work unit being assigned to someone else.
The thing to realise is that the next person is not guaranteed to be in any better of a position than you are. They are not guaranteed to return the work unit any quicker, if at all.
Returning your work unit late still allows the next work unit to be started, albeit resources have been wasted ensuring it will actually get done.
The last thing we want is for research to stop because it has hit a string of folders who cannot return the assigned work in a reasonable time, hence the grace period between timeout and expiry.

The second deadline (expiry) is basically the researchers giving up hope of receiving the assigned work unit back from you.

I will pass comment that some of the timeout/expiry times don't make sense to me.
https://apps.foldingathome.org/psummary
All times are UTC
Page 2 of 4

Powered by phpBB® Forum Software © phpBB Limited