Hi i just had a lot of wu's take about 8 secs to run i handed them in and they are invalid im running Ubuntu 21.04 here is the report :

<core_client_version>7.16.16</core_client_version>
<![CDATA[
<stderr_txt>
19:49:21 (537864): wrapper (7.5.26014): starting
19:49:21 (537864): wrapper: running worker.sh ()
Jobs starts with 1 cores
STEP OPT : Starting
Create output archive
OPT.out
Normal termination.
19:49:23 (537864): worker.sh exited; CPU time 1.052591
19:49:23 (537864): called boinc_finish(0)
taskset: failed to set pid 521597's affinity: Operation not permitted
taskset: failed to set pid 521603's affinity: Operation not permitted
taskset: failed to set pid 521619's affinity: Operation not permitted
taskset: failed to set pid 521644's affinity: Operation not permitted
taskset: failed to set pid 521662's affinity: Operation not permitted
taskset: failed to set pid 521748's affinity: Operation not permitted
taskset: failed to set pid 521763's affinity: Operation not permitted
taskset: failed to set pid 521782's affinity: Operation not permitted
taskset: failed to set pid 521783's affinity: Operation not permitted
taskset: failed to set pid 521792's affinity: Operation not permitted
taskset: failed to set pid 521843's affinity: Operation not permitted
taskset: failed to set pid 521951's affinity: Operation not permitted
taskset: failed to set pid 522059's affinity: Operation not permitted
taskset: failed to set pid 522131's affinity: Operation not permitted
taskset: failed to set pid 522168's affinity: Operation not permitted
taskset: failed to set pid 522176's affinity: Operation not permitted
taskset: failed to set pid 522200's affinity: Operation not permitted
taskset: failed to set pid 522205's affinity: Operation not permitted
taskset: failed to set pid 522227's affinity: Operation not permitted
taskset: failed to set pid 522235's affinity: Operation not permitted

</stderr_txt>
]]>

Any help would be great thanks

I have 45 waiting for validation and 47 inconclusive validatio on my Windows 10 PC.
Tullio

---

The error messages for affinity are normal since the execution is finished
For the short jobs, it is a know issue. Many users experiment this error with recent Linux distribution (ubuntu >=20.04 and Debian 11)
I suspect changes in the kernel or library but at the moment, we have no engineer and no time...

Any news on this issue?
I did just the update to debian 11 and get this error for this machine now too
Like previous on Ubuntu 21.10
Thanks in advance

I've stopped getting new work on this machine

---

Matthias

For linux users , it is advised to download Boinc through the distro repository of their own distro.
It is more secure.
Don't use neither the boinc installer of the boinc site , nor the personal package archive (ppa) costamagnagianfranco-ppa.
Thus , you will avoid incompatibility between the boinc code and the libraries needed.
The drawback is that you will crunch with a lower or equal version than the latest displayed on the boinc site .
But more important is that the behavior of boinc is correct to not discourage users.

So , unistall boinc and follow this piece of advice to install it once again.

Give us feedback to inform us of the success or the fail of this process.

To fix this issue, I edited the file /lib/systemd/system/boinc-client.service and replaced ProtectSystem=strict by ProtectSystem=full

systemctl stop boinc-client
sed -i 's/ProtectSystem=strict/ProtectSystem=full/g' /lib/systemd/system/boinc-client.service
systemctl daemon-reload
systemctl start boinc-client

Give us feedback to inform us of the success or the fail of this process.

At the moment, I am using BOINC 7.16.17 from ppa:costamagnagianfranco/boinc
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/boinc

It is running fine on Ubuntu 20.04.3.
On some versions there is an incompatibility with the libraries, and going back to the Ubuntu Software version usually fixes it.

Hello Philippe,
since some years I only use only the linux distros boinc package.
But I try the change for the boinc-client.service
I'll keep you informed about the outcome

---

Matthias

Looks like with "ProtectSystem=full" is working for me too
I now have a new task running on my debian 11 system wit a runtime with more than 10 minutes

Bot my Ubuntu 20.04.3 LTS also has the setting ProtectSystem=strict
So there is some change needed for quchem application to work with ProtectSystem=strict on newer linux systems

---

Matthias

ProtectSystem=full works on both machines (debian 11 and Ubuntu 21.10)
On debian I have the first valid result and all new results have a normal runtime
On Ubuntu the first result is uploaded too with a normal runtime

---

Matthias

No problems using Fedora 31 and the next to latest BOINC client version from the BOINC download website.

I much prefer the BOINC website downloads as it allows more control where things are on my computer and it works fine.
I have another computer with the Fedora 34 and latest BOINC client on it but have not run this project on it to see if it works (it probably needs hardware upgrades before software is an issue).

Conan

just checked my results on Fedora Linux 35 (Workstation Edition)
Works fine too with boinc 7.16.11 from Fedora Packages
and with default setting ProtectSystem=strict

---

Matthias

it works!