Message boards : Theory Application : Erreur systématique pendant le calcul ....
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile[AF>France>Ouest>Norm...

Send message
Joined: 13 Jul 05
Posts: 5
Credit: 319,128
RAC: 2,305
Message 53399 - Posted: 13 Apr 2026, 9:30:28 UTC

Bonjour,
Toutes les WU partent systématiquement en erreur au bout de quelques minutes.
Une idée ?
Bonne journée.
Bruno.
ID: 53399 · Report as offensive     Reply Quote
Toggleton

Send message
Joined: 4 Mar 17
Posts: 46
Credit: 13,036,976
RAC: 6,267
Message 53400 - Posted: 13 Apr 2026, 9:37:02 UTC - in response to Message 53399.  

We can't see your computer and the failed tasks. You need to set "Preferences for this project LHC@home preferences" -> Should LHC@home show your computers on its web site?

The logs of the tasks usually show where it failed.
ID: 53400 · Report as offensive     Reply Quote
Profile[AF>France>Ouest>Norm...

Send message
Joined: 13 Jul 05
Posts: 5
Credit: 319,128
RAC: 2,305
Message 53401 - Posted: 13 Apr 2026, 9:43:19 UTC - in response to Message 53400.  

Oups, c'est bon maintenant.
ID: 53401 · Report as offensive     Reply Quote
Profile[AF>France>Ouest>Norm...

Send message
Joined: 13 Jul 05
Posts: 5
Credit: 319,128
RAC: 2,305
Message 53403 - Posted: 13 Apr 2026, 17:03:41 UTC - in response to Message 53401.  

An exemple :

<core_client_version>8.2.9</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)</message>
<stderr_txt>
docker_wrapper 18 starting
docker_wrapper config:
workdir: /boinc_slot_dir
use GPU: no
create args: --cap-add=SYS_ADMIN --device /dev/fuse -v /cvmfs:/cvmfs:shared
verbose: 1
Using podman
running docker command: ps --all --filter "name=^boinc__lhcathome.cern.ch_lhcathome__theory_2922-4841152-759_1$" --format "{{.Names}}|{{.Status}}"
program: "/Library/Application Support/BOINC Data/Run_Podman" /opt/podman/bin/podman
zsh:1: parse error near `}'
command output:
creating container boinc__lhcathome.cern.ch_lhcathome__theory_2922-4841152-759_1
running docker command: images
program: "/Library/Application Support/BOINC Data/Run_Podman" /opt/podman/bin/podman
command output:
REPOSITORY TAG IMAGE ID CREATED SIZE
docker.io/library/4715b0856efc048351d3066475c82d1a891140205137df7d76fdb12700417520-tmp latest 8fef4b4f01cf 16 seconds ago 598 MB
docker.io/library/almalinux 9 4bf4f2bf0123 5 days ago 199 MB
building image
running docker command: build "/Library/Application\ Support/BOINC\ Data/slots/18" -t boinc__lhcathome.cern.ch_lhcathome__theory_2922-4841152-759 -f Dockerfile
program: "/Library/Application Support/BOINC Data/Run_Podman" /opt/podman/bin/podman
command output:
STEP 1/6: FROM almalinux:9
STEP 2/6: RUN dnf install -y https://cvmrepo.s3.cern.ch/cvmrepo/yum/cvmfs-release-latest.noarch.rpm && dnf install -y epel-release && dnf install -y libxcrypt-compat bc bzip2 lighttpd procps-ng make gcc which cvmfs bind-utils netcat zlib-devel compat-openssl11 freetype && dnf clean all
--> Using cache 8fef4b4f01cf41d331467fb673fc40be41405677c19ac162720b89c5a31dda60
--> 8fef4b4f01cf
STEP 3/6: RUN useradd -m boinc
--> Using cache e2d2d8ffad19c00605f3ec31820093a68fd1331b1b3e8553be4f3403d766c622
--> e2d2d8ffad19
STEP 4/6: EXPOSE 80
--> Using cache 04026ef62a9f5f5a2793f8be9113867307097250b328016602a705cbff8fa6d8
--> 04026ef62a9f
STEP 5/6: WORKDIR /boinc_slot_dir
--> Using cache 0278fca94fded639a5818a4b44b0052f5e78b91b1af56bead73bbbb87f2a6945
--> 0278fca94fde
STEP 6/6: CMD ./entrypoint.sh
--> Using cache c77819fca91b023fa996f301ecf2b154e750b4432774c1f71611ddd35d253669
COMMIT boinc__lhcathome.cern.ch_lhcathome__theory_2922-4841152-759
--> c77819fca91b
Successfully tagged localhost/boinc__lhcathome.cern.ch_lhcathome__theory_2922-4841152-759:latest
Successfully tagged localhost/boinc__lhcathome.cern.ch_lhcathome__theory_2922-4785187-834:latest
c77819fca91b023fa996f301ecf2b154e750b4432774c1f71611ddd35d253669
running docker command: create --name boinc__lhcathome.cern.ch_lhcathome__theory_2922-4841152-759_1 -v "/Library/Application\ Support/BOINC\ Data/slots/18/":"/boinc_slot_dir" --cap-add=SYS_ADMIN --device /dev/fuse -v /cvmfs:/cvmfs:shared --log-driver=k8s-file boinc__lhcathome.cern.ch_lhcathome__theory_2922-4841152-759
program: "/Library/Application Support/BOINC Data/Run_Podman" /opt/podman/bin/podman
Error: statfs /cvmfs: no such file or directory
command output:
starting container
running docker command: start boinc__lhcathome.cern.ch_lhcathome__theory_2922-4841152-759_1
program: "/Library/Application Support/BOINC Data/Run_Podman" /opt/podman/bin/podman
Error: no container with name or ID "boinc__lhcathome.cern.ch_lhcathome__theory_2922-4841152-759_1" found: no such container
command output:
running docker command: ps --all -f "name=boinc__lhcathome.cern.ch_lhcathome__theory_2922-4841152-759_1"
program: "/Library/Application Support/BOINC Data/Run_Podman" /opt/podman/bin/podman
command output:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
running docker command: logs boinc__lhcathome.cern.ch_lhcathome__theory_2922-4841152-759_1
program: "/Library/Application Support/BOINC Data/Run_Podman" /opt/podman/bin/podman
Error: no container with name or ID "boinc__lhcathome.cern.ch_lhcathome__theory_2922-4841152-759_1" found: no such container
command output:
stderr from container:
stderr end
running docker command: container rm boinc__lhcathome.cern.ch_lhcathome__theory_2922-4841152-759_1
program: "/Library/Application Support/BOINC Data/Run_Podman" /opt/podman/bin/podman
Error: no container with ID or name "boinc__lhcathome.cern.ch_lhcathome__theory_2922-4841152-759_1" found: no such container
command output:
running docker command: image rm boinc__lhcathome.cern.ch_lhcathome__theory_2922-4841152-759
program: "/Library/Application Support/BOINC Data/Run_Podman" /opt/podman/bin/podman
command output:
Untagged: localhost/boinc__lhcathome.cern.ch_lhcathome__theory_2922-4841152-759:latest
2026-04-13 16:39:27 (89100): called boinc_finish(1)

</stderr_txt>
]]>
ID: 53403 · Report as offensive     Reply Quote
computezrmle
Volunteer moderator
Volunteer developer
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 15 Jun 08
Posts: 2755
Credit: 304,271,457
RAC: 116,232
Message 53404 - Posted: 13 Apr 2026, 17:39:59 UTC - in response to Message 53403.  

On your host create an empty directory '/cvmfs' and set the permissions to 777.
[sudo] mkdir /cvmfs
[sudo] chmod 777 /cvmfs
ID: 53404 · Report as offensive     Reply Quote
Profile[AF>France>Ouest>Norm...

Send message
Joined: 13 Jul 05
Posts: 5
Credit: 319,128
RAC: 2,305
Message 53405 - Posted: 13 Apr 2026, 18:23:11 UTC - in response to Message 53404.  

How to ?
I am on MacOS Sequoia
ID: 53405 · Report as offensive     Reply Quote
computezrmle
Volunteer moderator
Volunteer developer
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 15 Jun 08
Posts: 2755
Credit: 304,271,457
RAC: 116,232
Message 53450 - Posted: 20 Apr 2026, 16:06:54 UTC - in response to Message 53405.  

Since Catalina 10.15 (introduced in 2019!) the root filesystem is read-only.
To fake a subfolder there you may need an entry in /etc/synthetic.conf that looks like this:
cvmfs<tab>System/Volumes/Data/cvmfs

After a reboot /cvmfs should be available for the Theory docker app.
For more info see:
https://keith.github.io/xcode-man-pages/synthetic.conf.5.html

Since I don't have a Mac I can't verify this method, so please post a comment whether it worked or not.
To check the logs it would be good that you make your computers visible in the prefs:
https://lhcathome.cern.ch/lhcathome/prefs.php?subset=project
ID: 53450 · Report as offensive     Reply Quote
Profile[AF>France>Ouest>Norm...

Send message
Joined: 13 Jul 05
Posts: 5
Credit: 319,128
RAC: 2,305
Message 53497 - Posted: 26 Apr 2026, 11:03:30 UTC - in response to Message 53450.  

Permission denied to create the file synthetic.conf on the directory /etc/
ID: 53497 · Report as offensive     Reply Quote
computezrmle
Volunteer moderator
Volunteer developer
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 15 Jun 08
Posts: 2755
Credit: 304,271,457
RAC: 116,232
Message 53498 - Posted: 27 Apr 2026, 10:24:55 UTC - in response to Message 53497.  

When you install a local CVMFS on MacOS this is what 'cvmfs_config setup' originally does (copied from the CVMFS source code):
     # Since MacOS 10.15 Catalina it is not possible anymore (without disabling
     # SIP) create directory in root `/`.
     # We decide to move the standard installation directory on
     # `/Users/shared/cvmfs` instead of `/cvmfs`
     # In order to keep the standard CVMFS mountpoint, we decide to implement
     # firmlinks from `/cvmfs` to `/Users/shared/cvmfs`
     if compare_versions $(sw_vers -productVersion) -ge "10.15"; then
        mkdir -p /Users/shared/cvmfs
        chown cvmfs:cvmfs /Users/shared/cvmfs
        chmod 777 /Users/shared/cvmfs
        if ! grep -q "^cvmfs\t" /etc/synthetic.conf 2> /dev/null ; then
          echo -e "# The line below was autogenerated by CernVM-FS, do not delete nor edit" >> /etc/synthetic.conf
          echo -e "cvmfs\t/Users/Shared/cvmfs" >> /etc/synthetic.conf
        fi
        # reload synthetic.conf - seems to return nonzero status code even on success
        /System/Library/Filesystems/apfs.fs/Contents/Resources/apfs.util -t || true
     else
        echo "Fuse4x and autofs bug" > /dev/null
        mkdir -p /cvmfs
        chown cvmfs:cvmfs /cvmfs
        chmod 777 /cvmfs
     fi

To run Theory (docker) without a local CVMFS you MUST ensure '/cvmfs' is present since the container requires it as mountpoint.
So, manually run the relevant commands from the source code above as admin, then reboot:
mkdir -p /Users/shared/cvmfs
chmod 777 /Users/shared/cvmfs
if ! grep -q "^cvmfs\t" /etc/synthetic.conf 2> /dev/null; then echo -e "cvmfs\t/Users/Shared/cvmfs" >> /etc/synthetic.conf; fi

The part between 'if' and 'fi' must be run as one command without a newline that may be inserted by the forum software here!
If you get permission issues you may not be admin!
In this case, consult your manual or visit MacOS related websites.
ID: 53498 · Report as offensive     Reply Quote

Message boards : Theory Application : Erreur systématique pendant le calcul ....


©2026 CERN