It was built using Open MPI, which was configured with set SLURMLOC = "/opt/slurm"; ./configure --with-slurm=$SLURMLOC --with-pmi=$SLURMLOC --with-verbs --without-mpi-param-check --enable-orterun-prefix-by-default --prefix=$PWD/install --with-mxm=/opt/mellanox/mxm --with-fca=/opt/mellanox/fca CFLAGS="-g -O3"
and from what we can tell have both PMI and PMI2 built in. The SLURM is the recently released 2.6.0 (presumably built straightforwardly, but I don’t have the details). On Jul 18, 2013, at 6:31 AM, Hongjia Cao <[email protected]> wrote: > > Could you tell how is the program foo built? Which MPI version and PMI > library are you using? > > 在 2013-07-17三的 13:16 -0700，Ralph Castain写道： >> Hi folks >> >> >> We're trying to test the pmi2 support in 2.6.0 and hitting a problem. >> We have verified that the pmi2 support was built/installed, and that >> both slurmctld and slurmd are at 2.6.0 level. When we run "srun >> --mpi-list", we get: >> >> >> srun: MPI types are... >> srun: mpi/mvapich >> srun: mpi/pmi2 >> srun: mpi/mpich1_shmem >> srun: mpi/mpich1_p4 >> srun: mpi/none >> srun: mpi/lam >> srun: mpi/openmpi >> srun: mpi/mpichmx >> srun: mpi/mpichgm >> >> >> So it looks like the install is correct. However, when we attempt to >> run a job with "srun --mpi=pmi2 foo", we get an error from the slurmd >> on the remote node: >> >> >> slurmd[n1]: mpi/pmi2: no value for key in req >> >> >> and the PMI calls in the app fail. Any ideas as to the source of the >> problem? Do we have to configure something else, or start slurmd with >> some option? >> >> >> Thanks >> Ralph >> >> >> >
