LAM/MPI logo

LAM/MPI General User's Mailing List Archives

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

From: raja (raja_28_at_[hidden])
Date: 2006-05-06 02:33:38


Dear all,
The following error reporting for the command "lamboot -d" in cygwin in
Windowxp for lam-7.1.1.
Kindly help me to fix this error.
###################################################################################################
$ lamboot -d
n-1<2232> ssi:boot:open: opening
n-1<2232> ssi:boot:open: opening boot module globus
n-1<2232> ssi:boot:open: opened boot module globus
n-1<2232> ssi:boot:open: opening boot module rsh
n-1<2232> ssi:boot:open: opened boot module rsh
n-1<2232> ssi:boot:open: opening boot module slurm
n-1<2232> ssi:boot:open: opened boot module slurm
n-1<2232> ssi:boot:select: initializing boot module globus
n-1<2232> ssi:boot:globus: globus-job-run not found, globus boot will
not run
n-1<2232> ssi:boot:select: boot module not available: globus
n-1<2232> ssi:boot:select: initializing boot module rsh
n-1<2232> ssi:boot:rsh: module initializing
n-1<2232> ssi:boot:rsh:agent: rsh
n-1<2232> ssi:boot:rsh:username: <same>
n-1<2232> ssi:boot:rsh:verbose: 1000
n-1<2232> ssi:boot:rsh:algorithm: linear
n-1<2232> ssi:boot:rsh:no_n: 0
n-1<2232> ssi:boot:rsh:no_profile: 0
n-1<2232> ssi:boot:rsh:fast: 0
n-1<2232> ssi:boot:rsh:ignore_stderr: 0
n-1<2232> ssi:boot:rsh:priority: 10
n-1<2232> ssi:boot:select: boot module available: rsh, priority: 10
n-1<2232> ssi:boot:select: initializing boot module slurm
n-1<2232> ssi:boot:slurm: not running under SLURM
n-1<2232> ssi:boot:select: boot module not available: slurm
$
n-1<2232> ssi:boot:globus: finalizing
n-1<2232> ssi:boot:select: closing boot module globus
n-1<2232> ssi:boot:select: finalizing boot module slurm
n-1<2232> ssi:boot:slurm: finalizing
n-1<2232> ssi:boot:select: closing boot module slurm
n-1<2232> ssi:boot:select: selected boot module rsh

LAM 7.1.1/MPI 2 C++ - Indiana University

n-1<2232> ssi:boot:base: looking for boot schema in following
directories:
n-1<2232> ssi:boot:base: <current directory>
n-1<2232> ssi:boot:base: $TROLLIUSHOME/etc
n-1<2232> ssi:boot:base: $LAMHOME/etc
n-1<2232> ssi:boot:base: /usr/local/etc
n-1<2232> ssi:boot:base: looking for boot schema file:
n-1<2232> ssi:boot:base: lam-bhost.def
n-1<2232> ssi:boot:base: found boot schema: /usr/local/etc/lam-bhost.def
n-1<2232> ssi:boot:rsh: found the following hosts:
n-1<2232> ssi:boot:rsh: n0 localhost (cpu=1)
n-1<2232> ssi:boot:rsh: resolved hosts:
n-1<2232> ssi:boot:rsh: n0 localhost --> 127.0.0.1 (origin)
n-1<2232> ssi:boot:rsh: starting RTE procs
n-1<2232> ssi:boot:base:linear: starting
n-1<2232> ssi:boot:base:server: opening server TCP socket
n-1<2232> ssi:boot:base:server: opened port 1424
n-1<2232> ssi:boot:base:linear: booting n0 (localhost)
n-1<2232> ssi:boot:rsh: starting lamd on (localhost)
n-1<2232> ssi:boot:rsh: starting on n0 (localhost): hboot -t -c
lam-conf.lamd
 -I -H 127.0.0.1 -P 1424 -n 0 -o 0
n-1<2232> ssi:boot:rsh: launching locally
-----------------------------------------------------------------------------
" in your path. find the executable "

Things to check:

" in your $PATH?
        - Does your .cshrc/.profile set your $PATH properly?

The following Unix error message may be helpful:

        Unix errno: 2
        No such file or directory

-----------------------------------------------------------------------------
n-1<2232> ssi:boot:base:linear: Failed to boot n0 (localhost)
n-1<2232> ssi:boot:base:server: closing server socket
n-1<2232> ssi:boot:base:linear: aborted!
lamboot did NOT complete successfully
#############################################################################################

With thanks !
B.Nataraj

-- 
  raja
  raja_28_at_[hidden]
-- 
http://www.fastmail.fm - A no graphics, no pop-ups email service