I would also encourage you to use defaults in the slurm.conf (matching
what's shipped in the Ubuntu packages). However, here is what I've done to
use non-Ubuntu-package paths for the PID files.
Create an override in /etc/systemd/system/slurmd.service.d/override.conf
with something like:
node32[~
Hi,
thanks for all the responses.
On 18.03.21 11:29, Stefan Staeglich wrote:
> I think it makes more sense to adjust the config file
> /etc/slurm-llnl/slurm.conf
> and not the systemd units:
> SlurmctldPidFile=/run/slurmctld.pid
> SlurmdPidFile=/run/slurmd.pid
That was of course my first appr
Hi Sven,
I think it makes more sense to adjust the config file
/etc/slurm-llnl/slurm.conf
and not the systemd units:
SlurmctldPidFile=/run/slurmctld.pid
SlurmdPidFile=/run/slurmd.pid
Best,
Stefan
Am Mittwoch, 17. März 2021, 19:16:38 CET schrieb Sven Duscha:
> Hi,
>
> I experience with SLURM s
I can't immediately check what I do with Slurm but in several systemd files
I create sub folders of /var/run and set their ownership the same as the
service will run under.
I use CentOS (for now!).
I can post an actual service startup file in daylight if useful.
William
On Wed, 17 Mar 2021,
That is looking like your /run folder does not have world execute
permissions, making it impossible for anything to access sub-directories.
Brian Andrus
On 3/17/2021 1:05 PM, Sven Duscha wrote:
Hi,
On 17.03.21 19:54, Brian Andrus wrote:
Be that as it may, you can see it is a permissions issu
Hi,
On 17.03.21 19:54, Brian Andrus wrote:
> Be that as it may, you can see it is a permissions issue. Check
> permissions on /run and ensure the slurmctld user is able to write there.
>
> You can either change the slurmctld user to one that can write there
> or change the permissions on the direc
After installing SLURM in Ubuntu and before starting the services, I do:
mkdir -p /var/spool/slurmd
mkdir -p /var/lib/slurm-llnl
mkdir -p /var/lib/slurm-llnl/slurmd
mkdir -p /var/lib/slurm-llnl/slurmctld
mkdir -p /var/run/slurm-llnl (You need to change this to /run/slurm-llnl as
your location for
I am guessing you aren't overly familiar with Linux/systemd since you
have the '&' at the end of your start command.
Be that as it may, you can see it is a permissions issue. Check
permissions on /run and ensure the slurmctld user is able to write there.
You can either change the slurmctld us
Hi,
I experience with SLURM slurmctld an error on Ubuntu20.04, when starting
the service (through systemctl):
I installed munge and SLURM version 19.05.5-1 through the package
manager from
the default repository:
apt-get install munge slurm-client slurm-wlm slurm-wlm-doc slurmctld slurmd
syst
