The most common cause for this is when you have some other executable
of the same name in your PATH that LAM found before the intended one
(e.g., have something else in your PATH named "ring"). Do a "which
ring" and see if this is true. If it is, then what is happening is
that LAM is running the "wrong" ring program, which never invokes
MPI_INIT. You can fix this by either fixing your PATH or by mpirun'ing
the absolute path name of your MPI ring.
Let me know if this is not the issue.
On Jul 1, 2005, at 5:15 PM, Marcelo Fukushima wrote:
> hi fellows!! im pretty urgent here, trying to figure how to make mpi
> work and im receiving this msg when running the mpirun:
>
> -----------------------------------------------------------------------
> ------
> It seems that [at least] one of the processes that was started with
> mpirun did not invoke MPI_INIT before quitting (it is possible that
> more than one process did not invoke MPI_INIT -- mpirun was only
> notified of the first one, which was on node n0).
>
> mpirun can *only* be used with MPI programs (i.e., programs that
> invoke MPI_INIT and MPI_FINALIZE). You can use the "lamexec" program
> to run non-MPI programs over the lambooted nodes.
> -----------------------------------------------------------------------
> ------
>
> im trying the ring example from the tutorial section... any help is
> apreciated
>
>
> --
> []'s
> Marcelo Takeshi Fukushima
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
