1) Message boards : ATLAS application : Best number of cores on a 16 core machine to use for ATLAS (Message 44860)
Posted 2 May 2021 by Aurum
Post:
what is the best use for a single task?
One.
2) Message boards : ATLAS application : Ubuntu 20.04 support? (Message 44819)
Posted 25 Apr 2021 by Aurum
Post:
I have go version 1.15.2, which works fine.
You read mind, I was wondering which Go version you used. I've tried Go 1.16.3, 1.14.15 and 1.14.1. None of them worked.
I also downgraded Singularity from 3.7.3 to 3.6.4 that you used. Still fails.
And all this time wasted just because a muon did a dance.

The release notes indicate that Singularity has been upgraded to fix security issues. It's a shame that CERN is so far behind.

Maybe he can figure out how to uninstall one version and get another.
"If you anticipate needing to remove Singularity, it might be easier to install it in a custom directory using the --prefix option to mconfig. In that case Singularity can be uninstalled simply by deleting the parent directory."
https://sylabs.io/guides/3.7/admin-guide/installation.html#remove-an-old-version
I just deleted my Singularity folder although in rereading the Sylabs instructions that may not have been sufficient.
My notes show last year's installation used the --prefix option:
sudo mkdir /usr/local/bin/singularity ; /
cd /usr/local/bin/singularity ; /
sudo wget https://github.com/hpcng/singularity/releases/tag/v3.7.3/singularity-3.7.3.tar.gz ; /
tar xvf singularity-3.7.3.tar.gz ; /
sudo apt install libarchive-dev ; /
./configure --prefix=/usr/local ; /
make ; /
sudo make install
This year's instructions say:
cd /usr/local/bin
export VERSION=3.6.4 && # adjust this as necessary \
    sudo wget https://github.com/hpcng/singularity/releases/download/v${VERSION}/singularity-${VERSION}.tar.gz && \
    sudo tar -xzf singularity-${VERSION}.tar.gz
cd /usr/local/bin/singularity
sudo -s 
./mconfig && \
    make -C builddir && \
    make -C builddir install
