Thanks for your patience and persistence. I’ll find a place to post your
experiences to help others as they navigate these waters.
> On Nov 28, 2017, at 8:52 PM, Philip Kovacs wrote:
>
> I doubled checked and yes, you definitely want the pmix headers and libpmix
> library installed before you
I doubled checked and yes, you definitely want the pmix headers and libpmix
library installed before you configure slurm.No need to use --with-pmix if pmix
is installed in standard system locations. Configure slurm and it will see the
pmix installation. After configuring slurm, but before insta
My apologies - I guess we hadn’t been tracking it that way. I’ll try to add
some clarification. We presented a nice table at the BoF and I just need to
find a few minutes to post it.
I believe you do have to build slurm against PMIx so that the pmix plugin is
compiled. You then also have to spe
Okay, I didn't see any note on the PMIx 2.1 page about versions of slurm
it was combatible with so I assumed all of them. My bad. Thanks for
the correction and the help. I just naively used the rpm spec that was
packaged with PMIx which does enable the legacy support. It seems best
then to
We run in that manner using this config on v.3.10.0-693.5.2.el7.x86_64 This is
slurm 17.02.4
Do your compute nodes have hyperthreading enabled ?
AuthType=auth/munge
CryptoType=crypto/munge
AccountingStorageEnforce=limits,qos,safe
AccountingStoragePort=ANumber
AccountingStorageType=ac
I've been trying to setup a slurm cluster with con_res enabled. No luck.
Running on ubuntu 16.04
When using linear selection all works as expected. Jobs are schedules and run
their course then exit. Exclusive use of the node is granted.
We would like to schedule based on cpu (cores actually) an
Actually if you're set on installing pmix/pmix-devel from the rpms and then
configuring slurm manually,you could just move the pmix-installed versions of
libpmi.so* and libpmi2.so* to a safe place, configureand install slurm which
will drop in its versions pf those libs and then either use the s
Very true - one of the risks with installing from packages. However, be aware
that slurm 17.02 doesn’t support PMIx v2.0, and so this combination isn’t going
to work anyway.
If you want PMIx v2.x, then you need to pair it with SLURM 17.11.
Ralph
> On Nov 28, 2017, at 2:32 PM, Philip Kovacs wr
This issue is that pmi 2.0+ provides a "backward compatibility" feature,
enabled by default, which installsboth libpmi.so and libpmi2.so in addition to
libpmix.so. The route with the least friction for you would probablybe to
uninstall pmix, then install slurm normally, letting it install its l
After 9 months of development and testing we are pleased to announce the
availability of Slurm version 17.11.0!
As usual this can be downloaded from https://www.schedmd.com/downloads.php.
Thanks again for all the help and support to get this out the door. It
was fun to see most of you at SC17!
Hello, Paul
Please see below.
2017-11-28 13:13 GMT-08:00 Paul Edmon :
> So in an effort to future proof ourselves we are trying to build Slurm
> against PMIx, but when I tried to do so I got the following:
>
> Transaction check error:
> file /usr/lib64/libpmi.so from install of
> slurm-17.02.
Hello,
Don´t understand why i can´t connect to the controller. This is a new fresh
install using slurmdbd in ubuntu 16.04
Seems like a persistant connection to mysql cannot be made ???
*slurmctl.log:*
[2017-11-27T20:22:48.056] Job accounting information stored, but details
not gathered
[2017-11
So in an effort to future proof ourselves we are trying to build Slurm
against PMIx, but when I tried to do so I got the following:
Transaction check error:
file /usr/lib64/libpmi.so from install of
slurm-17.02.9-1fasrc02.el7.centos.x86_64 conflicts with file from
package pmix-2.0.2-1.el7.ce
Sounds suspiciously similar to a bug we reported a very long time ago,
and that I'd submitted a patch for:
https://bugs.schedmd.com/show_bug.cgi?id=1048
Which was then revisited here:
https://bugs.schedmd.com/show_bug.cgi?id=2423
Though my fix handles a problem with a UsageFactor other than 1, I'
I think it's more related to your configuration than general slurm
capabilities. For example if you have quite long prolog/epilog scripts it
may be good idea to discourage users from submitting huge job arrays (with
very short tasks?).
In my case it's quite common to see users submitting arrays wi
15 matches
Mail list logo
