Re: [slurm-users] Reservations and groups

Ok, PEBKAC :) When creating the reservation, I set account=root . Just adding "account=" to the update fixed both errors. Sorry for the noise. Diego Il 04/05/2023 07:51, Diego Zuccato ha scritto: Hello all. I'm trying to define a reservation that only allows users in a group, but it seems

[slurm-users] Reservations and groups

Hello all. I'm trying to define a reservation that only allows users in a group, but it seems I'm missing something: [root@slurmctl ~]# scontrol update res reservationname=prj-test groups=res-TEST Error updating the reservation: Invalid group id slurm_update error: Invalid group id [root@slu

Re: [slurm-users] Problem with cgroup plugin in Ubuntu22.04 and slurm 21.08.5

Hello, Angel de Vicente writes: > , > | slurmd: fatal: Hybrid mode is not supported. Mounted cgroups are: > | 5:freezer:/ > | 3:cpuacct:/ > ` in the end I learnt that despite Ubuntu 22.04 reporting to be using only cgroup V2, it was also using V1 and creating those mount points, and th

Re: [slurm-users] Several slurmdbds against one mysql server?

Hello, Angel de Vicente writes: > And hence my question.. because as I was saying in a previous mail, > reading the documentation I understand that this is the standard way to > do it, but right now I got it working the other way: in each cluster I > have one slurmdbd daemon that connects with a

[slurm-users] Best way to accurately calculate the CPU usage of an account when using fairshare?

Good morning, We have at least one billed account right now, where the associated researchers are able to submit jobs that run against our normal queue with fairshare, but not for an academic research purpose. So we'd like to accurately calculate their CPU hours. We are currently using a script

Re: [slurm-users] Unexpected negative NICE values

Hi Jürgen, This was it! Thank you so much for the hint! I did not know about the "top" command and was also not aware that this option was enabled in our slurm.conf. Thanks for the help! Sebastian On 03.05.23 12:10, Juergen Salk wrote: Hi Sebastian, maybe it's a silly thought on my part,

Re: [slurm-users] unable to kill namd3 process

Hi, For an update we tried one case please find it below: We tried by adding below script to kill the namd3 process in our epilog script. # To kill remaining processes of job. # if [ $SLURM_UID = 1234 ] ; then STUCK_PID=`${SLURM_BIN}scontrol listpids $SLURM_JOB_ID | awk '{print $1}' | gr

Re: [slurm-users] Unexpected negative NICE values

Hi Sebastian, maybe it's a silly thought on my part, but do you have the `enable_user_top´ Option included in your SchedulerParameters configuration? This would allow regular users to use `scontrol top ´ to push some of their jobs ahead of other jobs owned by them and this works internally by

Re: [slurm-users] slurm-users Digest, Vol 65, Issue 38

Hi Jürgen Thanks for your feedback. I think you are right that I should probably be using `sreport` for this. I think there must be some other reason that `sreport` is not showing me any actual output. Perhaps the explanation could be that we currently do not have users organised in accounts.

Re: [slurm-users] slurm-users Digest, Vol 65, Issue 38

Hi Mike Thanks for the suggestion. I think something else may be missing here on my end. With `acct` I can actually get the usage of individual jobs with TRES information, but there must be something else causing GPU not to be included in the information I get. When I include the "--allocation

[slurm-users] Unexpected negative NICE values

Hello all, I am encountering some unexpected behavior where the jobs (queued & running) of one specific user have negative NICE values and therefore an increased priority. The user is not privileged in any way and cannot explicitly set the nice value to a negative value by e.g. adding "--nice