I added cd /usr/local/bin so it wasn't installed in my Home directory as the CERN instructions specify.
I would be willing to try a fresh install on a new-build computer that has never been tainted by an LHC@home attachment. But the ambiguity and contradictions have overwhelmed me.
https://lhcathome.cern.ch/lhcathome/result.php?resultid=315423475
3) Message boards : ATLAS application : Ubuntu 20.04 support? (Message 44816)
Posted 25 Apr 2021 by Aurum
Post:
Tried running an ATLAS WU but it failed at about 1%:
[2021-04-25 03:37:21] Using singularity image /cvmfs/atlas.cern.ch/repo/containers/images/singularity/x86_64-centos7.img
[2021-04-25 03:37:21] Checking for singularity binary...
[2021-04-25 03:37:21] Singularity is not installed, using version from CVMFS
[2021-04-25 03:37:21] Checking singularity works with /cvmfs/atlas.cern.ch/repo/containers/sw/singularity/x86_64-el7/current/bin/singularity exec -B /cvmfs /cvmfs/atlas.cern.ch/repo/containers/images/singularity/x86_64-centos7.img hostname
[2021-04-25 03:37:24] INFO: Converting SIF file to temporary sandbox... Rig-48 INFO: Cleaning up image...
[2021-04-25 03:37:24] Singularity works
[2021-04-25 03:37:24] Starting ATLAS job with PandaID=5037675747
[2021-04-25 03:37:24] Running command: /cvmfs/atlas.cern.ch/repo/containers/sw/singularity/x86_64-el7/current/bin/singularity exec --pwd /var/lib/boinc-client/slots/2 -B /cvmfs,/var /cvmfs/atlas.cern.ch/repo/containers/images/singularity/x86_64-centos7.img sh start_atlas.sh
[2021-04-25 03:37:26] Job failed
[2021-04-25 03:37:26] INFO:    Converting SIF file to temporary sandbox...
[2021-04-25 03:37:26] INFO:    Cleaning up image...
[2021-04-25 03:37:26] FATAL:   container creation failed: hook function for tag prelayer returns error: failed to create /var/lib/alternatives directory: mkdir /var/lib/alternatives: read-only file system
[2021-04-25 03:37:26] ./runtime_log.err
[2021-04-25 03:37:26] ./runtime_log
03:47:26 (4413): run_atlas exited; CPU time 17.180037
03:47:26 (4413): app exit status: 0x1
03:47:26 (4413): called boinc_finish(195)
4) Message boards : ATLAS application : Ubuntu 20.04 support? (Message 44815)
Posted 25 Apr 2021 by Aurum
Post:
I can't get it to install. Fails here:
root@Rig-48:/usr/local/bin/singularity# ./mconfig && \
>     make -C builddir && \
>     make -C builddir install
Configuring for project `singularity' with languages: C, Golang
=> running pre-basechecks project specific checks ...
=> running base system checks ...
 checking: host C compiler... cc
 checking: host C++ compiler... c++
 checking: host Go compiler (at least version 1.13)... not found!
mconfig: could not complete configuration
Even though
aurum@Rig-48:~$ go version
go version go1.16.3 linux/amd64
I don't have the foggiest idea what to try now. Any suggestions??? TIA
5) Message boards : ATLAS application : Ubuntu 20.04 support? (Message 44812)
Posted 25 Apr 2021 by Aurum
Post:
what do you get when you run "singularity --version"?

$ singularity --version
Command 'singularity' not found, but can be installed with:
sudo apt install singularity
6) Message boards : ATLAS application : Ubuntu 20.04 support? (Message 44810)
Posted 24 Apr 2021 by Aurum
Post:
It seems odd that CERN is sending me an image for a different operating system???
[2021-04-24 13:21:36] Checking singularity works with /cvmfs/atlas.cern.ch/repo/containers/sw/singularity/x86_64-el7/current/bin/singularity exec -B /cvmfs /cvmfs/atlas.cern.ch/repo/containers/images/singularity/x86_64-centos7.img hostname

Why send a CENTOS7 image to a Ubuntu computer???
7) Message boards : Number crunching : Recommended CVMFS Configuration for Native Apps - Comments and Questions (Message 44809)
Posted 24 Apr 2021 by Aurum
Post:
What does this mean???
cvmfs_config stat
/usr/bin/cvmfs_config: line 907: cd: /cvmfs/atlas.cern.ch: Transport endpoint is not connected
8) Message boards : ATLAS application : Ubuntu 20.04 support? (Message 44808)
Posted 24 Apr 2021 by Aurum
Post:
I added those and it still fails.
<core_client_version>7.16.6</core_client_version>
<![CDATA[
<message>
process exited with code 195 (0xc3, -61)</message>
<stderr_txt>
09:59:55 (52264): wrapper (7.7.26015): starting
09:59:55 (52264): wrapper: running run_atlas (--nthreads 1)
[2021-04-24 09:59:55] Arguments: --nthreads 1
[2021-04-24 09:59:55] Threads: 1
[2021-04-24 09:59:55] Checking for CVMFS
[2021-04-24 09:59:58] Probing /cvmfs/atlas.cern.ch... OK
[2021-04-24 10:00:00] Probing /cvmfs/atlas-condb.cern.ch... OK
[2021-04-24 10:00:01] Probing /cvmfs/grid.cern.ch... OK
[2021-04-24 10:00:02] Probing /cvmfs/cernvm-prod.cern.ch... OK
[2021-04-24 10:00:02] Probing /cvmfs/grid.cern.ch... OK
[2021-04-24 10:00:03] Probing /cvmfs/sft.cern.ch... OK
[2021-04-24 10:00:04] Probing /cvmfs/alice.cern.ch... OK
[2021-04-24 10:00:05] VERSION PID UPTIME(M) MEM(K) REVISION EXPIRES(M) NOCATALOGS CACHEUSE(K) CACHEMAX(K) NOFDUSE NOFDMAX NOIOERR NOOPEN HITRATE(%) RX(K) SPEED(K/S) HOST PROXY ONLINE
[2021-04-24 10:00:05] 2.8.1.0 52564 0 24632 83323 3 1 473981 4194304 0 130560 0 0 100.000 0 0 http://s1unl-cvmfs.openhtc.io/cvmfs/atlas.cern.ch DIRECT 1
[2021-04-24 10:00:05] CVMFS is ok
[2021-04-24 10:00:05] Using singularity image /cvmfs/atlas.cern.ch/repo/containers/images/singularity/x86_64-centos7.img
[2021-04-24 10:00:05] Checking for singularity binary...
[2021-04-24 10:00:05] Singularity is not installed, using version from CVMFS
[2021-04-24 10:00:05] Checking singularity works with /cvmfs/atlas.cern.ch/repo/containers/sw/singularity/x86_64-el7/current/bin/singularity exec -B /cvmfs /cvmfs/atlas.cern.ch/repo/containers/images/singularity/x86_64-centos7.img hostname
[2021-04-24 10:00:10] INFO: Converting SIF file to temporary sandbox... Rig-46 INFO: Cleaning up image...
[2021-04-24 10:00:10] Singularity works
[2021-04-24 10:00:10] Starting ATLAS job with PandaID=5035383237
[2021-04-24 10:00:10] Running command: /cvmfs/atlas.cern.ch/repo/containers/sw/singularity/x86_64-el7/current/bin/singularity exec --pwd /var/lib/boinc-client/slots/35 -B /cvmfs,/var /cvmfs/atlas.cern.ch/repo/containers/images/singularity/x86_64-centos7.img sh start_atlas.sh
[2021-04-24 10:00:17] Job failed
[2021-04-24 10:00:17] INFO:    Converting SIF file to temporary sandbox...
[2021-04-24 10:00:17] INFO:    Cleaning up image...
[2021-04-24 10:00:17] FATAL:   container creation failed: hook function for tag prelayer returns error: failed to create /var/lib/alternatives directory: mkdir /var/lib/alternatives: read-only file system
[2021-04-24 10:00:17] ./runtime_log
[2021-04-24 10:00:17] ./runtime_log.err
10:10:17 (52264): run_atlas exited; CPU time 11.489694
10:10:17 (52264): app exit status: 0x1
10:10:17 (52264): called boinc_finish(195)
</stderr_txt>
9) Message boards : ATLAS application : Creation of container failed (Message 44807)
Posted 24 Apr 2021 by Aurum
Post:
Failed again. A perfect record: 100% failures for ATLAS.
[2021-04-24 09:34:41] Using singularity image /cvmfs/atlas.cern.ch/repo/containers/images/singularity/x86_64-centos7.img
[2021-04-24 09:34:41] Checking for singularity binary...
[2021-04-24 09:34:41] Singularity is not installed, using version from CVMFS
[2021-04-24 09:34:41] Checking singularity works with /cvmfs/atlas.cern.ch/repo/containers/sw/singularity/x86_64-el7/current/bin/singularity exec -B /cvmfs /cvmfs/atlas.cern.ch/repo/containers/images/singularity/x86_64-centos7.img hostname
[2021-04-24 09:34:42] Singularity isnt working: INFO:    Converting SIF file to temporary sandbox...
[2021-04-24 09:34:42] FATAL:   while extracting /cvmfs/atlas.cern.ch/repo/containers/images/singularity/x86_64-centos7.img: root filesystem extraction failed: extract command failed: WARNING: passwd file doesn't exist in container, not updating
[2021-04-24 09:34:42] WARNING: group file doesn't exist in container, not updating
[2021-04-24 09:34:42] WARNING: Skipping mount /etc/hosts [binds]: /etc/hosts doesn't exist in container
[2021-04-24 09:34:42] WARNING: Skipping mount /etc/localtime [binds]: /etc/localtime doesn't exist in container
[2021-04-24 09:34:42] WARNING: Skipping mount proc [kernel]: /proc doesn't exist in container
[2021-04-24 09:34:42] WARNING: Skipping mount /cvmfs/atlas.cern.ch/repo/containers/sw/singularity/x86_64-el7/3.7.2/var/singularity/mnt/session/tmp [tmp]: /tmp doesn't exist in container
[2021-04-24 09:34:42] WARNING: Skipping mount /cvmfs/atlas.cern.ch/repo/containers/sw/singularity/x86_64-el7/3.7.2/var/singularity/mnt/session/var/tmp [tmp]: /var/tmp doesn't exist in container
[2021-04-24 09:34:42] WARNING: Skipping mount /cvmfs/atlas.cern.ch/repo/containers/sw/singularity/x86_64-el7/3.7.2/var/singularity/mnt/session/etc/resolv.conf [files]: /etc/resolv.conf doesn't exist in container
[2021-04-24 09:34:42] 
[2021-04-24 09:34:42] FATAL ERROR:write_file: failed to create file /image/root/usr/include/c++/4.8.2/ext/pb_ds/detail/cc_hash_table_map_/erase_fn_imps.hpp, because Too many open files
[2021-04-24 09:34:42] Parallel unsquashfs: Using 36 processors
[2021-04-24 09:34:42] 41269 inodes (41434 blocks) to write
[2021-04-24 09:34:42] 
[2021-04-24 09:34:42] : exit status 1
09:44:43 (47648): run_atlas exited; CPU time 1.082061
09:44:43 (47648): app exit status: 0x1
09:44:43 (47648): called boinc_finish(195)
</stderr_txt>
10) Message boards : ATLAS application : Creation of container failed (Message 44806)
Posted 24 Apr 2021 by Aurum
Post:
The feedback I got said there was a configuration change related to setuid in the latest singularity, and he pointed me to this page.

I didn't try to install a local singularity but I did try to:
openSUSE and SUSE have a small difference with upstream default. 
This means the SUID root binaries distributed by singularity are executable only by users belonging to the group 'singularity'.
Otherwise, users will get an error message like this one:
FATAL:   while executing /usr/lib/singularity/bin/starter-suid: permission denied
To add a user to the group singularity, execute (as root):
 # usermod -a -G singularity <user_login>
But when I execute:
sudo usermod -a -G singularity aurum
It responds with:
usermod: group 'singularity' does not exist

Ok, trying again:
sudo groupadd singularity
sudo usermod -a -G singularity aurum
Ok, so far so good. Just broke 1.1% which is first.
11) Message boards : ATLAS application : Ubuntu 20.04 support? (Message 44804)
Posted 24 Apr 2021 by Aurum
Post:
Regarding the cvmfs 18.04 packages: they are selected by the cvmfs-release package, which is responsible for picking a suitable package repository. It uses
lsb-release
to figure out where it runs. Officially, only the Ubuntu LTS releases are supported. So, "focal" is a recognized release but "ulyssa" is not. For unsupported distributions, the cvmfs-release tries to fall back to a package repository with compatible binaries. In this case, it picks the repository with the 18.04 binaries. While somewhat less than perfect, these binaries should nevertheless work fine on Mint 20, so there is nothing to worry about.

That's not the issue. The issue is that LHC ATLAS Fails 100% of the time. What are the correct instructions to make ATLAS run Linux native WUs???

Here's what I'm trying:

wget https://ecsft.cern.ch/dist/cvmfs/cvmfs-release/cvmfs-release-latest_all.deb ; \
sudo dpkg -i cvmfs-release-latest_all.deb ; \
rm -f cvmfs-release-latest_all.deb ; \
sudo apt-get update ; \
sudo apt-get install cvmfs ; \
sudo apt install glibc-doc open-iscsi watchdog

sudo wget https://lhcathomedev.cern.ch/lhcathome-dev/download/default.local -O /etc/cvmfs/default.local ; \
sudo cvmfs_config setup ; \
sudo echo "/cvmfs /etc/auto.cvmfs" > /etc/auto.master.d/cvmfs.autofs ; \
sudo systemctl restart autofs ; \
cvmfs_config probe

sudo xed /etc/cvmfs/default.local
CVMFS_REPOSITORIES=atlas.cern.ch,atlas-condb.cern.ch,grid.cern.ch,cernvm-prod.cern.ch,grid.cern.ch,sft.cern.ch,alice.cern.ch
CVMFS_QUOTA_LIMIT=4096
CVMFS_CACHE_BASE=/scratch/cvmfs
CVMFS_HTTP_PROXY=DIRECT
CVMFS_USE_CDN=yes
CVMFS_USE_GEOAPI=no

sudo xed /etc/cvmfs/domain.d/cern.ch.local
CVMFS_USE_GEOAPI=no

sudo cvmfs_config reload
12) Message boards : ATLAS application : Ubuntu 20.04 support? (Message 44626)
Posted 30 Mar 2021 by Aurum
Post:
Yes, unfortunately the CERN world is rather CentOS-centric and so other Linux flavours like Ubuntu don't work out of the box.
So the options for running ATLAS WU are (in rough order of increasing difficulty):
- Run the Vbox app
- Run a pre-made Docker container with no configuration required
- Set up a CentOS VM and run BOINC inside
- Install (compile if necessary) CVMFS and Singularity to run real native tasks
- Wipe Ubuntu and install CentOS 7 (just a joke :)
1. By definition ATLAS is NOT a native application and you should not call it one.
2. I will never run anything in a VirtualCatBox. I made that mistake before and I'll never do it again.
3. ATLAS ran fine for me before and most of the 37 million points I have here were running ATLAS but NOT in a VirtualCatBox.
4. I believe the current instructions are posted in more than one place and contradict themselves. Please clean up behind yourselves.
5. These were all the steps that it previously took to run ATLAS for Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic:
For new & reinstalls:
wget https://ecsft.cern.ch/dist/cvmfs/cvmfs-release/cvmfs-release-latest_all.deb ; \
 sudo dpkg -i cvmfs-release-latest_all.deb ; \
 rm -f cvmfs-release-latest_all.deb ; \
 sudo apt-get update ; \
 sudo apt-get install cvmfs ; \
 sudo apt install glibc-doc open-iscsi watchdog

sudo wget https://lhcathomedev.cern.ch/lhcathome-dev/download/default.local -O /etc/cvmfs/default.local ; \
 sudo cvmfs_config setup ; \
 sudo echo "/cvmfs /etc/auto.cvmfs" > /etc/auto.master.d/cvmfs.autofs ; \
 sudo systemctl restart autofs ; \
 cvmfs_config probe

sudo cvmfs_config reload

6. cvmfs is installed 2.8.0~1+ubuntu18.04 (50.4 MB).
7. It says fuse was installed yet earlier post indicates it's not there. Maybe there's a problem with what's in the Linux repository?
/.
/etc
/etc/auto.cvmfs
/etc/bash_completion.d
/etc/bash_completion.d/cvmfs
/etc/cvmfs
/etc/cvmfs/config.d
/etc/cvmfs/config.sh
/etc/cvmfs/default.conf
/etc/cvmfs/default.d
/etc/cvmfs/default.d/README
/sbin
/sbin/mount.cvmfs
/usr
/usr/bin
/usr/bin/cvmfs2
/usr/bin/cvmfs_config
/usr/bin/cvmfs_fsck
/usr/bin/cvmfs_talk
/usr/lib
/usr/lib/libcvmfs_fuse.so
/usr/lib/libcvmfs_fuse.so.2.8.0
/usr/lib/libcvmfs_fuse_debug.so
/usr/lib/libcvmfs_fuse_debug.so.2.8.0
/usr/lib/libcvmfs_fuse_stub.so
/usr/lib/libcvmfs_fuse_stub.so.2.8.0
/usr/libexec
/usr/libexec/cvmfs
/usr/libexec/cvmfs/authz
/usr/libexec/cvmfs/authz/cvmfs_allow_helper
/usr/libexec/cvmfs/authz/cvmfs_deny_helper
/usr/libexec/cvmfs/auto.cvmfs
/usr/libexec/cvmfs/cache
/usr/libexec/cvmfs/cache/cvmfs_cache_posix
/usr/libexec/cvmfs/cache/cvmfs_cache_ram
/usr/share
/usr/share/doc
/usr/share/doc/cvmfs
/usr/share/doc/cvmfs-2.8.0
/usr/share/doc/cvmfs-2.8.0/AUTHORS
/usr/share/doc/cvmfs-2.8.0/COPYING
/usr/share/doc/cvmfs-2.8.0/ChangeLog.gz
/usr/share/doc/cvmfs-2.8.0/README.md
/usr/share/doc/cvmfs/changelog.Debian.gz
/usr/share/doc/cvmfs/changelog.gz
/usr/share/doc/cvmfs/copyright
13) Message boards : ATLAS application : Ubuntu 20.04 support? (Message 44625)
Posted 30 Mar 2021 by Aurum
Post:
aurum@Rig-25:~$ dpkg -l |grep -i cvmfs
ii  cvmfs                                      2.8.0~1+ubuntu18.04                   amd64        CernVM File System
ii  cvmfs-config-default                       2.0-1                                 all          CernVM File System Default Configuration
ii  cvmfs-release                              3.2-1                                 all          This package contains the apt configuration for the CernVM File System packages.

Looks like I'm missing cvmfs-fuse3. Now if I can just figure out how to install that...
14) Message boards : ATLAS application : Ubuntu 20.04 support? (Message 44615)
Posted 30 Mar 2021 by Aurum
Post:
Failed saying no go compiler:
root@Rig-25:/home/aurum/singularity# ./mconfig && \
>     make -C builddir && \
>     sudo make -C builddir install
Configuring for project `singularity' with languages: C, Golang
=> running pre-basechecks project specific checks ...
=> running base system checks ...
 checking: host C compiler... cc
 checking: host C++ compiler... c++
 checking: host Go compiler (at least version 1.13)... not found!
