that supported yet? I'd look very forward to a feature
like that!
Looking forward to your answers!
Best wishes,
Felix Willenborg
--
Felix Willenborg
Arbeitsgruppe Machine Learning
Department für Medizinische Physik und Akustik
Fakultät für Medizin und Gesundheitswissenschaften
Carl von Ossietzky
re out what is causing the problem.
>
> Regards,
> Said
> --------
> *From:* Felix Willenborg <felix.willenb...@uni-oldenburg.de>
> *Sent:* Wednesday, July 5, 2017 9:07:05 PM
> *To:* slurm-dev
> *Subject:* [slurm-
__
> > From: Ole Holm Nielsen <ole.h.niel...@fysik.dtu.dk>
> > Sent: Wednesday, July 5, 2017 7:07:15 PM
> > To: slurm-dev
> > Subject: [slurm-dev] Re: SLURM ERROR! NEED HELP
> >
> >
> > On 07/05/2017 11:40 AM, Felix Willenborg wrote:
> >>
Hi,
in my network I encountered that managed switches were preventing
necessary network communication between the nodes, on which SLURM
relies. You should check if you're using managed switches to connect
nodes to the network and if so, if they're blocking communication on
slurm ports.
Best,
anybody
spot an error I made? I'm looking for a solution for days and I'm
running out of ideas.
Looking forward to your answers. Thanks in advance!
Best wishes,
Felix Willenborg
or you can use the reservation feature depending on your
> exact use case.
>
> /Magnus
>
> On 2016-12-01 15:54, Felix Willenborg wrote:
>>
>> Dear everybody,
>>
>> I'd like to restrict submissions from a certain user group or allow only
>> one certain user group
you here.
Looking forward to some answers!
Best,
Felix Willenborg
omeone has a good
idea to solve my problem anyway?
Best,
Felix Willenborg
Am 07.03.2016 um 12:55 schrieb Felix Willenborg:
> Dear Lachele,
>
> your suggestion is great! It would work if we'd have a complete
> homogenic cluster - which is unfortunately not the case :(. All nodes
>
useful to schedule GPUs. For
>> example a node can be associated with two Slurm partitions (e.g.
>> "cpu" and "gpu") and the partition/queue "cpu" could be limited to
>> only a subset of the node’s CPUs, insuring that one or more CPUs would
>
So i tried out installing the latest package (14.11.4-1) of slurm with
no success - unfortunately. I kept an eye on the compilation of the
Infiniband Plugin, that it is loaded in the slurmd and that a
acct_gathering.conf is available. Still, i have the same problem. I
assume that i'm not
@Yann Sagon:
This is a good point. I didn't notice this. I'm new to this particular
system. Everything installed, configured etc. was already there when i
got into it. I'll keep that in mind, because i've got to discuss the
upgrade with the group. Maybe i should set it up from the beginning
which came in my mind, like possible
blocked ports or user/group rights set wrong. Maybe you have an idea.. i
ran out of them. Also, here is the - anonymized - slurm.conf aswell as
the slurmctld.log and slurmd.log of on node. I'm looking forward to some
help!!
Best wishes,
Felix Willenborg
12 matches
Mail list logo