It seems that tasks can only be successfully completed on Linux and Darwin now.

My computer's operating system is Windows 11 and BOINC versions 8.0.2 and 8.0.4 have been used. For some reason, adding LODA and running it makes BOINC Manager stuck. Some operations such as updating projects and adjusting usage will bring up a dialog box saying ‘connect to BOINC Manager’, which will be stuck for a while. This won't happen even if I add all the projects besides LODA. It's back to normal after removing LODA.

Does anyone know the cause of these problems?

I have the same problem on windows10

When you look at the date of the application it shows that a new version was released on 31 january. Seems that this has a bug.

Hi Henk,
I found the following error in your logs:

2025-02-05 15:36:11|WARN |Retrying fetch of https://api.loda-lang.org/miner/v1/oeis/b189229.txt.gz
curl: (35) schannel: next InitializeSecurityContext failed: CRYPT_E_NO_REVOCATION_CHECK (0x80092012) - De intrekkingsfunctie kan het intrekken van het certificaat niet controleren.
...
2025-02-05 15:41:12|ERROR|Error fetching https://api.loda-lang.org/miner/v1/oeis/b189229.txt.gz
2025-02-05 15:41:12|ERROR|Error during initialization or mining: Error fetching https://api.loda-lang.org/miner/v1/oeis/b189229.txt.gz

We enabled secure communication to the API server in the latest app version.
There seems to be a problem with the root CA certificates on your machine (might be outdated).
Can you try to run this command in a terminal:

curl https://api.loda-lang.org/miner/v1/count

Hi Henk,
I found the following error in your logs:

2025-02-05 15:36:11|WARN |Retrying fetch of https://api.loda-lang.org/miner/v1/oeis/b189229.txt.gz
curl: (35) schannel: next InitializeSecurityContext failed: CRYPT_E_NO_REVOCATION_CHECK (0x80092012) - De intrekkingsfunctie kan het intrekken van het certificaat niet controleren.
...
2025-02-05 15:41:12|ERROR|Error fetching https://api.loda-lang.org/miner/v1/oeis/b189229.txt.gz
2025-02-05 15:41:12|ERROR|Error during initialization or mining: Error fetching https://api.loda-lang.org/miner/v1/oeis/b189229.txt.gz

We enabled secure communication to the API server in the latest app version.
There seems to be a problem with the root CA certificates on your machine (might be outdated).
Can you try to run this command in a terminal:

curl https://api.loda-lang.org/miner/v1/count

I have made the check and get the respons you already found in the log.
What do I need to do to fix this?

Hi Henk,
I found the following error in your logs:

2025-02-05 15:36:11|WARN |Retrying fetch of https://api.loda-lang.org/miner/v1/oeis/b189229.txt.gz
curl: (35) schannel: next InitializeSecurityContext failed: CRYPT_E_NO_REVOCATION_CHECK (0x80092012) - De intrekkingsfunctie kan het intrekken van het certificaat niet controleren.
...
2025-02-05 15:41:12|ERROR|Error fetching https://api.loda-lang.org/miner/v1/oeis/b189229.txt.gz
2025-02-05 15:41:12|ERROR|Error during initialization or mining: Error fetching https://api.loda-lang.org/miner/v1/oeis/b189229.txt.gz

We enabled secure communication to the API server in the latest app version.
There seems to be a problem with the root CA certificates on your machine (might be outdated).
Can you try to run this command in a terminal:

curl https://api.loda-lang.org/miner/v1/count

I have made the check and get the respons you already found in the log.
What do I need to do to fix this?

I have done a bit more thinking about this and started to wonder if this is this real problem.

I run most of the active BOINC projects and none have this error. In fact I show no errors on any program or application that I run on my host.

That leads to the question why is this important for LODA?

I am clearly not the only one who has this problem so even if I am able to fix this it is fixed for only my host

I think you shoud have a new look at your server stetup and /or application or need to provide the needed certificate for this secure communication.

Which Windows version do you use? And what is the output of "curl --version" ?

