LAM/MPI logo

LAM/MPI General User's Mailing List Archives

  |   Home   |   Download   |   Documentation   |   FAQ   |   all just in this list

From: Amey Dharurkar (adharurk_at_[hidden])
Date: 2003-09-26 14:04:28


Hello,
First of all I would like to tell you that LAM 7.0 has more
features than LAM 6.5.9 and I strongly encourage you concentrate on LAM
7.0

> I am unable to install LAM properly,If someone guide me in this,I have tried both lam-6.5.9 and lam-7.0.
>
> 1-
>
> After the installation of lam-7.0 with
>
> "./configure --with-rsh=RSH"
>
> i face following error,
>
> -----------------------------------------------------------------------------
>
> [Ahmed_at_localhost MPI-examples]$ lamboot
>
> -----------------------------------------------------------------------------
>
> No SSI boot modules said that they were available to run. This should
>
> not happen.
>
> -----------------------------------------------------------------------------

This happens because LAM has not builded properly. Try using laminfo
command to see if you get SSI boot and SSI rpi modules in the list. Send
the output of laminfo command which will give us more idea.

Also try looking at the LAM 7.0 installation manual.
http://www.lam-mpi.org/using/docs/

> 2-
>
> After the successful installation of lam-6.5.9, After the command " lamboot "
>
> -----------------------------------------------------------------------------
>
> [Ahmed_at_localhost ring]$ mpirun -np 3 ring
>
> -----------------------------------------------------------------------------
>
> It seems that there is no lamd running on this host, which indicates
>
> that the LAM/MPI runtime environment is not operating. The LAM/MPI
>
> runtime environment is necessary for the "mpirun" command.
>
> Please run the "lamboot" command the start the LAM/MPI runtime
>
> environment. See the LAM/MPI documentation for how to invoke
>
> "lamboot" across multiple machines.
>
> -----------------------------------------------------------------------------
>

This happens because LAM daemon is not running on the local machine. Your
lamboot may have failed in the above case.

Hope this helps

-Amey