LHC@home

Hello

I installed a new linux VM with debian 12, boinc was running fine and I decided to try to do the native theory setup again, based on this thread.

cvmfs_config probe was giving all OK and then I wanted to do these steps

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. 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.

However after doing this my boinc is broken

sudo systemctl restart boinc-client
Job for boinc-client.service failed because the control process exited with error code.
See "systemctl status boinc-client.service" and "journalctl -xeu boinc-client.service" for details.
jerome@VM-Debian-OVH2:/etc/cvmfs$ sudo systemctl status boinc-client.service
× boinc-client.service - Berkeley Open Infrastructure Network Computing Client
Loaded: loaded (/etc/systemd/system/boinc-client.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Sat 2023-12-30 17:26:02 UTC; 45s ago
Duration: 34min 43.140s
Docs: man:boinc(1)
Process: 4455 ExecStartPre=/bin/sh -c /bin/chmod +x /sbin/create-boinc-cgroup && /sbin/create-boinc-cgroup (code=exited, status=1/FAILURE)
Process: 4499 ExecStopPost=/bin/rm -f lockfile (code=exited, status=0/SUCCESS)
CPU: 63ms

Dec 30 17:26:02 VM-Debian-OVH2 sh[4494]: chmod: cannot access '/sys/fs/cgroup/freezer/boinc/tasks': No such file or directory
Dec 30 17:26:02 VM-Debian-OVH2 sh[4495]: chown: cannot access '/sys/fs/cgroup/cpuset/boinc/cpuset.cpus': No such file or directory
Dec 30 17:26:02 VM-Debian-OVH2 sh[4495]: chown: cannot access '/sys/fs/cgroup/cpuset/boinc/cpuset.mems': No such file or directory
Dec 30 17:26:02 VM-Debian-OVH2 sh[4496]: chmod: cannot access '/sys/fs/cgroup/cpuset/boinc/cpuset.cpus': No such file or directory
Dec 30 17:26:02 VM-Debian-OVH2 sh[4496]: chmod: cannot access '/sys/fs/cgroup/cpuset/boinc/cpuset.mems': No such file or directory
Dec 30 17:26:02 VM-Debian-OVH2 sh[4497]: chown: cannot access '/sys/fs/cgroup/freezer/boinc/freezer.state': No such file or directory
Dec 30 17:26:02 VM-Debian-OVH2 sh[4498]: chmod: cannot access '/sys/fs/cgroup/freezer/boinc/freezer.state': No such file or directory
Dec 30 17:26:02 VM-Debian-OVH2 systemd[1]: boinc-client.service: Control process exited, code=exited, status=1/FAILURE
Dec 30 17:26:02 VM-Debian-OVH2 systemd[1]: boinc-client.service: Failed with result 'exit-code'.
Dec 30 17:26:02 VM-Debian-OVH2 systemd[1]: Failed to start boinc-client.service - Berkeley Open Infrastructure Network Computing Client.

What can be the issue ?

What can be the issue ?

The new garbage cranky is to blame. Forget about cgroups and other moronic stuff. Edit your cranky file and you'll be set. See https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=6075&postid=49061#49061

You can save the whole VM in Virtualbox.
Reload is also possible.

If you follow the "advice" from Evangelos Katikos all subroutines dealing with suspend/resume will get lost.


The method/scripts in thread 4971 have been developed in 2019 and should not be used any more on recent Linux systems.
At that time many computers (especially at CERN) were using cgroups v1.
Since then many Linux distributions switched to cgroups v2 as default where "freezer" has a different meaning.

Linux does not allow to mix freezer from v1 and freezer from v2.

As a result the latest cranky script was modified to work without the cgroups v1 modification from thread 4971.
Instead it uses a suspend/resume method that is directly available via systemd.
The new requirement here is an sudoers definition file which must be installed once.
This definition makes certain commands available without the need to enter a password - a standard method and widely used on Linux, hence far away from being "moronic".


The suggestion would be to
- undo the modifications from thread 4971
- reboot
- follow the advice given here: https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=6075&postid=48978
- reboot


Best case:
The local Linux system fulfils all requirements
=> Theory native runs and supports suspend/resume via systemd

Worst case:
The local Linux system does not fulfil all requirements
=> Theory native runs in legacy mode without suspend/resume support

Thanks for the quick and many answers !

The suggestion would be to
- undo the modifications from thread 4971
- reboot
- follow the advice given here: https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=6075&postid=48978
- reboot

I assume you mean to undo what was performed here

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

right ? can you please advise how can I undo this ?

Try to understand what the scripts you download do.


(1.) /sbin/create-boinc-cgroup
This script modifies your cgroups v1 setup.
It must not be run if your system is configured to use cgroups v2.

(2.) /etc/systemd/system/boinc-client.service
This overwrites your original boinc-client unit file used by systemd.


ToDo:
Replace /etc/systemd/system/boinc-client.service with the original unit file.
Option: delete /etc/systemd/system/boinc-client.service if the original service file is located in /usr/lib/systemd/system/
The original file does not include this line:
ExecStartPre=/bin/sh -c "/bin/chmod +x /sbin/create-boinc-cgroup && /sbin/create-boinc-cgroup"

As a result the script from (1.) will not be executed any more and you will be fine.


Remember to reboot after the changes to start with a clean setup.

Thanks a lot !

Yes there was a version in /usr/lib/systemd/system/ without the ExecStartPre instruction, so I only did the option to delete the one from /etc/systemd/system/ and then after reboot, and then I also ran the new instruction from Laurence in the other topic you mention and did a "sudo systemctl daemon-reload" then a "sudo systemctl restart boinc-client" and it worked, my boinc is up and running again :)