mconfig: could not complete configuration


This is unimaginably complicated.
15) Message boards : ATLAS application : Ubuntu 20.04 support? (Message 44603)
Posted 30 Mar 2021 by Aurum
Post:
I can't get this command to work:
sudo snap install go --classic
sudo: snap: command not found

But when I search in the Synaptic Package Manager it shows I have snap installed.
SNAP is a general purpose gene finding program suitable for both eukaryotic and prokaryotic genomes. SNAP is an acronym for Semi-HMM-based Nucleic Acid Parser.

But when I search SPM for go there is no standalone program called go but there are thousands of programs containing go.
16) Message boards : ATLAS application : Ubuntu 20.04 support? (Message 44600)
Posted 29 Mar 2021 by Aurum
Post:
Haven't been here in a while. The instructions are far more complex and confusing than they were when I last ran ATLAS. Now every WU fails with computation error even though I passed cvmfs config probe.
When setting it up I get:
Setting up cvmfs-release (3.2-1) ...
Warning: this distribution is not supported. Using Ubuntu 18.04 packages as fallback.
I'm running Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal. Is this my problem that I have Ubuntu 20.04 ???

This is called a "native application" but it doesn't conform to the definition:
"Something running on a computer natively means that it is running without any external layer requiring fewer software layers."

In the instructions it says:
Docker Container
The CernVM-FS service container can expose the /cvmfs directory tree to the host. Import the container with
docker pull cvmfs/service
https://cvmfs.readthedocs.io/en/stable/cpt-quickstart.html#docker-container
To get this command to run I had to execute these 2 commands since I never use docker:
sudo apt install docker.io -y
sudo docker pull cvmfs/service
Do I need docker or not???

