Hello, I have installed Ope
 

Hello,

I have installed OpenFOAM-1.4 on a linux machine running on Redhat enterprise 4. I was able to complete the installation, and I'm now trying to setup the mpi capability.

I generated keys with ssh-keygen and I can connect to a second computer without passwords. The error I get after launching lamboot -v <myfile> is:

LAM 7.1.2 - Indiana University

n-1<6232> ssi:boot:base:linear: booting n0 (128.61.185.163)
-----------------------------------------------------------------------------
The lamboot agent failed to read a message over a socket from the
newly-booted process. This should not happen (especially since TCP is
a guaranteed protocol).

*** PLEASE READ THIS ENTIRE MESSAGE, FOLLOW ITS SUGGESTIONS, AND
*** CONSULT THE "BOOTING LAM" SECTION OF THE LAM/MPI FAQ
*** (http://www.lam-mpi.org/faq/) BEFORE POSTING TO THE LAM/MPI USER'S
*** MAILING LIST.

You should probably check the following:

- Network connectivity: Ensure that messages can be passed reliably
over TCP using random ports.
- Environment / PATH settings: Ensure that you are running the same
version of LAM/MPI on all nodes. Sometimes premature disconnects
(and therefore this error message) may be caused if mismatched
versions of LAM are used on different nodes.
- Node health: Ensure that the host where the newly-booted process was
launched is healthy and still available on the network.
-----------------------------------------------------------------------------
n-1<6232> ssi:boot:base:linear: aborted!
lamboot did NOT complete successfully


Do I need to install the lam verision that comes with OpenFOAM on all the machines that I will be running via OpenFOAM?

Thank you in advance

If I'm not wrong, lamboot try
 

If I'm not wrong, lamboot try to check if it can open a ssh connection with the other specified machines.
Basicly, it execute a command through ssh and check the standard error. Execute "lamboot -v" to have some more verbose output.
In my case, the error was due to the X11 forwarding.
I remeber I resolved it by using "ssh -x" as remote connection client. Check in the lamport documentation how to do this... I really don't remember what I did, and I'm not using that system anymore...

Hope this can be a starting point...
Francesco