[slurm-users] Re: Cloud elastic help

2025-01-29 Thread Ryan Novosielski via slurm-users
> On Jan 29, 2025, at 16:49, mark.w.moorcroft--- via slurm-users > wrote: > > It helps to unblock port 6818 on the node image. #eyeroll Bear in mind there are also port requirements on the login node too if you plan to run interactive jobs (they will otherwise hang when executed). -- #BlackLi

[slurm-users] Re: Cloud elastic help

2025-01-29 Thread mark.w.moorcroft--- via slurm-users
It helps to unblock port 6818 on the node image. #eyeroll -- slurm-users mailing list -- slurm-users@lists.schedmd.com To unsubscribe send an email to slurm-users-le...@lists.schedmd.com

[slurm-users] Cloud elastic help

2025-01-29 Thread mark.w.moorcroft--- via slurm-users
I have a new Slurm setup in AWS gov cloud that is not quite working. I will list a few factoids and maybe someone can suggest where to look next. The Troubleshooting page really has nothing relevant for elastic cloud deployments. The nodes are getting set to DOWN+CLOUD+POWERED_DOWN. Running a jo

[slurm-users] RHEL8.10 V slurmctld

2025-01-29 Thread Steven Jones via slurm-users
I am using Redhat's IdM/IPA for users Slurmctld is failing to run jobs and it is getting "invalid user id". "2025-01-28T21:48:50.271] sched: Allocate JobId=4 NodeList=node4 #CPUs=1 Partition=debug [2025-01-28T21:48:50.280] Killing non-startable batch JobId=4: Invalid user id" id on the slurm c