I strongly suggest that the sticky old topic in this section of the forum would be commented (or removed) because it is the first thing you see then you arrive here.

However I got some native theory tasks and they all failed quickly

<core_client_version>7.20.5</core_client_version>
<![CDATA[
<message>
process exited with code 195 (0xc3, -61)</message>
<stderr_txt>
11:20:38 (6665): wrapper (7.15.26016): starting
11:20:38 (6665): wrapper (7.15.26016): starting
11:20:38 (6665): wrapper: running ../../projects/lhcathome.cern.ch_lhcathome/cranky-0.1.4 ()
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] Detected Theory App
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] This application must have permanent access to
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] online repositories via a local CVMFS service.
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] It supports suspend/resume if a couple of
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] requirements are fulfilled.
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] Most important:
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] - init process is systemd
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] - cgroups v2 is enabled and 'freezer' is available
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] - the user running this application is a member of the 'boinc' group
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] - sudo is at least version 1.9.10
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] - sudoer file provided by LHC@home is installed
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] Checking local requirements.
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] Found Sudo-Version 1.9.13p3.
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] Can't find '/etc/cvmfs/domain.d/cern.ch.local'.
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] Can't find '/etc/cvmfs/config.d/cvmfs-config.cern.ch.local'.
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] Probing /cvmfs/alice.cern.ch... OK
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] Probing /cvmfs/cernvm-prod.cern.ch... OK
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] Probing /cvmfs/grid.cern.ch... OK
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] Probing /cvmfs/sft.cern.ch... OK
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] Excerpt from "cvmfs_config stat": VERSION HOST PROXY
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] 2.11.2.0 http://s1ral-cvmfs.openhtc.io/cvmfs/alice.cern.ch DIRECT
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] Found 'runc version spec: 1.0.2-dev' at '/cvmfs/grid.cern.ch/vc/containers/runc.new'.
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] Creating container filesystem.
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] Using /cvmfs/cernvm-prod.cern.ch/cvm4
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] Starting runc container.
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] To get some details on systemd level run
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] systemctl status Theory_2673-2280032-98_0.scope
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] mcplots runspec: boinc pp bbbar 7000 105 - pythia8 8.307 CP1-CR1 100000 98
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] ----,^^^^,<<<~_____---,^^^,<<~____--,^^,<~__;_
sudo: a password is required
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] Container Theory_2673-2280032-98_0 finished with status code 1.
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] Preparing output.
11:20:38 UTC +00:00 2023-12-31: cranky-0.1.4: [ERROR] No output found.
11:20:39 (6665): cranky exited; CPU time 0.264837
11:20:39 (6665): app exit status: 0xce
11:20:39 (6665): called boinc_finish(195)

</stderr_txt>
]]>

This "sudo: a password is required" in the middle is very strange isn't it ?

The VM I'm using is Debian GNU/Linux 12 (bookworm) [6.1.0-16-cloud-amd64|libc 2.36]

