Le vendredi 28 janvier 2022 à 06:56, Ratnasamy, Fritz
a écrit :
> Hi,
>
> I have a similar issue as described on the following link
> (https://groups.google.com/g/slurm-users/c/6SnwFV-S_Nk)A machine had some
> existing local permissions. We have added it as a compute node to our cluster
> via
--- Original Message ---
Le mardi 25 janvier 2022 à 22:22, a écrit :
> Dear all,
>
> how can I reverse the priority, so that jobs with high cpu and memory
>
> have a low priority?
>
> The Priority/Multifactor plugin it is possible to calculate high
>
> priority for high cpu and memory jo
Hi Remi,
Yes it does return the same id. See below:
johndoe@ecolonnelli:~ $ id
uid=71953(johndoe) gid=100026(Faculty_Collab)
groups=100026(Faculty_Collab),100181(ecolonnelli_access)
johndoe@ecolonnelli:~ $ id johndoe
uid=71953(johndoe) gid=100026(Faculty_Collab)
groups=100026(Faculty_Collab),1000
Any idea why pam_slurm_adopt would work on some nodes but not others? Here is
an excerpt from one of the nodes:
Jan 28 15:38:54 dgx1-1 sshd[1027640]: pam_sss(sshd:auth): authentication
success; logname= uid=0 euid=0 tty=ssh ruser= rhost=10.10.10.1 user=test.user
Jan 28 15:38:54 dgx1-1 pam_slurm_
Do you see the uid in /sys/fs/cgroup? (i.e. find /sys/fs/cgroup -name
"*71953*"). If not that could point to cgroup config.
From: slurm-users on behalf of
Ratnasamy, Fritz
Sent: Friday, January 28, 2022 11:13 AM
To: Rémi Palancher; Slurm User Community
Hi Mitchell, Remi
This is what returned the command: find /sys/fs/cgroup -name "*71953*"
/sys/fs/cgroup/freezer/slurm/uid_71953
/sys/fs/cgroup/devices/slurm/uid_71953
/sys/fs/cgroup/cpuset/slurm/uid_71953
/sys/fs/cgroup/cpu,cpuacct/slurm/uid_71953
/sys/fs/cgroup/memory/slurm/uid_71953
Do you hav
