FAH 8.18 Ubuntu Client not retrieving work.

[speed2048]

I have installed FAH client on Ubuntu 23.04. And is not retrieving any work for the CPU. It does recognized that the GPU is not supported I am running Ubuntu on a I5 Intel NUC. Here is the log file I am getting an exception so not sure if this is causing the issue. Highlighted in the log.

*********************** Log Started 2023-10-09T19:24:01Z ***********************
19:24:01:I1:*********************** Folding@home Client ***********************
19:24:01:I1: Version: 8.1.18
19:24:01:I1: Author: Joseph Coffland <[email protected]>
19:24:01:I1: Org: foldingathome.org
19:24:01:I1: Copyright: 2023 foldingathome.org
19:24:01:I1: Homepage: https://foldingathome.org/
19:24:01:I1: License: https://www.gnu.org/licenses/gpl-3.0.txt
19:24:01:I1: Date: Apr 18 2023
19:24:01:I1: Time: 12:09:09
19:24:01:I1: Revision: 80a3d5eb8f60f7833de2954087682958b511895c
19:24:01:I1: Branch: master
19:24:01:I1: Compiler: GNU 10.2.1 20210110
19:24:01:I1: Options: -faligned-new -std=c++17 -fsigned-char -ffunction-sections
19:24:01:I1: -fdata-sections -O3 -funroll-loops -fno-pie
19:24:01:I1: Platform: linux 5.10.0-16-cloud-amd64
19:24:01:I1: Bits: 64
19:24:01:I1: Mode: Release
19:24:01:I1: Args: --log=/var/log/fah-client/log.txt
19:24:01:I1: --log-rotate-dir=/var/log/fah-client/
19:24:01:I1: Config: /var/lib/fah-client/config.xml
19:24:01:I1:****************************** CBang ******************************
19:24:01:I1: Version: 1.7.2
19:24:01:I1: Author: Joseph Coffland <[email protected]>
19:24:01:I1: Org: Cauldron Development LLC
19:24:01:I1: Copyright: Cauldron Development LLC, 2003-2023
19:24:01:I1: Homepage: https://cauldrondevelopment.com/
19:24:01:I1: License: GPL 2+
19:24:01:I1: Date: Apr 14 2023
19:24:01:I1: Time: 16:26:30
19:24:01:I1: Revision: ac8bbdd5bb93c01679a881f5962fed800bf29e58
19:24:01:I1: Branch: master
19:24:01:I1: Compiler: GNU 10.2.1 20210110
19:24:01:I1: Options: -faligned-new -std=c++17 -fsigned-char -ffunction-sections
19:24:01:I1: -fdata-sections -O3 -funroll-loops -fno-pie -fPIC
19:24:01:I1: Platform: linux 5.10.0-16-cloud-amd64
19:24:01:I1: Bits: 64
19:24:01:I1: Mode: Release
19:24:01:I1:***************************** System ******************************
19:24:01:I1: CPU: Intel(R) Core(TM) i5-6260U CPU @ 1.80GHz
19:24:01:I1: CPU ID: GenuineIntel Family 6 Model 78 Stepping 3
19:24:01:I1: CPUs: 4
19:24:01:I1: Memory: 31.12GiB
19:24:01:I1:Free Memory: 26.39GiB
19:24:01:I1: Threads: POSIX_THREADS
19:24:01:I1: OS Version: 6.2
19:24:01:I1:Has Battery: false
19:24:01:I1: On Battery: false
19:24:01:I1: UTC Offset: -7
19:24:01:I1: PID: 5890
19:24:01:I1: CWD: /var/lib/fah-client
19:24:01:I1: Exec: /usr/bin/fah-client
19:24:01:I1:*******************************************************************
19:24:01:I2:<config>
19:24:01:I2: <!-- Client -->
19:24:01:I2:
19:24:01:I2: <!-- HTTP Server -->
19:24:01:I2: <allow v='0.0.0.0/0'/>
19:24:01:I2:
19:24:01:I2: <!-- User Information -->
19:24:01:I2: <passkey v='*****'/>
19:24:01:I2: <team v='54196'/>
19:24:01:I2: <user v='BoincSpy'/>
19:24:01:I2:</config>
19:24:01:I1:Opening Database
19:24:01:I1:Listening for HTTP on 127.0.0.1:7396
19:24:01:I1:Generating RSA key..........................++++-.............++++-
19:24:01:I3:id = UFJcTS8UO59WjYofBf9V9ZqSw8wr27GMNDB/mIJC6IU=
19:24:01:I3:Loaded 0 wus.
19:24:01:E :Exception: Not a Boolean
19:24:01:E :Exception: Failed to open dynamic library 'libOpenCL.so': libOpenCL.so: cannot open shared object file: No such file or directory
19:24:01:E :Exception: Failed to open dynamic library 'libcuda.so': libcuda.so: cannot open shared object file: No such file or directory
19:24:01:I3:gpus = {
19:24:01:I3: "gpu:00:02:00": {"vendor": 32902, "device": 6438, "type": "intel", "supported": false}
19:24:01:I3:}

[speed2048]

Found out the issue.

I had to toggle the Fold Anonymously button on and off to down load the workunit, I noticed the Json for the config.fold_anon was initiall set to 1 instead of a false or true. Once I toggled the button it is now its all working now.. So I suspect the exception in the log was caused by the json parser expecting a boolean and got a one..

I only noticed this on a linux platform.