It took me quite a while, but I have finally traced this back to a bug
in 1.3.0. The confusion was caused by the original cited issue of a
problem when the exes had different names. This proved incorrect.
The key was your final statement about having both exes available on
all nodes. This i
Hi Ralph,
Thanks for taking time to look into my problem. As you can see , it happens
when i dont have both exe available on both nodes.
When it's the case (test3) , it works. I dont know if my particular libdir
causes the problem or not but I 'll try on Monday with a more classical
setup.
I ll
HI Geoffrey
Hmmmwell, I redid my tests to mirror yours, and still cannot
replicate this problem. I tried it with both slurm and ssh
environments - no difference in the results.
% make hello
% cp hello hello2
% ls
hello hello2
% mpirun -n 1 -host odin038 ./hello : -n 1 -host odin039 .
Hello
I redid few tests with my hello world , here are my results.
First of all my config :
configure --prefix=/tmp/openmpi-1.3 --libdir=/tmp/openmpi-1.3/lib64
--enable-heterogeneous . you will find attached my ompi_info -param all all
compil02 and compil03 are identical Rh43 64 bits nodes.
*Tes
I can't replicate that behavior - it all seems to be working just
fine. I can launch apps of different name, we correctly detect and
respond to missing executables, etc.
Can you provide more info as to how this was built? Also, be sure to
check that the remote hosts are using the same versi
Hello , still a bug ???
compil03% /tmp/openmpi-1.3/bin/mpirun -n 1 --wdir /tmp --host compil03 a.out
: -n 1 --host compil02 a.out
Hello world from process 0 of 2
Hello world from process 1 of 2
compil03% mv a.out a.out_32
compil03% /tmp/openmpi-1.3/bin/mpirun -n 1 --wdir /tmp --host compil03
a.ou
