LHC@home

So I've gone through the steps to install cvmfs on Debian Stretch and now boinc-client will not start.

I think I've traced the problem to "hugetbl" not being created under "/sys/fs/cgroup" by the "create-boinc-cgroup" script.
Is "hugetbl" to be create under the root of "/sys/fs/cgroup" or in another directory?

Some other info, the error I get from systemd when trying to start the client is:
boinc-client.service: Control process exited, code=exited status=210

Thanks for any pointers.

What OS do you have?

Debian Stretch, updated on May 13th and running kernel 4.9.168-1+deb9u2

Thanks.

Please could you let me know the output from running the following:

sudo /sbin/create-boinc-cgroup

Here is the output:

mkdir: cannot create directory '/sys/fs/cgroup/hugetlb': Read-only file system
chown: cannot access '/sys/fs/cgroup/hugetlb/boinc/': No such file or directory
chown: cannot access '/sys/fs/cgroup/hugetlb/boinc/cgroup.procs': No such file or directory
chown: cannot access '/sys/fs/cgroup/hugetlb/boinc/tasks': No such file or directory
chmod: cannot access '/sys/fs/cgroup/hugetlb/boinc/': No such file or directory
chmod: cannot access '/sys/fs/cgroup/hugetlb/boinc/cgroup.procs': No such file or directory
chmod: cannot access '/sys/fs/cgroup/hugetlb/boinc/tasks': No such file or directory

These are the only errors reported by the script, the other steps execute with no errors.

An update on the situation:

1. Starting the boinc client via systemctl fails with the earlier error as the script /sbin/create-boinc-group gets called
2. Starting the boinc client from within the boinc-client directory starts up with no errors and things work
3. Running cvmfs_config chksetup reports no errors

I am getting work units for TheoryN and they are completing.

On a slightly different tack: I am running Atlas via VirtualBox, would it be better to switch it to the native Linux now that cvmfs and TheoryN seem to be working?

Thanks.
Goni.

I am getting work units for TheoryN and they are completing.

Congrats!

On a slightly different tack: I am running Atlas via VirtualBox, would it be better to switch it to the native Linux now that cvmfs and TheoryN seem to be working?

Yes. The fact that BOINC won't start with systemctl is disconcerting but if native ATLAS works for you then by all means enjoy the benefits.

I am running Atlas via VirtualBox, would it be better to switch it to the native Linux now that cvmfs and TheoryN seem to be working?

ATLAS native will have a better efficiency. Up to 30 % compared to the vbox app.
The disadvantage would be that ATLAS native doesn't allow checkpointing.
This means if you pause the task without leaving it in memory or if you restart the BOINC client or reboot your computer all ATLAS native tasks would later restart from the scratch.
If you can live with that ATLAS native is the recommended app on Linux.

Preparing to test with ATLAS native, I followed the instructions on https://cvmfs.readthedocs.io/en/stable/cpt-quickstart.html

Linux Mint 20.3 'Mate' succeeded, but Linux Mint 21 'Mate' failed. Not entirely clear why, but the verification checks couldn't find cvmfs.

I had a similar problem trying to load BOINC v7.20.2 on Mint 21 using the LocutusOfBorg PPA. On that occasion, it reported that the security key validation/storage mechanisms had been tightened, and the key in the PPA could no longer be used - so I fell back to repo BOINC v7.18.1, which is running fine.

Just reporting for info.

using the LocutusOfBorg

Mate, that is your problem, Borg are untrustworthy and Borg Queen herself controls Locutus. :-)

I also had issues going from Ubuntu 20.04 to 22.04.