LHC@home

Please post the boinc-client service file you are currently using.
In the past there were some versions with a few options set too strict.

@Jerome_C2005
think computezrmle asks for the boinc* file in

/etc/systemd/system/
and
/etc/systemd/system/boinc-client.service.d/

The last is'n used in most cases

Happy new year.

@Saturn911
Probably the most useful post of the year so far as it leads to a solution.


Issue causing the failure:
The sudoers pattern allows to run a locally installed "runc" without asking for a password.
If no local runc can be found cranky checks for "runc.new" or even "runc.old".
Since the sudoer pattern doesn't include the extensions ".old|.new" there's no match and sudo consequently does what it is intended to do - it asks for a password.

Saturn911's solution works as it checks the pattern until "runc" and allows arbitrary characters after that.

I suggest to be a bit more strict and modify the original sudoer pattern as follows:
1. As root edit "/etc/sudoers.d/50-lhcathome_boinc_theory_native"
2. Locate the alias "LHCATHOMEBOINC_03"
3. Replace "...runc --root state..." with "...(runc|runc\.new|runc\.old) --root state..."
4. Save the file


Be aware:
The parentheses are part of the replacement and must be entered as shown.


I will send this as a suggestion to CERN to update the setup script.

Probably the most useful post of the year so far

lol

Replace "...runc --root state..." with "...(runc|runc\.new|runc\.old) --root state..."

seems to work for me.
Thank you much.

\o/

jerome@VM-Debian-OVH2:~$ sudo systemctl status Theory_2673-2347711-98_1.scope
● Theory_2673-2347711-98_1.scope - /cvmfs/grid.cern.ch/vc/containers/runc.new --root state run -b cernvm Theory_2673-2347711-98_1
     Loaded: loaded (/run/systemd/transient/Theory_2673-2347711-98_1.scope; transient)
  Transient: yes
     Active: active (running) since Mon 2024-01-01 14:40:01 UTC; 5min ago
      Tasks: 18 (limit: 4575)
     Memory: 95.0M
        CPU: 3min 18.514s
     CGroup: /system.slice/Theory_2673-2347711-98_1.scope
             ├─53448 /cvmfs/grid.cern.ch/vc/containers/runc.new --root state run -b cernvm Theory_2673-2347711-98_1
             ├─53494 /bin/bash ./job
             ├─53708 /bin/bash ./runRivet.sh boinc pp jets 7000 350 - pythia8 8.186 tune-2c 100000 98
             ├─59960 /bin/bash ./runRivet.sh boinc pp jets 7000 350 - pythia8 8.186 tune-2c 100000 98
             ├─59962 /bin/bash ./runRivet.sh boinc pp jets 7000 350 - pythia8 8.186 tune-2c 100000 98
             ├─59965 /shared/rivetvm/rivetvm.exe -a CMS_2013_I1224539:JMODE=DIJET -i /shared/tmp/tmp.9Ffyol8vvV/generator.hepmc -o /shared/tmp/tmp.9Ffyol8vvV/flat -H /shared/>
             ├─59966 /bin/bash ./rungen.sh boinc pp jets 7000 350 - pythia8 8.186 tune-2c 100000 98 /shared/tmp/tmp.9Ffyol8vvV/generator.hepmc
             ├─66356 /shared/pythia8/pythia8.exe /shared/tmp/tmp.9Ffyol8vvV/generator.params /shared/tmp/tmp.9Ffyol8vvV/generator.hepmc
             └─68014 sleep 3

Jan 01 14:40:01 VM-Debian-OVH2 systemd[1]: Started Theory_2673-2347711-98_1.scope - /cvmfs/grid.cern.ch/vc/containers/runc.new --root state run -b cernvm Theory_2673-2347711->
lines 1-19/19 (END)

The year us starting very happy indeed ! Thanks a lot guys !!

So this is actually the *only* thing that has to be done on debian 12 so the native task can work (and not execute the last part of Laurence script in the sticky post, I insist this should be commented or removed), right ?

(+ do the script given by Laurence in the other recent topic to "sudo must be configured to allow the boinc user to run systemctl and systemd-run commands")

Is this a "debian 12" only issue (and manjaro) ?

think the easiest solution for most users is to have a corrected script.
Laurence has explained was it does.
If someone want to do it himself, that's o.k. but not suitable for all.
afaik this is like things work in linux.

The systemctl status now looks exactly how it should look like.
Happy crunching.

do the script given by Laurence in the other recent topic to "sudo must be configured to allow the boinc user to run systemctl and systemd-run commands"

That script is thought as an offer to easily create the correct sudoers file at the right place and with the right attributes.
It must be run as root, hence can't be run via BOINC.
The sudoers file contains the commands a non-root user is allowed to run without entering the root password.

The command aliases should be used as strict as possible (which was the issue here -> too strict).

In the past many volunteers asked for easy to use oneliners to set up complex things.
That's why the script has been created.

... I suggest to be a bit more strict and modify the original sudoer pattern as follows:
1. As root edit "/etc/sudoers.d/50-lhcathome_boinc_theory_native"
2. Locate the alias "LHCATHOMEBOINC_03"
3. Replace "...runc --root state..." with "...(runc|runc\.new|runc\.old) --root state..."
4. Save the file

As of today the updated script creating the sudoers file is available on the project servers (-dev and -prod).
The modified script now creates the correct command alias.

Volunteers who already modified the sudoers file do not need to run the script again.

Volunteers who run the script again will find a backup of the old sudoers file in /etc/sudoers.d beside the new file.
Feel free to leave the backup there or delete it.

Sudo will automatically ignore the backup file and use the new file as soon as it is available.
Sudo version >= 1.9.10 still remains a requirement.