yes, that's exactly the problem. I assumed salloc was used to run an
interactive job but I was wrong. I guess I have to use srun for that.
I am still trying to figure how to do the user guide to explain when
to use salloc and then srun instead of srun in the first place.
Thanks a bunch for your help
Eva
On Fri, 12 Sep 2014, Bruce Roberts wrote:
>
> I think the problem you have here is the salloc you ran doesn't
> automatically send you to a node in your allocation. I am gussing you
> ran your salloc from hpcdev-005 that is why hostname by itself returns
> that. If you ran srun hostname inside of your salloc you would get on
> the node in your allocation.
>
> On 09/11/2014 03:44 PM, Eva Hocks wrote:
> >
> >
> > I am trying to configure the latest slurm 14.03 and am running into
> > problem to prevent slurm from running jobs on the control node.
> >
> > sinfo shows 3 nodes configure in the slurm.conf:
> > active up 2:00:00 1 down* hpc-0-5
> > active up 2:00:00 1 mix hpc-0-4
> > active up 2:00:00 1 idle hpc-0-6
> >
> >
> > but when I use salloc I end up on the head node
> >
> >
> > $ salloc -N 1 -p active sh
> > salloc: Granted job allocation 16
> > sh-4.1$ hostname
> > hpcdev-005.sdsc.edu
> >
> >
> > That node is not part of the "active" partition but slurm still uses it.
> > How? The allocation btw is for NodeList=hpc-0-4
> > and the user can login to that node without a problem but slurm doesn't
> > run the sh on that node for the user.
> >
> > Also how can a user find out what nodes are allocated without having to
> > run the scontrol command? Is there an option in salloc to return the
> > host names?
> >
> > Thanks
> > Eva
> >
>
