Re: [slurm-users] [External] Re: Slurm queue seems to be completely blocked

2020-05-11 Thread Joakim Hove
And we have ignition - thank you very much! :-) On Mon, May 11, 2020 at 8:44 PM Alex Chekholko wrote: > Any time a node goes into DRAIN state you need to manually intervene and > put it back into service. > scontrol update nodename=ip-172-31-80-232 state=resume > > On Mon, May 11, 2020 at 11:40

Re: [slurm-users] [External] Re: Slurm queue seems to be completely blocked

2020-05-11 Thread Alex Chekholko
Any time a node goes into DRAIN state you need to manually intervene and put it back into service. scontrol update nodename=ip-172-31-80-232 state=resume On Mon, May 11, 2020 at 11:40 AM Joakim Hove wrote: > > You’re on the right track with the DRAIN state. The more specific answer >> is in the

Re: [slurm-users] [External] Re: Slurm queue seems to be completely blocked

2020-05-11 Thread Joakim Hove
> You’re on the right track with the DRAIN state. The more specific answer > is in the “Reason=” description on the last line. > > It looks like your node has less memory than what you’ve defined for the > node in slurm.conf > Thank you; that sounded meaningful to me. My slurm.conf file had RealMe

Re: [slurm-users] [External] Re: Slurm queue seems to be completely blocked

2020-05-11 Thread Michael Robbert
You’re on the right track with the DRAIN state. The more specific answer is in the “Reason=” description on the last line. It looks like your node has less memory than what you’ve defined for the node in slurm.conf Mike From: slurm-users on behalf of Joakim Hove Reply-To: Slurm User