All my wus (on Windows 11 64bit) are errors after few seconds:

<core_client_version>7.16.20</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code 195 (0xc3)</message>
<stderr_txt>
17:43:26 (21320): wrapper (7.7.26016): starting
17:43:26 (21320): wrapper: running ../../projects/boinc.loda-lang.org_loda/loda-220512-windows.exe (boinc -H 4)
17:43:27 (21320): loda exited; CPU time 0.015625
17:43:27 (21320): app exit status: 0xc0000409
17:43:27 (21320): called boinc_finish(195)

You need Git for Windows. Do you have it installed?

https://git-scm.com/download/win

Have also posted in getting started session.

BOINC 7.19.0
Ubuntu 22.04
Git 2.34.1

Don't know what other information you might need System is AuthenticAMD
AMD Ryzen 7 3700X 8-Core Processor [Family 23 Model 113 Stepping 0]
(16 processors) with 32GB RAM

Perhaps I am not understanding, the instructions here do I need to carry out those steps whatever or only if participating directly and not through BOINC? possibly relevant to OP?

Edit: trying to carry out instructions I get

curl -fsSLo loda https://github.com/loda-lang/loda-cpp/releases/latest/download/$LODA_EXEC
curl: (22) The requested URL returned error: 404

You don't need to manually install LODA. All you need is git.

Can you please check if /tmp is writable?

You don't need to manually install LODA. All you need is git.

Can you please check if /tmp is writable?

Owner root.
others Read&write.

Edit: I think of myself as a reasonably competent Linux user. I compiled BOINC from source and am one of the testing crew/moderators over at CPDN but know I still have a lot to learn about some aspects of BOINC. But do feel free to treat me as if I know nothing!

You don't need to manually install LODA. All you need is git.

Thanks. I assumed that was the case but thought I should check!

I also have all my tasks ending with an error after a few seconds.

Ubuntu 22.04 LTS
git version 2.34.1
AMD Ryzen 5 1600X Six-Core Processor

<core_client_version>7.18.1</core_client_version>
<![CDATA[
<message>
process exited with code 195 (0xc3, -61)</message>
<stderr_txt>
23:18:47 (49788): wrapper (7.5.26014): starting
23:18:47 (49788): wrapper: running ../../projects/boinc.loda-lang.org_loda/loda-220513-linux-x86 (boinc -H 4)
23:18:56 (49788): loda exited; CPU time 5.890697
23:18:56 (49788): app exit status: 0x86
23:18:56 (49788): called boinc_finish(195)

</stderr_txt>
]]>

Windows 11 Pro
Git for Windows v2.36.1
Intel i9-10850

My first two tasks failed after five and 3 minutes. I restarted the computer and 20 tasks are running beyond 40 minutes.

I have posted on the BOINC forums and it seems BOINC does not have write access to /tmp. I ran

 systemctl cat boinc-client.service

and the output included

 ProtectSystem=strict
ReadWritePaths=-/var/lib/boinc -/etc/boinc-client

And was told this:

That configuration makes the system read-only for BOINC, with few implicit or explicit exceptions. /tmp is none of those. You could override the configuration to allow /tmp but that would have to be done for every client. Or you could make the application developers aware that they are effectively restricted to the BOINC data directory.

For the average user instructions on how to override the configuration file will be needed but even if you provide these you will get a significant (possibly even a majority of users on Linux) who are set and forget so will crash a large number of tasks. CPDN has this problem with respect to 32bit libraries needed on Linux.

I used

 sudo systemctl edit boinc-client.service

to add /tmp to the read write paths.

Tasks running for longer 4 seconds instead of 1.something cpu time and around 50 seconds run time but still failing with

 195 (0x000000C3) EXIT_CHILD_FAILED

Edit: next stage might be to try it in a vm and change the line

ProtectSystem=strict

I still see the same error:

2022-05-14 07:41:14|INFO |Starting LODA v22.5.13. See https://loda-lang.org/
2022-05-14 07:41:14|INFO |Platform: linux-x86, user name: Catchercradle
2022-05-14 07:41:14|INFO |Using LODA home directory "/var/lib/boinc-client/projects/boinc.loda-lang.org_loda/"
2022-05-14 07:41:14|INFO |Loading sequences from the OEIS index
2022-05-14 07:41:16|INFO |Loaded 332578/353581 sequences in 1.58s
2022-05-14 07:42:00|INFO |Generating program stats at "/var/lib/boinc-client/projects/boinc.loda-lang.org_loda/stats/"
sh: 1: cannot create /tmp/loda_git_tmp.txt: Read-only file system
2022-05-14 07:42:03|INFO |PATH=
2022-05-14 07:42:03|ERROR|Error executing command (exit code 512): git -C "/var/lib/boinc-client/projects/boinc.loda-lang.org_loda/programs/" log --oneline --format="%H" -n 100 > /tmp/loda_git_tmp.txt
terminate called after throwing an instance of 'std::runtime_error'
  what():  Error executing command (exit code 512): git -C "/var/lib/boinc-client/projects/boinc.loda-lang.org_loda/programs/" log --oneline --format="%H" -n 100 > /tmp/loda_git_tmp.txt

I will try to make these logs available on the website.

Now trying in a VM where I feel a little safer making some changes.

Still the same problem despite having removed the line

ProtectSystem=strict

I suspect there is something I don't understand about how to allow BOINC access to /tmp

dthonon: you have the same problem as Catchercradle: /tmp is not writable

Vester: your miners seem to work. I have seen many results already

I installed git for windows (accepting) all of the default questions during installation and my first task ran through what appears to be a full process time with an exit status error 195.

Environment Win 10 fully up to date.

Task 21798
Name wu_1652470802_5825_0
Workunit 9875
Created 14 May 2022, 1:19:58 UTC
Sent 14 May 2022, 1:26:28 UTC
Report deadline 21 May 2022, 1:26:28 UTC
Received 14 May 2022, 6:44:00 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status 195 (0x000000C3) EXIT_CHILD_FAILED
Computer ID 74
Run time 2 hours 34 min 17 sec
CPU time 1 hours 28 min 3 sec
Validate state Invalid
Credit 0.00
Device peak FLOPS 3.22 GFLOPS
Application version LODA v2205.13
windows_x86_64
Peak working set size 605.41 MB
Peak swap size 885.24 MB
Peak disk usage 0.05 MB
Stderr output

<core_client_version>7.16.20</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code 195 (0xc3)</message>
<stderr_txt>
20:43:25 (11484): wrapper (7.7.26016): starting
20:43:25 (11484): wrapper: running ../../projects/boinc.loda-lang.org_loda/loda-220513-windows.exe (boinc -H 4)
00:43:20 (11484): loda exited; CPU time 5283.906250
00:43:20 (11484): app exit status: 0xc0000409
00:43:20 (11484): called boinc_finish(195)

</stderr_txt>
]]>

I have in the vm added boinc to the root user group to see if that makes any difference but will have to wait till boinc communicates with the servers again.

I can prepare a new app version that uses the project dir as fallback

I have in the vm added boinc to the root user group to see if that makes any difference but will have to wait till boinc communicates with the servers again.

Still all crashing with the same error. ran

~$ systemctl cat boinc-client.service

again and the same lines are still in the output so it clearly hasn't allowed write permission to the directory.

Catchercradle, dthonon: I published a new app version (220514) which uses the project dir as fallback if /tmp is not writable.

(unknown error) - exit code 195 (0xc3)

under Windows 10 64-bit (of course) and BOINC 7.16.20

app version : LODA v2205.14 windows_x86_64

7 tasks, 7 erros in a row. It makes me feel ashame.

(just so you know)

micropro