OK,
Thanks for your help.
Mike...
On 02/26/2018 05:07 PM, Marco Atzeri wrote:
> On 26/02/2018 22:57, Michael A. Saverino wrote:
>>
>> Marco,
>>
>> If you disable the loopback as well as the other adapters via Device
>> Manager, you should be able to reproduce the error.
>>
>> Mike...
>
> It
On 26/02/2018 22:57, Michael A. Saverino wrote:
Marco,
If you disable the loopback as well as the other adapters via Device
Manager, you should be able to reproduce the error.
Mike...
It worked with also the loopback disabled.
Probably the installation of the loopback just enabled some
Marco,
If you disable the loopback as well as the other adapters via Device
Manager, you should be able to reproduce the error.
Mike...
On 02/26/2018 04:51 PM, Marco Atzeri wrote:
> On 26/02/2018 22:10, Michael A. Saverino wrote:
>>
>> Marco,
>>
>> I think oob still has a problem, at least on
On 26/02/2018 22:10, Michael A. Saverino wrote:
Marco,
I think oob still has a problem, at least on my machine, even though we
specify --mca oob ^tcp. The workaround I found is to install the
Microsoft loopback adapter. That satisfies OPMI at startup even though
the ethernet or WiFi is
Marco,
I think oob still has a problem, at least on my machine, even though we
specify --mca oob ^tcp. The workaround I found is to install the
Microsoft loopback adapter. That satisfies OPMI at startup even though
the ethernet or WiFi is either disabled or disconnected. You still have
to
On 26/02/2018 18:14, Michael A. Saverino wrote:
I am running the v-1.10.7 OMPI package that is available via the Cygwin
package manager. I have a requirement to run my OMPI application
standalone on a Windows/Cygwin system without any network connectivity.
If my OMPI system is not connected to
Thank you for the quick response. Your suggested commands did not work
with the network interface disabled or unplugged. I still get:
[SAXM4WIN:02124] [[20996,1],0] tcp_peer_send_blocking: send() to socket
12 failed: Transport endpoint is not connected (128)
So, in spite of including --mca
There are a couple of problems here. First the “^tcp,self,sm” is telling OMPI
to turn off all three of those transports, which probably leaves you with
nothing. What you really want is to restrict to shared memory, so your param
should be “-mca btl self,sm”. This will disable all transports
I am running the v-1.10.7 OMPI package that is available via the Cygwin
package manager. I have a requirement to run my OMPI application
standalone on a Windows/Cygwin system without any network connectivity.
If my OMPI system is not connected to the network, I get the following
errors when I
