i tried
$ rsh 11.11.11.2 -n tkill -N -v
bash: line 1: tkill: command not found
what's the meaning?
=====================================================
a file named tmpset in ~/
in the tmpset file:
export PATH=/u2/test/Lenjoy/LAMHOME/bin:and so on...
export LD_LIBRARY_PATH=/u2/test/Lenjoy/LAMHOME/lib:and so on...
what i did:
*/u2/test $ . tmpset*
*/u2/test $ rsh node2*
Last login: Sun Mar 5 22:39:39 from node1
[test_at_node2 test]$ *. tmpset*
[test_at_node2 test]$* rsh node3
*Last login: Sun Mar 5 22:33:39 from node2
[test_at_node3 test]$ *. tmpset*
[test_at_node3 test]$ *rsh node4*
Last login: Sun Mar 5 22:33:39 from node3
[test_at_node4 test]$* . tmpset*
[test_at_node4 test]$ *lamboot Lenjoy/envset/lamhosts*
LAM 7.1.1/MPI 2 C++/ROMIO - Indiana University
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 "11.11.11.1",
but received some output on the standard error. This heuristic
assumes that any output on the standard error indicates a fatal error,
and therefore aborts. You can disable this behavior (i.e., have LAM
ignore output on standard error) in the rsh boot module by setting the
SSI parameter boot_rsh_ignore_stderr to 1.
LAM tried to use the remote agent command "rsh"
to invoke "hboot" on the remote node.
*** 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.
This can indicate an authentication error with the remote agent, or
can indicate an error in your $HOME/.cshrc, $HOME/.login, or
$HOME/.profile files. The following is a (non-inclusive) list of items
that you should check on the remote node:
- You have an account and can login to the remote machine
- Incorrect permissions on your home directory (should
probably be 0755)
- Incorrect permissions on your $HOME/.rhosts file (if you are
using rsh -- they should probably be 0644)
- You have an entry in the remote $HOME/.rhosts file (if you
are using rsh) for the machine and username that you are
running from
- Your .cshrc/.profile must not print anything out to the
standard error
- Your .cshrc/.profile should set a correct TERM type
- Your .cshrc/.profile should set the SHELL environment
variable to your default shell
Try invoking the following command at the unix command line:
rsh 11.11.11.1 -n hboot -t -c lam-conf.lamd -s -I '"-H 11.11.11.4 -P
37018 -n 0 -o 3"'
You will need to configure your local setup such that you will *not*
be prompted for a password to invoke this command on the remote node.
No output should be printed from the remote node before the output of
the command is displayed.
When you can get this command to execute successfully by hand, LAM
will probably be able to function properly.
-----------------------------------------------------------------------------
2006/3/5, Andrew Friedley <afriedle_at_[hidden]>:
>
> Mars Lenjoy wrote:
> > $ recon -v lamhosts
> > n-1<21389> ssi:boot:base:linear: booting n0 (11.11.11.1)
> > n-1<21389> ssi:boot:base:linear: booting n1 (11.11.11.2)
> > ERROR: LAM/MPI unexpectedly received the following on stderr:
> > bash: line 1: tkill: command not found
>
> Have you set up your PATH and LD_LIBRARY_PATH correctly on all nodes?
> These must be set via some sort of login script, and must be done for
> non-interactive logins.
>
> > Try invoking the following command at the unix command line:
> >
> > rsh 11.11.11.2 -n tkill -N -v
>
> Have you done this? What happens?
>
> > n-1<21389> ssi:boot:base:linear: Failed to boot n1 (11.11.11.2)
> > n-1<21389> ssi:boot:base:linear: aborted!
> >
> > =============================== end
> > ==============================================
> >
> > why are only n-0 and n-1 tested, but not n2-5?
>
> Testing stops when any sort of error occurs, like what happened for n1.
> When n1 succeeds recon will continue to the other nodes.
>
> > if I use lamboot without any parameter
> >
> > ===================== begin =============
> >
> > *$ lamboot*
> >
> > LAM 7.1.1/MPI 2 C++/ROMIO - Indiana University
> >
> > *$ ps aux | grep lam
> > *test 21695 0.0 0.0 2260 1048 ? S 23:16 0:00
> > /u2/test/Lenjoy/LAMHOME/bin/lamd -H 127.0.0.1 -P 36823 -n 0 -o 0
> > test 21713 0.0 0.0 3580 656 pts/4 S 23:16 0:00 grep lam
> >
> > ======================== end ======================
>
> This is because you are only lamboot'ing the local node, not any remote
> nodes.
>
> Andrew
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
|