The previous instructions used this command but the current instructions don't mention it:
sudo apt install glibc-doc open-iscsi watchdog
When I follow the current instructions it said something about watchdog being recommended. I have synaptic options set to consider recommends as dependencies but watchdog and/or open-iscsi did not load. So I ran sudo apt install glibc-doc open-iscsi watchdog.
Is this needed or not???

This section is confusing since it tells me to do something that has already been done by:
sudo wget https://lhcathome.cern.ch/lhcathome/download/default.local -O /etc/cvmfs/default.local
CVMFS_REPOSITORIES="atlas,atlas-condb,grid,cernvm-prod,sft,alice"
So I took to mean I needed to open default.local and edit it and entered this which may be one of my problems:
CVMFS_REPOSITORIES=atlas.cern.ch,atlas-condb.cern.ch,grid.cern.ch
CVMFS_CLIENT_PROFILE=single
https://cvmfs.readthedocs.io/en/stable/cpt-quickstart.html#create-default-local
17) Message boards : Theory Application : Checkpointing (Message 43153)
Posted 31 Jul 2020 by Aurum
Post:
Running Theory (or ATLAS) native still requires lots of expert knownlege, additional settings and more babysitting.
They pay back more efficient tasks and less total RAM requirements, especially if many task run concurrently on a computer with many cores.

