Davide,
No worries. I like to see folks engage SchedMD, especially if they are
seeing value in all the work that has gone into creating the software
that runs the majority of fastest clusters on the planet.
To your question: yes, you can update slurm.conf and do 'scontrol
reconfigure' to cha
Hi Brian,
>From your response, I speculate that my wording sounded harsh or
unrespectful. That was not my intention and therefore I sincerely
apologize for it.
In fact my perplexity is certainly due to my ignorance (as it must be
very clear by the number and "quality" of queries that I am posting
Davide,
I'll not engage on this. If you want a feature, pay SchedMD for support
and they will prioritize it and work on it. You are already using a
very impressive bit of software for free.
As far as local license updates, yes, you can do the local license and
reconfigure regularly. Feel fr
Hi ladies and gentlemen.
I am finding some problems while configuring sacct on an existing slurm-wlm
19.05.5 installation. I can not start MySQL Server for begin account
configuration becose DB server have root password (don't remember set it up).
If I try to remove and reinstall MySQL/MariaDB,
Thanks Brian.
I am still perplexed. What is a database to install, administer,
patch, update, could break, be down, etc buying us? I see limited use
cases, e.g. a license server which does not provide the license
count/use in a parsable way, and that someone wants to use with
multiple SLURM instal
Davide,
You have it pretty correct. While the database itself is not part of the
slurm suite, slurmdbd (which would access the database) is.
As far as writing something that keeps things updated, I'm sure many
have done this. However, it would be unique to your installation. The
specific num
Thanks a lot.
> > Does it need the execution permission? For root alone sufficient?
>
> slurmd runs as root, so it only need exec perms for root.
Perfect. That must have been then, since my script (like the example
one) did not have the execution permission on.
> I'm curious: What kind of disrup
On Fri, Sep 16, 2022 at 3:43 PM Sebastian Potthoff <
s.potth...@uni-muenster.de> wrote:
> Hi Hermann,
>
> So you both are happily(?) ignoring this warning the "Prolog and Epilog
> Guide",
> right? :-)
>
> "Prolog and Epilog scripts [...] should not call Slurm commands (e.g.
> squeue,
> scontrol, s
We also call scontrol in our scripts (a little as we can manage) and we
run at the scale of 1500 nodes. It hasn't really caused many issues,
but we try to limit it as much as we possibly can.
-Paul Edmon-
On 9/16/22 9:41 AM, Sebastian Potthoff wrote:
Hi Hermann,
So you both are happily(?) i
Hi Hermann,
>> So you both are happily(?) ignoring this warning the "Prolog and Epilog
>> Guide",
>> right? :-)
>>
>> "Prolog and Epilog scripts [...] should not call Slurm commands (e.g. squeue,
>> scontrol, sacctmgr, etc)."
>
> We have probably been doing this since before the warning was add
Davide DelVento writes:
> Does it need the execution permission? For root alone sufficient?
slurmd runs as root, so it only need exec perms for root.
>> > 2. How to debug the issue?
>> I'd try capturing all stdout and stderr from the script into a file on the
>> compute
>> node, for instance l
Hi Hermann,
Hermann Schwärzler writes:
> Hi Loris,
> hi Sebastian,
>
> thanks for the information on how you are doing this.
> So you both are happily(?) ignoring this warning the "Prolog and Epilog
> Guide",
> right? :-)
>
> "Prolog and Epilog scripts [...] should not call Slurm commands (e.g.
Thanks to both of you.
> Permissions on the file itself (and the directories in the path to it)
Does it need the execution permission? For root alone sufficient?
> Existence of the script on the nodes (prologue is run on the nodes, not the
> head)
Yes, it's in a shared filesystem.
> Not sure
Hi Loris,
hi Sebastian,
thanks for the information on how you are doing this.
So you both are happily(?) ignoring this warning the "Prolog and Epilog
Guide", right? :-)
"Prolog and Epilog scripts [...] should not call Slurm commands (e.g.
squeue, scontrol, sacctmgr, etc)."
May I ask how big
So if I understand correctly, this "remote database" is something that
is neither part of slurm itself, nor part of the license server per
se, correct?
Regarding the "if you got creative", has anybody on this list done
that already? I can't believe I'm the first one wanting this feature!
Matching
Hi Sebastian,
Sebastian Potthoff writes:
> Hi Loris
>
> We do something similar. At the end of our script pointed to by
> EpilogSlurmctld we have
>
> Using EpilogSlurmctld only works if the slurmctld user is root (or slurm with
> root privileges), right? I opted for the normal Epilog since w
Hi Loris
> We do something similar. At the end of our script pointed to by
> EpilogSlurmctld we have
Using EpilogSlurmctld only works if the slurmctld user is root (or slurm with
root privileges), right? I opted for the normal Epilog since we wanted to avoid
running slurm as root and I don’t h
Davide DelVento writes:
> 2. How to debug the issue?
I'd try capturing all stdout and stderr from the script into a file on the
compute
node, for instance like this:
exec &> /root/prolog_slurmd.$$
set -x # To print out all commands
before any other commands in the script. The "prolog_slurmd.
Hi Hermann,
Sebastian Potthoff writes:
> Hi Hermann,
>
> I happened to read along this conversation and was just solving this issue
> today. I added this part to the epilog script to make it work:
>
> # Add job report to stdout
> StdOut=$(/usr/bin/scontrol show job=$SLURM_JOB_ID | /usr/bin/grep
19 matches
Mail list logo
