I have not personally tried Open MPI in WSL / WSL2. Two suggestions:
1. Can you post the output of the error that occurs? 2. Can you try upgrading to the latest 4.0.x release, or at least the latest v3.1.x release (as of this writing v3.1.6)? > On Nov 27, 2020, at 10:50 AM, schoon via users <users@lists.open-mpi.org> > wrote: > > Hi all, > > I cannot say I am a black belt MPI developer, and have sort of > slammed into the following problem "from the left". > > A quick summary of the situation: > > * The code which causes the problem has been used on many > different systems previously, but never on WSL2 before. > > * One component is launched from within the code by calling > mpiexec through a standard library system call. > > * This component works fine when run from the command line. It is > also possible to run it with mpiexec from the command line. > > * Other commands can still be launched with cmd::system from > within the code, but mpiexec of anything will fail invariably. > > * The OS is a fully updated version of Windows 10, running a > fully updated version of Debian in WSL2. The OpenMPI package > installed is v. 3.1.3. > > Now I don't really ask for, nor expect, that anyone can pinpoint > the problem with this little background information. For a start > I would merely like to hear if anyone has managed to use OpenMPI > on WSL2 in a similar fashion. > > Yours > Johannes > -- Jeff Squyres jsquy...@cisco.com
