On Sat, 12 Jul 2003, Sergei Lisenkov wrote:
> n0<21591> ssi:boot:base:linear: booting n1 (panda2)
> ERROR: LAM/MPI unexpectedly received the following on stderr:
> bash: line 1: hboot: command not found
> -----------------------------------------------------------------------------
> LAM attempted to execute a process on the remote node "panda2",
> but received some output on the standard error.
>
> LAM tried to use the remote agent command "rsh"
> to invoke "hboot" on the remote node.
As the error message says, the shell was unable to find an application
called 'hboot' on panda2. There are a number of reasons this can happen.
The most likely causes are that LAM isn't installed on Panda2 or LAM isn't
in your $PATH on panda2 when logging in via a non-interactive shell.
Not all dot files are processed when rsh or ssh starts a non-interactive
shell. This usually causes problems with $PATH being set unexpectedly.
A more detailed explination is available in the LAM/MPI 7.0 User's Guide,
available on our web page and in the distribution tarball.
Hope this helps,
Brian
--
Brian Barrett
LAM/MPI developer and all around nice guy
Have a LAM/MPI day: http://www.lam-mpi.org/
|
