According to the error message (especially since it's consistent across 2 
different platforms), it looks like you have an error in your application.  
Open MPI says that you're using an invalid communicator when calling 
MPI_Cart_shift.  "Invalid" probably means that it's not a Cartesian 
communicator.

You might want to double check the definition and requirements of the 
MPI_CART_SHIFT function (see the MPI_Cart_shift(3) man page).



On Jul 28, 2010, at 12:28 PM, christophe petit wrote:

> hello,
> 
> i have a problem concerning the execution of a f90 program (explicitPar) 
> compiled with openmpi-1.4.2. I get nearly the same error on my debian desktop 
> ( AMD Phenom(tm) 9550 Quad-Core Processor) and my mac pro i7 laptop :
> 
> on mac pro i7 :
> 
> $ mpiexec -np 2 explicitPar
> [macbook-pro-de-fab.livebox.home:48805] *** An error occurred in 
> MPI_Cart_shift
> [macbook-pro-de-fab.livebox.home:48805] *** on communicator MPI_COMM_WORLD
> [macbook-pro-de-fab.livebox.home:48805] *** MPI_ERR_COMM: invalid communicator
> [macbook-pro-de-fab.livebox.home:48805] *** MPI_ERRORS_ARE_FATAL (your MPI 
> job will now abort)
> --------------------------------------------------------------------------
> mpiexec has exited due to process rank 1 with PID 48805 on
> node macbook-pro-de-fab.livebox.home exiting without calling "finalize". This 
> may
> have caused other processes in the application to be
> terminated by signals sent by mpiexec (as reported here).
> 
> ---------------------------------------------------------------------------
> 
> on my debian desktop :
> 
> mpirun -np 2 explicitPar
> [pablo:11665] *** An error occurred in MPI_Cart_shift
> [pablo:11665] *** on communicator MPI_COMM_WORLD
> [pablo:11665] *** MPI_ERR_COMM: invalid communicator
> [pablo:11665] *** MPI_ERRORS_ARE_FATAL (your MPI job will now abort)
> --------------------------------------------------------------------------
> mpirun has exited due to process rank 1 with PID 11665 on
> node pablo exiting without calling "finalize". This may
> have caused other processes in the application to be
> terminated by signals sent by mpirun (as reported here).
> --------------------------------------------------------------------------
> 
> 
> I have installed openmpi-1.4.2 with the following options :
> 
> ./configure --prefix=/usr/local/openmpi --enable-mpi-f77 --enable-mpi-f90
> 
> with exported variables on bash shell : FC=gfortran F90=gfortran F77=gfortran 
> CC=gcc CXX=g++
> 
> The  installation has been completed, the program compiles fine but i don't 
> understand what's wrong. I note that with a single processor ("mpirun -np 1 
> explicitPar"), execution works fine.
> 
> My debian desktop is a quad-core, so, theoretically, i can put up to 4 for 
> "np" parameter.
> On my mac pro i7, i don't know how processors are there, but the "htop" 
> command makes appear 4 cores too.
> 
> Anyone has a solution ?
> 
> Regards.
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/


Reply via email to