Hello Jeff, I think what you suggest is likely exactly what we want to see happen. We run the interop tests with at least two servers, sometimes more. We also have other devices (InfiniBand or RoCE switches) between the servers.
I will have to ask a stupid question here but when you suggest that we open the firewall to trust random TCP connections, how is that different from disabling it? Is there some configuration besides the suggestion by Gilles to specify ports or a range of ports? I thank you. -- Llolsten -----Original Message----- From: users [mailto:users-boun...@open-mpi.org] On Behalf Of Jeff Squyres (jsquyres) Sent: Tuesday, May 10, 2016 3:47 PM To: Open MPI User's List <us...@open-mpi.org> Subject: Re: [OMPI users] mpirun command won't run unless the firewalld daemon is disabled Open MPI generally needs to be able to communicate on random TCP ports between machines in the MPI job (and the machine where mpirun is invoked, if that is a different machine). You could also open your firewall to trust random TCP connections just between the servers in your cluster. > On May 10, 2016, at 3:44 PM, Llolsten Kaonga <l...@soft-forge.com> wrote: > > Hello Orion, > > I actually rather like the new CentOS 7.2 system better and would like > to not remove firewalld. We will try Gilles' suggestion and see what happens. > > I thank you. > -- > Llolsten > > -----Original Message----- > From: users [mailto:users-boun...@open-mpi.org] On Behalf Of Orion > Poplawski > Sent: Tuesday, May 10, 2016 3:31 PM > To: Open MPI Users <us...@open-mpi.org> > Subject: Re: [OMPI users] mpirun command won't run unless the > firewalld daemon is disabled > > On 05/10/2016 09:24 AM, Llolsten Kaonga wrote: >> Hello Durga, >> >> As I mentioned earlier, up to version 1.8.2, we would just disable >> SELinux and the IPv4 firewall and things run smoothly. It was only >> when we installed version 1.10.2 (CentOS 7.2) that we run into these >> troubles. CentOS 7.2 no longer seems to bother with the IPv4 >> firewall, so > you can't do: >> >> >> >> # service iptables save >> >> # service iptables stop >> >> # chkconfig iptables off > > I'll just note that you can either embrace the new firewalld config > (and use firewall-cmd to open your needed ports) or you can remove > firewalld and install iptables-services and go back to the old > iptables method of configuring the firewall. If you don't want a > firewall at all, just remove firewalld. > > -- > Orion Poplawski > Technical Manager 303-415-9701 x222 > NWRA, Boulder/CoRA Office FAX: 303-415-9702 > 3380 Mitchell Lane or...@nwra.com > Boulder, CO 80301 http://www.nwra.com > _______________________________________________ > users mailing list > us...@open-mpi.org > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/users > Link to this post: > http://www.open-mpi.org/community/lists/users/2016/05/29160.php > > > _______________________________________________ > users mailing list > us...@open-mpi.org > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/users > Link to this post: > http://www.open-mpi.org/community/lists/users/2016/05/29161.php -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ _______________________________________________ users mailing list us...@open-mpi.org Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/users Link to this post: http://www.open-mpi.org/community/lists/users/2016/05/29162.php