Which Windows version do you use? And what is the output of "curl --version" ?

Windows 10 Home version 22H2 build 19045.5440

curl 8.9.1 (Windows) libcurl/8.9.1 Schannel zlib/1.3 WinIDN
Release-Date: 2024-07-31
Protocols: dict file ftp ftps http https imap imaps ipfs ipns mqtt pop3 pop3s smb smbs smtp smtps telnet tftp
Features: alt-svc AsynchDNS HSTS HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM SPNEGO SSL SSPI threadsafe Unicode UnixSockets

Microsoft Windows 11 Pro for Workstations x64 Edition 24H2, 26120.3073, (10.00.26120.00)

curl 8.10.1 (Windows) libcurl/8.10.1 Schannel zlib/1.3 WinIDN
Release-Date: 2024-09-18
Protocols: dict file ftp ftps http https imap imaps ipfs ipns mqtt pop3 pop3s smb smbs smtp smtps telnet tftp
Features: alt-svc AsynchDNS HSTS HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM SPNEGO SSL SSPI threadsafe Unicode UnixSockets

Also, I noticed that "CPU does not have hardware virtualization support" was displayed on the Details page of my computer. But another project, LHC@home, says "CPU has hardware virtualization support and it is enabled".

Which Windows version do you use? And what is the output of "curl --version" ?

Windows 10 Home version 22H2 build 19045.5440

curl 8.9.1 (Windows) libcurl/8.9.1 Schannel zlib/1.3 WinIDN
Release-Date: 2024-07-31
Protocols: dict file ftp ftps http https imap imaps ipfs ipns mqtt pop3 pop3s smb smbs smtp smtps telnet tftp
Features: alt-svc AsynchDNS HSTS HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM SPNEGO SSL SSPI threadsafe Unicode UnixSockets

I had to reboot my systeem an noticed this in the startup log for Boinc

12/02/2025 09:18:32 | | Libraries: libcurl/8.7.0-DEV Schannel zlib/1.3.1

It shows a lower version of libcurl

Which Windows version do you use? And what is the output of "curl --version" ?

Windows 10 Home version 22H2 build 19045.5440

curl 8.9.1 (Windows) libcurl/8.9.1 Schannel zlib/1.3 WinIDN
Release-Date: 2024-07-31
Protocols: dict file ftp ftps http https imap imaps ipfs ipns mqtt pop3 pop3s smb smbs smtp smtps telnet tftp
Features: alt-svc AsynchDNS HSTS HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM SPNEGO SSL SSPI threadsafe Unicode UnixSockets

My Win10 Pro pc with the same version of curl you have fails on every task as well!

I noticed that there was a new version of the application so I let BOINC do a bit of LODA work.

The new version is not a success in fixing the 195 (0x000000C3) EXIT_CHILD_FAILED error.

PS. It would have been nice if a announcement had been made that there was a new version of the application.

I noticed that there was a new version of the application so I let BOINC do a bit of LODA work.

The new version is not a success in fixing the 195 (0x000000C3) EXIT_CHILD_FAILED error.

PS. It would have been nice if a announcement had been made that there was a new version of the application.

Add-on to this post.

I had another WU running and that one did end just fine.
I need to do a bit more testing because it seems to be that no longer every WU ends in a error.
Now to figure out what is the difference.

I think I have figured out wat is happening and it is strange.

If a WU is started and runs without an interupt it ends in Error
If a WU is started and then I Suspend my system including a power down, it wil after the resume run to the end and is Valid.

Whatever de application is doing there seems to be a difference in what is done at the start of a WU and what is done on a resume.

Which Windows version do you use? And what is the output of "curl --version" ?

One thought here: if you were to add to the Applications line for Windows that 'git-hub' is required it would make it easier for more people to join your Project. And then maybe add a Forum Board with a link to the one you prefer so at least most people are trying to use what you want them to use resulting in fewer problems. Remember most people are newbies to Boinc let alone 'git-hub' .

mikey

---