MPIEXEC IS USING SSH AND IS GENERATING SSH MESSAGES

[Francois Courteille]

Hi Troy,

thanks for your answer.

I checked the mpiexec i was using : it was OSC's mpiexec.
It looks like the problem i encountered came from the interaction beetween
PBS (configuration issue ?)
with ssh.
OSC's mpiexec is working perfectly on another cluster .
(the 2 clusters were supposed to be configured the same way).

Furthermore i have 2 other questions , one regarding openpbs the other
regarding mpich with emp.
(the url www.osc.edu/~pw/emp  is not working for me)
Has EMP work been thrown away ?

Regarding Openpbs the question is the following one :
how to create a queue for sequential jobs only ?
(limiting the usage to one processor at a time per job)
This is because we are using smp nodes.
The problem is to prohibit users to submit parallel jobs in a sequential
queue and
use several cpus.
(resources_max.nodect=1 still grants access to the number of processors a
node have)

Whom could i ask ?

Thank you for you help,

with best regards

Francois Courteille






----- Original Message ----- 
From: "Troy Baer" <troy at osc.edu>
To: "Francois Courteille" <francois at hpce.nec.com>
Cc: <mpiexec at osc.edu>
Sent: Monday, September 08, 2003 4:45 PM
Subject: Re: MPIEXEC IS USING SSH AND IS GENERATING SSH MESSAGES


> 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
>
>
>