Re: [OMPI users] Weird error with OMPI 1.6.3

Yeah, the old 1.6 series didn't do a very good job of auto-detection of #sockets. I believe there is an mca param for telling it how many are there, which is probably what you'd need to use. On Aug 29, 2014, at 9:40 AM, Maxime Boissonneault wrote: > It

Re: [OMPI users] Weird error with OMPI 1.6.3

It is still there in 1.6.5 (we also have it). I am just wondering if there is something wrong in our installation that makes MPI unabled to detect that there are two sockets per node if we do not include a npernode directive. Maxime Le 2014-08-29 12:31, Ralph Castain a écrit : No, it isn't

Re: [OMPI users] Weird error with OMPI 1.6.3

No, it isn't - but we aren't really maintaining the 1.6 series any more. You might try updating to 1.6.5 and see if it remains there On Aug 29, 2014, at 9:12 AM, Maxime Boissonneault wrote: > It looks like > -npersocket 1 > > cannot be used alone. If I

Re: [OMPI users] Weird error with OMPI 1.6.3

It looks like -npersocket 1 cannot be used alone. If I do mpiexec -npernode 2 -npersocket 1 ls -la then I get no error message. Is this expected behavior ? Maxime Le 2014-08-29 11:53, Maxime Boissonneault a écrit : Hi, I am having a weird error with OpenMPI 1.6.3. I run a non-MPI command

[OMPI users] Weird error with OMPI 1.6.3

Hi, I am having a weird error with OpenMPI 1.6.3. I run a non-MPI command just to exclude any code error. Here is the error I get (I run with set -x to get the exact command that are run). ++ mpiexec -npersocket 1 ls -la