Hi Howard, > On 27 Aug 2015, at 17:48 , Howard Pritchard <hpprit...@gmail.com> wrote: > I think you're hitting an RSIP port limit.
Thats sounds like it indeed. > If you bind to ipogif0 then you should have much better luck, unless > you're trying to have open mpi span outside the cray HPN. Now you get me wondering. I actually played with both oob-tcp-if-include and -exclude , but possibly not in the right context I realize now. Let me undo my changes and try with only the configuration changes. Thanks! Mark > > You can use the oob mca parameter: > > oob-tcp-if-include ipogif0 > > You may want to put that in your .openmpi/mca-params.conf file if you have > one installed, but > don't forget if your home directory is accesible from different machines, > some of which may > not be Cray XE/XC then probably don't want to do that. Messed me up with > runs on carver > system at NERSC for a while. > > Howard > > > 2015-08-27 9:42 GMT-06:00 Mark Santcroos <mark.santcr...@rutgers.edu>: > Hi, > > For some reason that is currently still beyond me, I can't bind to INADDR_ANY > for more than 74 ports on a Cray compute node, without getting EADDRINUSE. > This impacts my use of the oob_tcp_listener.c:create_listen() code on that > machine (through means of orte-submit). > > I've implemented a proof of concept that gets the address from a hardcoded > interface and uses that for the binding, and then everything is hunky dory. > > Although I'm interested in the root cause also, that may likely be outside of > my control, so I wonder whether the hack can be turned into something more > appropriate. > > So some questions: > > - I can't stop to think that somewhere in the codebase there is probably some > portable code to extract addresses from an interface. > - Is there already some MCA parameter that can be (re)used to specify the > interface to use for this kind of purpose. > - (And why is the "client" listening on a socket in the first place?) > > Thanks! > > Mark > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2015/08/17882.php > > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2015/08/17884.php
