MPIEXEC IS USING SSH AND IS GENERATING SSH MESSAGES

[Troy Baer]

OSC's mpiexec doesn't use ssh at all.

The new MPICH-2 distributions also have a tool called mpiexec that
does almost exactly the same thing as their old mpirun script.  Are you
sure you're not getting that instead?  Do a "which mpiexec" and make sure
you're getting the one you compiled and not something that came with
MPICH.

On Mon, 8 Sep 2003, Francois Courteille wrote:
> mpiexec looks a nice tool.
> 
> I have ported it (release 0.74)to one of our small LINUX  clusters.
> 
> I have a question regarding its usage.
> 
> Trying to run a small test i'm getting a lot of ssh messages, like below :
> 
> mpiexec -n 1 /tmp/test_fc
> generating ssh file /tmp/.ssh/id_dsa ...
> Generating public/private dsa key pair.
> open /tmp/.ssh/id_dsa failed: No such file or directory.
> Saving the key failed: /tmp/.ssh/id_dsa.
> generating ssh file /tmp/.ssh/identity ...
> Generating public/private rsa1 key pair.
> open /tmp/.ssh/identity failed: No such file or directory.
> Saving the key failed: /tmp/.ssh/identity.
> generating ssh file /tmp/.ssh/id_rsa ...
> Generating public/private rsa key pair.
> open /tmp/.ssh/id_rsa failed: No such file or directory.
> Saving the key failed: /tmp/.ssh/id_rsa.
> cat: /tmp/.ssh/id_dsa.pub: No such file or directory
> touch /tmp/.ssh/authorized_keys2
> touch: creating `/tmp/.ssh/authorized_keys2': No such file or directory
> chmod 700 /tmp/.ssh/authorized_keys2
> chmod: failed to get attributes of `/tmp/.ssh/authorized_keys2': No such file or
>  directory
> grep: /tmp/.ssh/authorized_keys2: No such file or directory
> adding id to ssh file /tmp/.ssh/authorized_keys2
> /tmp/.ssh/authorized_keys2: No such file or directory.
> 
> What is the fix to avoid those messages ?

	--Troy
-- 
Troy Baer                       email:  troy at osc.edu
Science & Technology Support    phone:  614-292-9701
Ohio Supercomputer Center       web:  http://oscinfo.osc.edu