Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Open MPI User's mailing list

From: Alex Tumanov (atumanov_at_[hidden])
Date: 2007-02-07 17:37:41


> mpirun -np 2 myprogram inputfile >outputfile
There can be a whole host of issues with the way you run your
executable and/or the way you have the environment setup. First of
all, when you ssh into the node, does the environment automatically
get updated with correct Open MPI paths? I.e. LD_LIBRARY_PATH should
be correctly set to the OMPI lib directory, PATH should contain OMPI's
bin dir, etc. If this is not the case, you have two options:
a. create small /etc/profile.d scripts to set up those env. variables
b. use --prefix version when you invoke mpirun on the headnode

Generally, it would be much more helpful if you provided the actual
output of running the commands you listed here.

> mpirun --hostfile myhostfile -np 4 myprogram inputfile >outputfile
Another issue I can think of is path specification to 'myprogram'. Do
you just cd into the directory where it resides and specify its name
only? Try to either specify an absolute path to the executable or path
relative to your homedir: ~/appdir/bin/appexec, assuming this location
is the same on all the nodes. If mpirun can't find your executable on
one of the nodes, it should report that as an error.

> which does not write to the output file.
Does it write anything to stderr? You could also try invoking mpirun
with '--mca pls_rsh_agent ssh'

> mpirun --hostfile myhostfile -np 4 `myprogram inputfile >outputfile`
Are those backquotes?? I would recommend getting mpirun to invoke
something basic on all the participating nodes successfully first, try
mpirun --prefix /path/to/ompi/ --hostfile myhosfile --np 4 hostname
for instance. Nothing else will work until this does.

These are just a few pointers to get you started. Hope this helps.