This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
My mpi application is hanging forever when called with mpirun -np >1 (that is 2 or more... not actually typing the '>').
So I built openmpi 1.4.3 with default options except I used -prefix=/usr/local/openmpi. I compiled an application against it but I need to run this application elsewhere. So brought in my entire installation directory /usr/local/openmpi to this new machine along with my binary to test it. Ran the following command... (If i did't use the -mca options it would print out messages about missing OpenFrabric):
/usr/local/openmpi/bin/mpirun --mca btl tcp,self -np 2 ./my_application
This actually works for -np 1. But requesting another process makes the call hang forever. 'strace' of the above call shows an never ending calls to "poll" resulting in (timeout) every time.
Executing /usr/local/openmpi/bin/ompi_info still shows the configure and build host as the machine I built on, but I don't know if this may cause a problem. I also see "Thread support: posix (mpi: no, progress: no)"
Unfortunately I need to do it this way.. I cannot build openmpi on the target machine, so I need to make it portable. This other machine should be the same architecture and OS and everything.
I should have solved this yesterday, please help, and thanks!