OS: Debian GNU/Linux 12 (bookworm) x86_64 
Host: OpenStack Nova 19.3.2 
Kernel: 6.1.0-16-cloud-amd64 
Packages: 505 (dpkg) 
Shell: bash 5.2.15 
Terminal: /dev/pts/0 
CPU: AMD EPYC-Milan (4) @ 2.295GHz 
GPU: 00:02.0 Cirrus Logic GD 5446 
Memory: 606MiB / 3835MiB 

Thanks ! (in advance :) )

sudo: a password is required

There are 2 things you need to check:

1. Does "/etc/sudoers.d/50-lhcathome_boinc_theory_native" exist and contains some lines?
To check this run:
sudo cat /etc/sudoers.d/50-lhcathome_boinc_theory_native

2. Is the user account (assuming it is "boinc" but you can use any other name except "root") running the BOINC client fully activated?
This means:
- does it have a real login shell in /etc/passwd
- does it have a password (an empty password deactivates the account

If you modify any of the account settings you need to logout the affected user and/or restart all services running as that user, e.g. the BOINC service

Once this is done login as user "boinc" or open a shell with "su boinc".
From that shell run "sudo cat /etc/sudoers.d/50-lhcathome_boinc_theory_native".
=> The command should now cat the sudoers file without asking for a password.

If this succeeds restart the BOINC client and try a Theory native task.

1. yes there is

sudo cat /etc/sudoers.d/50-lhcathome_boinc_theory_native
# save this file as '/etc/sudoers.d/50-lhcathome_boinc_theory_native'
# ownership must be 'root:root' and access rights must be '-r--r-----'
# '@includedir /etc/sudoers.d' must be enabled in /etc/sudoers

# regular expressions are enclosed between '^' and '$'
# this is supported since sudo version 1.9.10
# for more information read 'man sudoers'

# the regex patterns given here must match the command arguments in the calling script
# missing/additional arguments or an argument order not in sync causes a command to be rejected

# the commands are permitted for the local group 'boinc'
# ensure the calling user is a member of that group


Cmnd_Alias LHCATHOMEBOINC_01 = /usr/bin/cat ^/etc/sudoers.d/50-lhcathome_boinc_theory_native$
Cmnd_Alias LHCATHOMEBOINC_02 = /usr/bin/systemctl ^(freeze|thaw) Theory_[-a-zA-Z0-9_]+\.scope$
Cmnd_Alias LHCATHOMEBOINC_03 = /usr/bin/systemd-run ^--scope -u [a-zA-Z0-9_-]+ -p BindsTo=[a-zA-Z0-9_\.@-]+ -p After=[a-zA-Z0-9_\.@-]+ --slice-inherit --uid=[a-zA-Z0-9_-]+ --gid=boinc --same-dir -q -G /[a-zA-Z0-9_\./-]+/runc --root state run -b cernvm [a-zA-Z0-9_-]+$

%boinc     ALL = (ALL) NOPASSWD: LHCATHOMEBOINC_01, LHCATHOMEBOINC_02, LHCATHOMEBOINC_03

2. I'm really not sure to understand this, I did a standard boinc install with "sudo apt install boinc-client" and I have no knowledge if "boinc" can be used as a user or if it has any password (and which password it may have)

I can only confirm that boinc user is running boinc, but all this is automated of course, I didn't do anything so this can happen.


"- does it have a real login shell in /etc/passwd"

sudo cat passwd
///
boinc:x:104:109:BOINC core client,,,:/var/lib/boinc-client:/usr/sbin/nologin
///
jerome@VM-Debian-OVH2:/etc$ 

There is a row here for the boinc user so I assume it means "yes" to your question ? but i have no idea how to interpret this row and much less how to answer "does it have a password (an empty password deactivates the account", and even less why I would have to try to change anything here ?

Did I break something in boinc install / setup with the actions to try to have native app to work here ?

You shouldn't post your complete passwd file!

This is the line that matters:
boinc:x:104:109:BOINC core client,,,:/var/lib/boinc-client:/usr/sbin/nologin

The highlighted part shows that user "boinc" doesn't have a login shell.
Change this running:
sudo usermod -s /bin/bash boinc


Then set a password for user "boinc":
sudo passwd boinc

Use a "good" one when asked, hence not "12345678" or something like that.
And don't post it here or elsewhere ... ;-)

Have a question of understanding.
CentOS-VM starting boinc with this two commands:
sudo systemctl start boinc-client
boincmgr -d /var/lib/boinc
There was never a problem either in CentOS7 or CentOS8 or CentOS9 starting as a VM!

Read the thread title.
It's about Theory native and has nothing to do with vbox VMs.

Oopsy :D

But the password are not visible there ! anyway I did cleanup above.

I did what you say, now I see

boinc:x:104:109:BOINC core client,,,:/var/lib/boinc-client:/bin/bash

I setup a (complicated) password for the boinc user (not published here), and I restarted boinc service, I could then login with that boinc user and I do see the result for "sudo cat /etc/sudoers.d/50-lhcathome_boinc_theory_native", and it didn't prompt me any password when I did it actually.

So I logged out and back with my regular user, I got some Theory Simulation v300.08 (native_theory) x86_64-pc-linux-gnu but I have the exact same error again with the "sudo: a password is required" in the stderr :(

I rebooted the VM, and I did the test again : same issue.

Read the thread title.
It's about Theory native and has nothing to do with vbox VMs.

This are also Theory -native Tasks, sorry.

The log list this requirement:
17:06:07 UTC +00:00 2023-12-31: cranky-0.1.4: [INFO] - the user running this application is a member of the 'boinc' group

Did you check/ensure that?

So, if you run BOINC as a service under the account "boinc", then do this:
sudo usermod -a -G boinc boinc

If you start BOINC from your normal user account you may need this:
sudo usermod -a -G boinc your_user_name


As before:
A relogin or service restart is required

How on earth could the user created by the boinc installation script not have the proper requisites ?

I didn't setup as a service, in linux it installs like this, if I start the VM then boinc is running, so I assume that 1/yes it is running as a service 2/I swear I did nothing to achieve this !!

Anyway I did that :

boinc@VM-Debian-OVH2:~$ sudo usermod -a -G boinc boinc
[sudo] password for boinc: 
Sorry, user boinc is not allowed to execute '/usr/sbin/usermod -a -G boinc boinc' as root on VM-Debian-OVH2.

Edit : I just thought : maybe I must do the same under my own account, I just did it and didn't get that same error, I'm gonna restart boinc and try again.

Edit 2 : nope

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.

As for the sudoers file:
If cat of that file works as user "boinc" there's no reason other commands defined in the same file won't work.


Hint:
Will look into it tomorrow or early next week.

I'm leaving for new year party also :)

I'm not sure how to see the "boinc-client service file", I just managed to do this now :

sudo systemctl show boinc-client
Type=simple
ExitType=main
Restart=no
NotifyAccess=none
RestartUSec=100ms
TimeoutStartUSec=1min 30s
TimeoutStopUSec=1min 30s
TimeoutAbortUSec=1min 30s
TimeoutStartFailureMode=terminate
TimeoutStopFailureMode=terminate
RuntimeMaxUSec=infinity
RuntimeRandomizedExtraUSec=0
WatchdogUSec=0
WatchdogTimestampMonotonic=0
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=9132
ControlPID=0
FileDescriptorStoreMax=0
NFileDescriptorStore=0
StatusErrno=0
Result=success
ReloadResult=success
CleanResult=success
UID=104
GID=109
NRestarts=0
OOMPolicy=stop
ExecMainStartTimestamp=Sun 2023-12-31 17:53:50 UTC
ExecMainStartTimestampMonotonic=3045999408
ExecMainExitTimestampMonotonic=0
ExecMainPID=9132
ExecMainCode=0
ExecMainStatus=0
ExecStart={ path=/usr/bin/boinc ; argv[]=/usr/bin/boinc ; ignore_errors=no ; start_time=[Sun 2023-12-31 17:53:50 UTC] ; stop_time=[n/a] ; pid=9132 ; code=(null) ; status=0/0 }
ExecStartEx={ path=/usr/bin/boinc ; argv[]=/usr/bin/boinc ; flags= ; start_time=[Sun 2023-12-31 17:53:50 UTC] ; stop_time=[n/a] ; pid=9132 ; code=(null) ; status=0/0 }
ExecReload={ path=/usr/bin/boinccmd ; argv[]=/usr/bin/boinccmd --read_cc_config ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
ExecReloadEx={ path=/usr/bin/boinccmd ; argv[]=/usr/bin/boinccmd --read_cc_config ; flags= ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
ExecStop={ path=/usr/bin/boinccmd ; argv[]=/usr/bin/boinccmd --quit ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
ExecStopEx={ path=/usr/bin/boinccmd ; argv[]=/usr/bin/boinccmd --quit ; flags= ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
ExecStopPost={ path=/bin/rm ; argv[]=/bin/rm -f lockfile ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
ExecStopPostEx={ path=/bin/rm ; argv[]=/bin/rm -f lockfile ; flags= ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
Slice=system.slice
ControlGroup=/system.slice/boinc-client.service
ControlGroupId=3308
MemoryCurrent=1219170304
MemoryAvailable=infinity
CPUUsageNSec=16569802821000
TasksCurrent=28
IPIngressBytes=[no data]
IPIngressPackets=[no data]
IPEgressBytes=[no data]
IPEgressPackets=[no data]
IOReadBytes=18446744073709551615
IOReadOperations=18446744073709551615
IOWriteBytes=18446744073709551615
IOWriteOperations=18446744073709551615
Delegate=no
CPUAccounting=yes
CPUWeight=[not set]
StartupCPUWeight=[not set]
CPUShares=[not set]
StartupCPUShares=[not set]
CPUQuotaPerSecUSec=infinity
CPUQuotaPeriodUSec=infinity
IOAccounting=no
IOWeight=[not set]
StartupIOWeight=[not set]
BlockIOAccounting=no
BlockIOWeight=[not set]
StartupBlockIOWeight=[not set]
MemoryAccounting=yes
DefaultMemoryLow=0
DefaultMemoryMin=0
MemoryMin=0
MemoryLow=0
MemoryHigh=infinity
MemoryMax=infinity
MemorySwapMax=infinity
MemoryLimit=infinity
DevicePolicy=auto
TasksAccounting=yes
TasksMax=4575
IPAccounting=no
ManagedOOMSwap=auto
ManagedOOMMemoryPressure=auto
ManagedOOMMemoryPressureLimit=0
ManagedOOMPreference=none
UMask=0022
LimitCPU=infinity
LimitCPUSoft=infinity
LimitFSIZE=infinity
LimitFSIZESoft=infinity
LimitDATA=infinity
LimitDATASoft=infinity
LimitDATASoft=infinity
LimitSTACK=infinity
LimitSTACKSoft=8388608
LimitCORE=infinity
LimitCORESoft=0
LimitRSS=infinity
LimitRSSSoft=infinity
LimitNOFILE=524288
LimitNOFILESoft=1024
LimitAS=infinity
LimitASSoft=infinity
LimitNPROC=15250
LimitNPROCSoft=15250
LimitMEMLOCK=8388608
LimitMEMLOCKSoft=8388608
LimitLOCKS=infinity
LimitLOCKSSoft=infinity
LimitSIGPENDING=15250
LimitSIGPENDINGSoft=15250
LimitMSGQUEUE=819200
LimitMSGQUEUESoft=819200
LimitNICE=0
LimitNICESoft=0
LimitRTPRIO=0
LimitRTPRIOSoft=0
LimitRTTIME=infinity
LimitRTTIMESoft=infinity
WorkingDirectory=/var/lib/boinc
OOMScoreAdjust=0
CoredumpFilter=0x33
Nice=10
IOSchedulingClass=3
IOSchedulingPriority=4
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
CPUAffinityFromNUMA=no
NUMAPolicy=n/a
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SyslogLevel=6
SyslogFacility=3
LogLevelMax=-1
LogRateLimitIntervalUSec=0
LogRateLimitBurst=0
SecureBits=0
CapabilityBoundingSet=cap_chown cap_dac_override cap_dac_read_search cap_fowner cap_fsetid cap_kill cap_setgid cap_setuid cap_setpcap cap_linux_immutable cap_net_bind_service>
User=boinc
DynamicUser=no
RemoveIPC=no
ReadWritePaths=-/var/lib/boinc -/etc/boinc-client
PrivateTmp=no
PrivateDevices=no
ProtectClock=no
ProtectKernelTunables=no
ProtectKernelModules=no
ProtectKernelLogs=no
ProtectControlGroups=yes
PrivateNetwork=no
PrivateUsers=no
PrivateMounts=no
PrivateIPC=no
ProtectHome=yes
ProtectSystem=strict
SameProcessGroup=no
UtmpMode=init
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=2147483646
LockPersonality=no
RuntimeDirectoryPreserve=no
RuntimeDirectoryMode=0755
StateDirectoryMode=0755
CacheDirectoryMode=0755
LogsDirectoryMode=0755
ConfigurationDirectoryMode=0755
TimeoutCleanUSec=infinity
MemoryDenyWriteExecute=no
RestrictRealtime=no
RestrictSUIDSGID=no
RestrictNamespaces=no
MountAPIVFS=no
KeyringMode=private
ProtectProc=default
ProcSubset=all
ProtectHostname=no
KillMode=control-group
KillSignal=15
RestartKillSignal=15
FinalKillSignal=9
SendSIGKILL=yes
SendSIGHUP=no
WatchdogSignal=6
Id=boinc-client.service
Names=boinc-client.service
Requires=sysinit.target system.slice -.mount
Wants=vboxdrv.service
WantedBy=multi-user.target
Conflicts=shutdown.target
Before=shutdown.target multi-user.target
After=basic.target vboxdrv.service sysinit.target network-online.target system.slice systemd-journald.socket -.mount
RequiresMountsFor=/var/lib/boinc
Documentation="man:boinc(1)"
Description=Berkeley Open Infrastructure Network Computing Client
LoadState=loaded
ActiveState=active
FreezerState=running
SubState=running
FragmentPath=/lib/systemd/system/boinc-client.service
UnitFileState=enabled
UnitFilePreset=enabled
StateChangeTimestamp=Sun 2023-12-31 17:53:50 UTC
StateChangeTimestampMonotonic=3045999666
InactiveExitTimestamp=Sun 2023-12-31 17:53:50 UTC
InactiveExitTimestampMonotonic=3045999666
ActiveEnterTimestamp=Sun 2023-12-31 17:53:50 UTC
ActiveEnterTimestampMonotonic=3045999666
ActiveExitTimestamp=Sun 2023-12-31 17:53:49 UTC
ActiveExitTimestampMonotonic=3045196371
InactiveEnterTimestamp=Sun 2023-12-31 17:53:50 UTC
InactiveEnterTimestampMonotonic=3045998275
CanStart=yes
CanStop=yes
CanReload=yes
CanIsolate=no
CanFreeze=yes
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=yes
OnSuccessJobMode=fail
OnFailureJobMode=replace
IgnoreOnIsolate=no
NeedDaemonReload=no
JobTimeoutUSec=infinity
JobRunningTimeoutUSec=infinity
JobRunningTimeoutUSec=infinity
JobTimeoutAction=none
ConditionResult=yes
AssertResult=yes
ConditionTimestamp=Sun 2023-12-31 17:53:50 UTC
ConditionTimestampMonotonic=3045998678
AssertTimestamp=Sun 2023-12-31 17:53:50 UTC
AssertTimestampMonotonic=3045998680
Transient=no
Perpetual=no
StartLimitIntervalUSec=10s
StartLimitBurst=5
StartLimitAction=none
FailureAction=none
SuccessAction=none
InvocationID=e4b35d3f1ce74ea5b3e5fa360dfca017
CollectMode=inactive

If this is not the good thing you'll tell me, see you tomorrow or after tomorrow : no worry thanks again for your help !

Also note I'm using boinc 7.20.5 : that's the one installed by "apt install boinc-client"

Happy new year to all !

sudo: a password is required

Have same issue on my manjaro box,

For me the (temporary) solution is to make a change to the regex script in /etc/sudoers/

from:
Cmnd_Alias LHCATHOMEBOINC_03 = /usr/bin/systemd-run ^--scope -u [a-zA-Z0-9_-]+ -p BindsTo=[a-zA-Z0-9_\.@-]+ -p After=[a-zA-Z0-9_\.@-]+ --slice-inherit --uid=[a-zA-Z0-9_-]+ --gid=boinc --same-dir -q -G /[a-zA-Z0-9_\./-]+/runc --root state run -b cernvm [a-zA-Z0-9_-]+$
to:
Cmnd_Alias LHCATHOMEBOINC_03 = /usr/bin/systemd-run ^--scope -u [a-zA-Z0-9_-]+ -p BindsTo=[a-zA-Z0-9_\.@-]+ -p After=[a-zA-Z0-9_\.@-]+ --slice-inherit --uid=[a-zA-Z0-9_-]+ --gid=boinc --same-dir -q -G /[a-zA-Z0-9_\./-]+/runc.+$

One more sign for the regex and my system gives "password is required"
But be aware: This is a safety issue.

@computezrmle
I'm open for a better solution.

Happy new year!

2. Is the user account (assuming it is "boinc" but you can use any other name except "root") running the BOINC client fully activated?
This means:
- does it have a real login shell in /etc/passwd
- does it have a password (an empty password deactivates the account)

login shell and password are not required for running tasks,
but it helps a lot to find some issues