Brian,
Thanks for your help, but I think I did a poor job of explaining my problem. Let me try again. I can get either of these two errors:
mpirun -ssi rpi tcp C ./sphu
-----------------------------------------------------------------------------
It seems that [at least] one of the processes that was started with
mpirun chose a different RPI than its peers. For example, at least
the following two processes mismatched in their RPI selections:
MPI_COMM_WORLD rank 1: tcp (v7.1.0)
MPI_COMM_WORLD rank 0: tcp (v7.0.0)
All MPI processes must choose the same RPI module and version when
they start. Check your SSI settings and/or the local environment
variables on each node.
-----------------------------------------------------------------------------
mpirun -ssi rpi usysv C ./sphu
-----------------------------------------------------------------------------
It seems that [at least] one of the processes that was started with
mpirun chose a different RPI than its peers. For example, at least
the following two processes mismatched in their RPI selections:
MPI_COMM_WORLD rank 1: usysv (v7.1.0)
MPI_COMM_WORLD rank 0: usysv (v7.0.0)
All MPI processes must choose the same RPI module and version when
they start. Check your SSI settings and/or the local environment
variables on each node.
-----------------------------------------------------------------------------
When I do laminfo on both machines, they both include:
SSI rpi: tcp (API v1.0, Module v7.1)
SSI rpi: usysv (API v1.0, Module v7.1)
It looks like rank 0 should have (v7.1.0) instead of (v7.0.0), but maybe I just don't understand the error. Thanks a lot.
Eric
> On Jun 22, 2005, at 3:54 PM, smiler21_at_[hidden] wrote:
>
> > Hi, I'm trying to run a code between Mac and Linux and I'm getting
> > this error:
> >
> > -----------------------------------------------------------------------
> > ------
> > It seems that [at least] one of the processes that was started with
> > mpirun chose a different RPI than its peers. For example, at least
> > the following two processes mismatched in their RPI selections:
> >
> > MPI_COMM_WORLD rank 1: usysv (v7.1.0)
> > MPI_COMM_WORLD rank 0: tcp (v7.0.0)
> >
> > All MPI processes must choose the same RPI module and version when
> > they start. Check your SSI settings and/or the local environment
> > variables on each node.
> > -----------------------------------------------------------------------
> > ------
> >
> > (The mac is node 0.) I read the post on forcing both machines to use
> > tcp, but is there a way to force versions to be the same? Or am I
> > going to have to download the correct versions?
>
> This probably happened because one node has usysv support and the other
> doesn't. You can run "laminfo" on both machines to get a list of
> supported modules. If usysv doesn't appear on the Mac list, then
> you'll either have to use a module that is available on both machines
> or rebuild LAM for the Mac.
>
> Note that there is a bug in the USYSV rpi for G5 hardware. If you are
> running on a G5, you should either avoid the USYSV rpi or upgrade to
> LAM 7.1.2b22.
>
> Hope this helps,
>
> Brian
>
> --
> Brian Barrett
> LAM/MPI developer and all around nice guy
> Have a LAM/MPI day: http://www.lam-mpi.org/
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
|
