Re: [OMPI users] OMPI 4.1 in Cygwin packages?

Martin, at first glance, I could not spot the root cause. That being said, the second note is sometimes referred as "WinDev2021Eval" in the logs, but it is also referred as "worker". What if you use the real names in your hostfile: DESKTOP-C0G4680 and WinDev2021Eval instead of master and

Re: [OMPI users] OMPI 4.1 in Cygwin packages?

Hello all, Gilles, unfortunately, the result is the same. Attached the log you ask me. Jeff, some time ago I tried with OMPI 4.1.0 (Linux) and it worked. Thank you both. Regards, Martín From: Jeff Squyres (jsquyres) via users Sent: jueves, 4 de febrero de 2021

Re: [OMPI users] OMPI 4.1 in Cygwin packages?

Do we know if this was definitely fixed in v4.1.x? > On Feb 4, 2021, at 7:46 AM, Gilles Gouaillardet via users > wrote: > > Martin, > > this is a connectivity issue reported by the btl/tcp component. > > You can try restricting the IP interface to a subnet known to work > (and with no

Re: [OMPI users] OMPI 4.1 in Cygwin packages?

Martin, this is a connectivity issue reported by the btl/tcp component. You can try restricting the IP interface to a subnet known to work (and with no firewall) between both hosts mpirun --mca btl_tcp_if_include 192.168.0.0/24 ... If the error persists, you can mpirun --mca

Re: [OMPI users] OMPI 4.1 in Cygwin packages?

Hi Marcos, Yes, I have a problem with spawning to a “worker” host (on localhost, works). There are just two machines: “master” and “worker”. I’m using Windows 10 in both with same Cygwin and packages. Pasted below some details. Thanks for your help. Regards, Martín Running: mpirun -np