Volunteers who don't want to spend that additional work should run the vbox apps.
Not an answer to either of my questions.
18) Message boards : Theory Application : Checkpointing (Message 43151)
Posted 31 Jul 2020 by Aurum
Post:
With the so-called "native" Theory project is it still necessary to go through this rigmarole to even be able to suspend while still running BOINC client???

Last modified: 25 Mar 2019
https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=4971

Suspend/Resume
The Suspend/Resume does not work out of the box. It needs a cgroup to be created for each slot and this requires a cgroup with permissions for the user boinc. This can be provided by adding a PreStart script for boinc-client systemd. Download two files with wget:
sudo wget http://lhcathome.cern.ch/lhcathome/download/create-boinc-cgroup -O /sbin/create-boinc-cgroup
sudo wget http://lhcathome.cern.ch/lhcathome/download/boinc-client.service -O /etc/systemd/system/boinc-client.service
Then run the following commands to pick up the changes:
sudo systemctl daemon-reload
sudo systemctl restart boinc-client
This will only suspend the application in memory.
19) Message boards : Theory Application : Checkpointing (Message 43150)
Posted 31 Jul 2020 by Aurum
Post:
Does Theory still not have checkpointing for Linux???

Last modified: 25 Mar 2019
https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=4971

To suspend the application to disk so that it will survive the client exiting requires the container checkpointing feature.
However, this is not currently available for Linux containers.
20) Message boards : CMS Application : New Version 50.00 (Message 43128)
Posted 30 Jul 2020 by Aurum
Post:
Is there a native CMS now?


Next 20


©2021 CERN