Page 1 of 1
BAD_WORK_UNIT (114 = 0x72)
Posted: Wed Apr 08, 2020 7:27 pm
by lusterking
I recently installed FAH on about 100 computers sitting idle at work since noone is there. It seems that every one frequently gets the following error:
Code: Select all
18:35:45:WU00:FS00:Starting
18:35:45:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\Windows\system32\cores/cores.foldingathome.org/v7/win/64bit/avx/Core_a7.fah/FahCore_a7.exe -dir 00 -suffix 01 -version 705 -lifeline 12068 -checkpoint 15 -np 4
18:35:45:WU00:FS00:Started FahCore on PID 2904
18:35:45:WU00:FS00:Core PID:9304
18:35:45:WU00:FS00:FahCore 0xa7 started
18:35:46:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
I found several threads where people suggest to update the video driver, but these are HP business class machines with Intel display adapters so it should just be using the cpu.
Is there maybe a setting I have wrong, or anything else to look at?
Thanks,
Steve
Re: BAD_WORK_UNIT (114 = 0x72)
Posted: Wed Apr 08, 2020 7:38 pm
by uyaem
Can you please provide a bit more of your log file?
Relevant parts are described here: viewtopic.php?f=61&t=26036
Thanks!
Re: BAD_WORK_UNIT (114 = 0x72)
Posted: Wed Apr 08, 2020 7:47 pm
by lusterking
Thank you! I cut out a bunch, but hopefully nothing important, mostly not getting assignments, and other copies of the error that I'm asking about
Code: Select all
*********************** Log Started 2020-04-08T17:50:18Z ***********************
17:50:18:************************* Folding@home Client *************************
17:50:18: Website: https://foldingathome.org/
17:50:18: Copyright: (c) 2009-2018 foldingathome.org
17:50:18: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
17:50:18: Args: --user=OIT --team=257946
17:50:18: --passkey=******************************** --idle=true
17:50:18: --power=full
17:50:18: Config: C:\Windows\system32\config.xml
17:50:18:******************************** Build ********************************
17:50:18: Version: 7.5.1
17:50:18: Date: May 11 2018
17:50:18: Time: 13:06:32
17:50:18: Repository: Git
17:50:18: Revision: 4705bf53c635f88b8fe85af7675557e15d491ff0
17:50:18: Branch: master
17:50:18: Compiler: Visual C++ 2008
17:50:18: Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
17:50:18: Platform: win32 10
17:50:18: Bits: 32
17:50:18: Mode: Release
17:50:18:******************************* System ********************************
17:50:18: CPU: Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
17:50:18: CPU ID: GenuineIntel Family 6 Model 94 Stepping 3
17:50:18: CPUs: 4
17:50:18: Memory: 7.79GiB
17:50:18: Free Memory: 5.42GiB
17:50:18: Threads: WINDOWS_THREADS
17:50:18: OS Version: 6.2
17:50:18: Has Battery: false
17:50:18: On Battery: false
17:50:18: UTC Offset: -4
17:50:18: PID: 12068
17:50:18: CWD: C:\Windows\system32
17:50:18: OS: Windows 10 Enterprise
17:50:18: OS Arch: AMD64
17:50:18: GPUs: 0
17:50:18: CUDA: Not detected: Failed to open dynamic library 'nvcuda.dll': The
17:50:18: specified module could not be found.
17:50:18:
17:50:18:OpenCL Device 0: Platform:0 Device:0 Bus:NA Slot:NA Compute:2.0 Driver:22.20
17:50:18: Win32 Service: false
17:50:18:***********************************************************************
17:50:19:<config>
17:50:19: <!-- Folding Slots -->
17:50:19: <slot id='0' type='CPU'>
17:50:19: <idle v='false'/>
17:50:19: </slot>
17:50:19:</config>
17:50:19:Trying to access database...
17:50:19:Successfully acquired database lock
17:50:19:Enabled folding slot 00: READY cpu:4
17:50:19:WU00:FS00:Connecting to 65.254.110.245:8080
17:50:20:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
18:35:44:WU00:FS00:Connecting to 65.254.110.245:8080
18:35:44:WU00:FS00:Assigned to work server 155.247.164.214
18:35:44:WU00:FS00:Requesting new work unit for slot 00: READY cpu:4 from 155.247.164.214
18:35:44:WU00:FS00:Connecting to 155.247.164.214:8080
18:35:44:WU00:FS00:Downloading 2.82MiB
18:35:44:WU00:FS00:Download complete
18:35:44:WU00:FS00:Received Unit: id:00 state:DOWNLOAD error:NO_ERROR project:14366 run:756 clone:1 gen:27 core:0xa7 unit:0x0000001c9bf7a4d65e81082a850d926e
18:35:44:WU00:FS00:Starting
18:35:44:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\Windows\system32\cores/cores.foldingathome.org/v7/win/64bit/avx/Core_a7.fah/FahCore_a7.exe -dir 00 -suffix 01 -version 705 -lifeline 12068 -checkpoint 15 -np 4
18:35:44:WU00:FS00:Started FahCore on PID 13096
18:35:44:WU00:FS00:Core PID:3268
18:35:44:WU00:FS00:FahCore 0xa7 started
18:35:45:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
Re: BAD_WORK_UNIT (114 = 0x72)
Posted: Thu Apr 09, 2020 1:42 am
by _r2w_ben
I see C:\Windows\system32\ in some of the paths in the log. The account used to run FAHClient probably does not have permission to write files there. Did you make changes to the default locations when installing?
Re: BAD_WORK_UNIT (114 = 0x72)
Posted: Thu Apr 09, 2020 3:03 am
by lusterking
Hmm, not that I know of, I just used the default settings. The user is an administrator
Re: BAD_WORK_UNIT (114 = 0x72)
Posted: Thu Apr 09, 2020 4:36 am
by PantherX
lusterking wrote:I recently installed FAH on about 100 computers sitting idle at work since noone is there...
Welcome to the F@H Forum lusterking,
Please note that if you're using work system to fold, you will need permission (generally written) from the people authorized to make that decision to run F@H on them. This is done as per the EULA.
Out of curiosity, how did you install the client? The default directories are not in the correct path so you're having permission issues as it is trying to write to locations it shouldn't be.
Your configuration path:
Code: Select all
17:50:18: Config: C:\Windows\system32\config.xml
My configuration Path
Code: Select all
18:07:21: Config: C:\Users\PantherX-H\AppData\Roaming\FAHClient\config.xml
Your CWD:
Code: Select all
17:50:18: CWD: C:\Windows\system32
My CWD:
Code: Select all
18:07:21: CWD: C:\Users\PantherX-H\AppData\Roaming\FAHClient
Your FahCore path:
Code: Select all
18:35:44:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\Windows\system32\cores/cores.foldingathome.org/v7/win/64bit/avx/Core_a7.fah/FahCore_a7.exe -dir 00 -suffix 01 -version 705 -lifeline 12068 -checkpoint 15 -np 4
My FahCore path:
Code: Select all
19:47:06:WU00:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\Users\PantherX-H\AppData\Roaming\FAHClient\cores/cores.foldingathome.org/v7/win/64bit/Core_22.fah/FahCore_22.exe -dir 00 -suffix 01 -version 705 -lifeline 8404 -checkpoint 15 -gpu-vendor nvidia -opencl-platform 0 -opencl-device 0 -cuda-device 0 -gpu 0
Assuming that you're only going to be folding on the CPU, my suggestion is that on one system (as a test), uninstall the client (including deleting all the data) and re-install it as a service. If you have issues, please post the new log file and we can look into it.
Re: BAD_WORK_UNIT (114 = 0x72)
Posted: Thu Apr 09, 2020 5:26 pm
by lusterking
PantherX wrote:lusterking wrote:I recently installed FAH on about 100 computers sitting idle at work since noone is there...
Welcome to the F@H Forum lusterking,
Please note that if you're using work system to fold, you will need permission (generally written) from the people authorized to make that decision to run F@H on them. This is done as per the EULA.
Yes, I definitely got permission from our CIO before starting on this project!
It seems like it had something to do with the way I used a batch file with the command line arguments to configure them.
I re-did one and now the CWD is c:\program files (x86)\fahclient which is different than what you posted, but probably better than windows\system32
So far I haven't gotten the error, but also haven't gotten a wu, so it's too soon to tell.
Thanks!
Re: BAD_WORK_UNIT (114 = 0x72)
Posted: Fri Apr 10, 2020 12:14 am
by PantherX
lusterking wrote:...I re-did one and now the CWD is c:\program files (x86)\fahclient which is different than what you posted, but probably better than windows\system32
So far I haven't gotten the error, but also haven't gotten a wu, so it's too soon to tell...
If you haven't gotten a WU in few hours, can you please post your log? If your next attempt is few hours, then you can pause/unpause the slot to reset the next attempt counter.
Re: BAD_WORK_UNIT (114 = 0x72)
Posted: Fri Apr 10, 2020 12:26 am
by lusterking
So far, the ones that I fixed are working.
Thanks!
Re: BAD_WORK_UNIT (114 = 0x72)
Posted: Fri Apr 10, 2020 12:55 am
by PantherX
That's great to hear! Hopefully, you can easily deploy to the remaining systems without major issue
Re: BAD_WORK_UNIT (114 = 0x72)
Posted: Fri Apr 10, 2020 12:56 am
by lusterking
Shouldn't be a problem, in fact I'm doing that right now. Thanks for your help!