[mpich-discuss] Problem running progrm on MPI cluster

Rajeev Thakur thakur at mcs.anl.gov
Thu Jul 24 10:05:09 CDT 2008


Yes, a.out must be accessible from all machines, for example, via a shared
file system (NFS). If not, then you will need to copy it over. Most users
use a shared file system for the executables.
 
Rajeev


  _____  

From: owner-mpich-discuss at anl.gov [mailto:owner-mpich-discuss at anl.gov] On
Behalf Of Jaydeep Vipradas
Sent: Thursday, July 24, 2008 8:55 AM
To: mpich-discuss at anl.gov
Subject: [mpich-discuss] Problem running progrm on MPI cluster



Hello,

 

I have successfully created MPI cluster of two computers.

mpdcheck , mpdtrace -l, mpdallexit, mpdboot  all commands works fine.

 

Command "mpirun -n 4 hostname" also works fine and shows two host name twice
correctly.

 

But when I try to run a.out it shows error 

   $ mpirun -n 4 ./a.out

   "[Errno 2] No such file or directory".

 

I have also tried by giving full path of the a.out but got the same error.

Note that error is for the second computer of the cluster and no error is
shown for the computer on which a.out is present.

 

I have created this a.out by following command

   $ mpicc test.c

 

Similarly when I run a python script written by me it runs on only one
computer and same error as above is shown for the other host.

  $ mpirun -n 4 python ./myscript.py

Again two processes on the computer one where the file is present shows
correct output but the same error is shown for other two processes which run
on the second computer where myscript.py is not present.

 

When I copied a.out to the second machine in the same path then the program
runs fine without any error.

 

Is it necessary to copy the executable on all computers in the cluster
before running (in the same path)?

Am I missing any command line flags for mpicc or mpirun ?

 

Thanks and Regards,

Jaydeep V.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/mpich-discuss/attachments/20080724/c3fecb69/attachment.htm>


More information about the mpich-discuss mailing list