On 20/6/19 3:24 am, Brian Andrus wrote:
Can you give the exact command/output you have from this?
I suspect a typo in your slurm.conf for nodenames or what you are typing.
Brian Andrus
Hi Brian,
I am pretty sure there is no error in my typing of the commands, but
just in case find below t
19 Jun. 2019, 4:21 pm Chris Samuel, wrote:
> On Tuesday, 18 June 2019 9:36:56 PM PDT nathan norton wrote:
>
> > Just tried running that command, but it only shows nodes that are up and
> > running, doesn’t tell me about any nodes that are down and turned off, as
> > an e
lure look in the slurmd or slurmctld logs.
>
> ---
> Sam Gallop
>
> -Original Message-
> From: slurm-users On Behalf Of
> nathan norton
> Sent: 18 June 2019 09:33
> To: slurm-users@lists.schedmd.com
> Subject: [slurm-users] status of cloud nodes
>
> Hi all,
>
Hi all,
I am using slurm with a cloud provider it is all working a treat.
lets say i have 100 nodes all working fine and able to be scheduled,
everything works fine.
$ srun -N100 hostname
works fine.
For some unknown reason after machines shut down for example over the
weekend if no jobs g
they
are not 'running'
Thanks
Nathan
On 20/5/19 12:04 am, Riebs, Andy wrote:
Just looking at this quickly, have you tried specifying
“hint=multithread” as an sbatch parameter?
*From:*slurm-users [mailto:slurm-users-boun...@lists.schedmd.com] *On
Behalf Of *nathan norton
*Sent:* Sa
Hi,
I am in the process of setting up Slurm using Amazon cloud
infrastructure. All is going well, I can elastically start and stop
nodes when jobs run. I am running into a few small teething issues,
that are probably due to me not understanding some of the terminology
here. At a high level a
