Hello Durga,
These are dedicated servers we use to run Interoperability testing and it is just easier for us to use a privileged user account. 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 That was our first sign of “trouble”. (-; I will try to run the command with the option to specify the port(s) per Gilles’ suggestion and see what happens. I thank you. -- Llolsten From: users [mailto:users-boun...@open-mpi.org] On Behalf Of dpchoudh . Sent: Monday, May 09, 2016 4:44 PM To: Open MPI Users <us...@open-mpi.org> Subject: Re: [OMPI users] mpirun command won't run unless the firewalld daemon is disabled Hello Llolsten Is there a specific reason you run as root? This practice is discouraged, isn't it? Also, isn't it true that OMPI uses ephemeral (i.e. 'user level, randomly chosen') ports for TCP transport? In that case, how did this ever worked with a firewall enabled? I have, in the past, have faced similar situations, thus I am curious to know the answer as well. Thanks Durga The surgeon general advises you to eat right, exercise regularly and quit ageing. On Mon, May 9, 2016 at 2:31 PM, Llolsten Kaonga <l...@soft-forge.com <mailto:l...@soft-forge.com> > wrote: Hello all, We’ve been running openmpi for a long time and up to version 1.8.2 and CentOS 6.7 with commands such as the one below: usr/local/bin/mpirun --allow-run-as-root --mca btl openib,self,sm --mca pml ob1 -np 2 -np 8 -hostfile /root/mpi-hosts /usr/local/bin/IMB-MPI1 To be able to run the above command, we normally just disabled the IPv4 firewall and SELinux. We recently made the following updates: OS: CentOS 7.2 IMB: 4.1 OpenMPI: 1.10.2 When we tried to execute the above mpirun command, we got a TCP Broken Pipe error. There was no IP assignment conflict and eventually, we narrowed down the problem to the firewall. Disabling the firewalld daemon allows the command to run to completion. We would prefer not to disable the daemon as our servers may sometimes be connected to the rest of our subnet. Are there other options such as perhaps specifying a port (I am guessing, so specific instructions will be greatly appreciated). I thank you. _______________________________________________ users mailing list us...@open-mpi.org <mailto: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/29143.php
