Hi,
The version of LAM is 6.3.2
The output of recon -vd:
recon: opening hostfile /usr/local/lammpi/boot/bhost.def
recon: found the following hosts:
recon: n0 flapjack.incyte.com
recon: found addresses for all hosts
recon: no duplicated hosts (good)
recon: found 1 host node(s)
recon: origin node is n0 (flapjack.incyte.com)
recon: -- testing n0 (flapjack.incyte.com)
recon: attempting to launch "tkill -N" (local execution)
recon: launch successful
-----------------------------------------------------------------------------
Woo hoo!
recon has completed successfully. This means that you will most likely
be able to boot LAM successfully with the "lamboot" command (but this
is not a guarantee). See the lamboot(1) manual page for more
information on the lamboot command.
If you have problems booting LAM (with lamboot) even though recon
worked successfully, enable the "-d" option to lamboot to examine each
step of lamboot and see what fails. Most situations where recon
succeeds and lamboot fails have to do with the hboot(1) command (that
lamboot invokes on each host in the hostfile).
-----------------------------------------------------------------------------
The output of lamboot -d:
LAM 6.3.2/MPI 2 C++ - University of Notre Dame
lamboot: boot schema file: /usr/local/lammpi/boot/bhost.def
lamboot: opening hostfile /usr/local/lammpi/boot/bhost.def
lamboot: found the following hosts:
lamboot: n0 flapjack.incyte.com
lamboot: found 1 host node(s)
lamboot: origin node is 0 (flapjack.incyte.com)
lamboot: attempting to execute "hboot -t -c conf.lam -d -I " -H 10.35.3.147 -P 1257 -n 0 -o 0 ""
hboot: process schema = "/usr/local/lammpi/boot/conf.lam"
hboot: found /usr/local/lammpi/bin/lamd
hboot: performing tkill
hboot: booting...
hboot: fork /usr/local/lammpi/bin/lamd
[1] 16696 lamd -H 10.35.3.147 -P 1257 -n 0 -o 0
hboot: attempting to execute
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
wipe ...
LAM 6.3.2 - University of Notre Dame
Executing tkill on n0 (flapjack.incyte.com)...
lamboot did NOT complete successfully
Thanks again!
-Karl
_______________________________________________
This list is archived at http://www.lam-mpi.org/MailArchives/lam/
|
