Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Open MPI User's mailing list

Subject: Re: [OMPI users] Issue with : mca_oob_tcp_peer_recv_connect_ack on SGI Altix
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2010-12-15 19:40:47

On Dec 15, 2010, at 3:24 PM, Ralph Castain wrote:

>> I am not using the TCP BTL, only OPENIB one. Does this change the number of sockets in use per node, please ?
> I believe the openib btl opens sockets for connection purposes, so the count is likely the same. An IB person can confirm that...

Nope -- the openib BTL uses the daemon-based communication mechanism. So it should only use the TCP ports that are already open.

Does this problem *always* happen, or does it only happen once in a great while?

I've seen a similar problem with the TCP BTL every once in a great while -- where a random, errant (non-Open MPI) process connects to a socket that Open MPI is listening on (regardless of whether it's the TCP BTL or TCP OOB). This causes badness in Open MPI because we don't verify the connector properly, and more importantly, don't handle it nicely when the connector is not Open MPI. I've seen this happen with network malware scanners, for example -- they try to connect to large swaths of TCP ports and sometimes unluckily hit an open Open MPI TCP port.

We have a fix for this coming in a future version of the TCP BTL; looks like we should also harden this up for the TCP OOB as well...

Jeff Squyres
For corporate legal information go to: