________________________________
From: lam-bounces_at_[hidden] <lam-bounces_at_[hidden]>
To: General LAM/MPI mailing list <lam_at_[hidden]>
Sent: Sun Oct 16 10:31:18 2011
Subject: Re: LAM: recon gives ERROR: LAM/MPI unexpectedly received the following on stderr: bash: tkill: command not found
i thought lam was necessary to run mpi programs ..is'nt it ??
how do i setup a cluster for running mpi jobs ??
thank you.
On Sun, Oct 16, 2011 at 6:16 PM, McCalla, Mac <macmccalla_at_[hidden]> wrote:
Hi,
LAM has not been maintained for quite some time. I highly recommend you try www.open-mpi.org instead .
HTH,
Mac in Skiatook
________________________________
From: lam-bounces_at_[hidden] <lam-bounces_at_[hidden]>
To: lam_at_[hidden] <lam_at_[hidden]>
Sent: Sun Oct 16 06:38:03 2011
Subject: LAM: recon gives ERROR: LAM/MPI unexpectedly received the following on stderr: bash: tkill: command not found
when i run recon -v hostfile
the error says it could'nt find tkill in $PATH
ERROR: LAM/MPI unexpectedly received the following on stderr:
bash: tkill: command not found
LAM failed to execute a LAM binary on the remote node "10.5.18.46".
Since LAM was already able to determine your remote shell as "tkill",
it is probable that this is not an authentication problem.
*** 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.
LAM tried to use the remote agent command "/usr/bin/ssh"
to invoke the following command:
/usr/bin/ssh -x -a 10.5.18.46 -n tkill -N -d
This can indicate several things. You should check the following:
- The LAM binaries are in your $PATH
- You can run the LAM binaries
- The $PATH variable is set properly before your
.cshrc/.profile exits
Try to invoke the command listed above manually at a Unix prompt.
surprisingly .. i could'nt invoke the command manually too ..
the path is set correctly ..
I am able to invoke "tkill" independently(seperately by logging into ) on the other node(10.5.18.46) which proves that the path is set properly .. but the command
/usr/bin/ssh -x -a 10.5.18.46 -n tkill -N -d
would still give the error!!!!!
bash: tkill: command not found
please help me with the issue ..
--
Neerati Sravan Kumar.
4th year B.Tech.
Computer Science and Engineering.
Indian Institute of Technology,Kharagpur.
This e-mail and any attachments are for the sole use of the intended recipient(s) and may contain information that is confidential. If you are not the intended recipient(s) and have received this e-mail in error, please immediately notify the sender by return e-mail and delete this e-mail from your computer. Any distribution, disclosure or the taking of any other action by anyone other than the intended recipient(s) is strictly prohibited.
_______________________________________________
This list is archived at http://www.lam-mpi.org/MailArchives/lam/
--
Neerati Sravan Kumar.
4th year B.Tech.
Computer Science and Engineering.
Indian Institute of Technology,Kharagpur.
This e-mail and any attachments are for the sole use of the intended recipient(s) and may contain information that is confidential. If you are not the intended recipient(s) and have received this e-mail in error, please immediately notify the sender by return e-mail and delete this e-mail from your computer. Any distribution, disclosure or the taking of any other action by anyone other than the intended recipient(s) is strictly prohibited.
|
