Ray, Looking back at your original message, you say that it works if you use the Myricom supplied mpirun from the Myrinet roll. I wonder if this is a mismatch between libraries on the compute nodes.
What do you get if you use your OMPI's mpirun with: $ mpirun -n 1 -H <remote_host> ldd $PWD/<your_binary> I am wondering if ldd find the libraries from your compile or the Myrinet roll. Scott On Oct 21, 2010, at 10:39 AM, Raymond Muno wrote: > On 10/20/2010 8:30 PM, Scott Atchley wrote: >> We have fixed this bug in the most recent 1.4.x and 1.5.x releases. >> >> Scott > OK, a few more tests. I was using PGI 10.4 as the compiler. > > I have now tried OpenMPI 1.4.3 with PGI 10.8 and Intel 11.1. I get the same > results in each case, mpirun seg faults. (I really did not expect that to > change anything). > > I tried OpenMPI 1.5. Under PGI, I could not get it to compile. With Intel > 11.1, it compiles. When I try to run a simple test, mpirun just seems to hang > and I never see anything start on the nodes. I would rather stick with 1.4.x > for now since that is what we are running on our other production cluster. I > will leave this for a later day. > > I grabbed the 1.4.3 version from this page. > > http://www.open-mpi.org/software/ompi/v1.4/ > > When you say this bug is fixed in recent 1.4.x releases, should I try one > from here? > > http://www.open-mpi.org/nightly/v1.4/ > > For grins, I compiled the OpenMPI 1.4.1 tree. This what Myricom supplied > with the MX roll. Same result. I can still run with their compiled version > of mpirun, even when I compile with the other build trees and compilers. I > just do not know what options they compiled with. > > Any insight would be appreciated. > > -Ray Muno > University of Minnesota > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users
