Will, If you use modules, perhaps you could detect when the module is loaded from a gateway and not set I_MPI_PMI_LIBRARY there. If you're not using SLURM on your gateways for interactive jobs then it becomes even easier-- just make I_MPI_PMI_LIBRARY conditional on finding one of the SLURM_* job variables.
-Aaron On Thu, Apr 30, 2015 at 2:35 PM, Will French <[email protected]> wrote: > On Apr 30, 2015, at 12:33 PM, Thompson, Matt[SCIENCE SYSTEMS AND > APPLICATIONS INC] (GSFC-610.1) <[email protected]> wrote: > > (Note: Do *not* have I_MPI_PMI_LIBRARY=/usr/slurm/lib64/libpmi.so set when > you mpirun. You get fun errors!) > > > > Has anyone discovered/created a smart way around this? We’d like to avoid > our users needing to export this environment variable in their SLURM > scripts, so we export it from a command similar to “module load intel_mpi”. > The problem is that this environment variable breaks mpirun/mpiexec if a > user wants to test a MPI program interactively from one of our gateways. > Works great with srun, though. > > Sorry, Matt, not trying to hijack your thread! Just thought I’d ask since > you brought it up. >
