Those CVEs are indeed for different software (one for PMIx, one for
Slurm), even though they're ultimately for the same kind of underlying
problem (chown() being used instead of lchown(), which could lead in
taking over privileged files).
The Slurm patches include more fixes related to
On 10/16/23 08:22, Groner, Rob wrote:
It is my understanding that it is a different issue than pmix.
That's my understanding too. The PMIx issue wasn't in Slurm, it was in
the PMIx code that Slurm was linked to. This CVE is for Slurm itself.
--
Chris Samuel : http://www.csamuel.org/ :
Hi Angel and Loris,
I hope this will be of at least some help, as I was tasked with trying to get
site factor implemented in our cluster for the sake of making conformant,
predictable priority values that were “pretty” and round, and I was not able to
find any good documentation for it either.
It is my understanding that it is a different issue than pmix. So to be fully
protected, you would need to build the latest/fixed pmix and rebuild slurm
using that (or just keep pmix disabled), AND have this latest version of slurm
with their fix for their own vulnerability.
Rob
Try
scontrol update NodeName=heimdall state=DOWN Reason="gpu issue"
and then
scontrol update NodeName=heimdall state=RESUME
to see if it will work. Probably just SLURM daemon having a hiccup
after you made changes.
Best,
Feng
On Mon, Oct 16, 2023 at 10:43 AM Gregor Hagelueken
wrote:
>
>
Hi,
We have a ubuntu server (22.04) with currently 5 GPUs (1 x l40 and 4 x
rtx_a5000).
I am trying to configure slurm such that a user can select either the l40 or
a5000 gpus for a particular job.
I have configured my slurm.conf and gres.conf files similar as in this old
thread:
Hello,
In the past it was recommended to reconfigure slurm daemons in logrotate
script, sending a signal I believe was also the way to go. But recently I
retested manual logrotation and I see that a removal of log file (for
slurmctld, slurmdbd or slurmd) does not affect the logging of the
Taras Shapovalov writes:
> Oh, does this mean that no one should use Slurm versions <= 21.08 any more?
That of course depends on your security requirements, but I wouldn't
have used those older versions in production any more, at least. (We
actually did upgrade from 21.08 to 23.02 on a couple
On 10/11/23 07:27, Cristian Huza wrote:
I recall there was a built in tool named seff (slurm efficiency), not
sure if it is still maintained
"seff" is in the Slurm sources in the contribs/seff directory, if you're
building RPMs from them then it's in the "slurm-contribs" RPM.
--
Chris
On 10/13/23 10:10, Angel de Vicente wrote:
But, in any case, I would still be interested in a site factor plugin
example, because I might revisit this in the future.
I don't know if you saw, but there is a skeleton example in the Slurm
sources:
src/plugins/site_factor/none
Not sure if
Hello Angel,
Angel de Vicente writes:
> Hello Loris,
>
> "Loris Bennett" writes:
>
>> Did you ever find an example or write your own plugin which you could
>> provide as a example?
>
> I'm afraid not (though I didn't persevere, because for the moment we are
> trying to encourage our users not
11 matches
Mail list logo
