Well that's fairly odd -- you got no diagnostic information at all.
For some reason, it failed to launch a LAM daemon (lamd) locally. Double
check that if $TMPDIR is set, it exists and is writeable. If it's not
set, ensure that /tmp is set and is writable.
Can you look at the syslog to see if anything came out there describing
the problem?
On Sun, 27 Jun 2004, Yu-Cheng Chou wrote:
> I installed LAM under my root directory on a public Linux machine.
> No error message occurred during the installation process.
>
> But when I run the 'lamboot -v' command, errors occurred:
>
> LAM 7.0.6/MPI 2 C++/ROMIO - Indiana University
>
> n-1<5917> ssi:boot:base:linear: booting n0 (localhost)
> n-1<5917> ssi:boot:base:linear: Failed to boot n0 (localhost)
> n-1<5917> ssi:boot:base:linear: aborted!
> -------------------------------------------------------------------------
> lamboot encountered some error (see above) during the boot process,
> and will now attempt to kill all nodes that it was previously able to
> boot (if any).
>
> Please wait for LAM to finish; if you interrupt this process, you may
> have LAM daemons still running on remote nodes.
> -------------------------------------------------------------------------
> lamboot: wipe -- nothing to do
> lamboot did NOT complete successfully
> make: *** [test] Error 2
>
> How to fix this problem?
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
