Hi Tena
I am glad to see that it you're getting there!
I'm following this thread all the time,
but I can't really help on this one,
for lack of any direct experience with EC2.
It looks like now you've got the full scoop of advice from
Jeff (OpenMPI side), Barnet and Ashley (EC2 side), which is
Hi Ashley,
> If you do this I would appreciate the chance to proof-read it before you go
> public...
Absolutely! I am a firm believer in two-heads-are-better-than-
one concept.
Regards,
Tena
On 2/18/11 1:29 AM, "Ashley Pittman" wrote:
>
> On 18 Feb 2011, at 09:09, Tena Sakai wrote:
>> I h
On 18 Feb 2011, at 09:09, Tena Sakai wrote:
> I had created a security group "intra." I opened ssh port from 0 to
> 65535, and launched instances (I unleashed 2 at a time in a same
> geography zone) each belonging to the group intra. So, here, ssh
> is a security rule of a security group intra.
Hi Gus,
I am starting to see the light at the other end of the tunnel.
As I wrote in reply to Jeff, it was not a ssh problem. It was
a setting of user configurable firewall that Amazon calls
security group. I need to expand my small tests to wider
set, but I think I can do that. I will keep you
Hi Jeff,
I have chosen to call this thread "This must be ssh problem, but I
can't figure out what it is..." It turns out that's really wrong!
EC2 allows users to create what is called security group. A security
group is made of one or more security rules, which is basically a
port based firewal
Hi Jeff,
Thank you for your suggestions. I followed your steps verbatim.
Unfortunately, there is a bit of problem. Here's what I did:
[tsakai@vixen ec2]$ ssh -i $MYKEY
tsa...@ec2-184-73-62-72.compute-1.amazonaws.com
The authenticity of host 'ec2-184-73-62-72.compute-1.amazonaws.com
(184.73.
On Feb 16, 2011, at 6:17 PM, Tena Sakai wrote:
> For now, may I point out something I noticed out of the
> DEBUG3 Output last night?
>
> I found this line:
>
>> debug1: Sending command: orted --daemonize -mca ess env -mca
>> orte_ess_jobid 125566976 -mca orte_ess_vpid 1 -mca orte_ess_num_procs
Hi Gus,
Thank you for the explanation. Your analogy (ping without
pong) makes sense and somewhat it is congruent with what
goes in my mind.
Regards,
Tena
On 2/16/11 4:31 PM, "Gus Correa" wrote:
> Hi Tena
>
> Again, I think your EC2 session log with ssh debug3 level (below)
> should be looked
Hi Gus,
I am sorry for delay. I had a busy day and kept me from doing
what I wanted to do. Namely, to figure out the problem with
mpirun on ec2 instances.
What I did just now was to
1) run the mpirun with the same app.ac file as before (locally,
between dasher and vixen) with DEBUG3 se
Hi Tena
Again, I think your EC2 session log with ssh debug3 level (below)
should be looked at by somebody more knowledgeable in OpenMPI
and in ssh that me.
There must be some clue to what is going on there.
Ssh experts, Jeff, Ralph, please help!
Anyway ...
AFAIK, 'orted' in the first line you s
Hi Gus,
Thank you for your reply and suggestions.
I will follow up on these in a bit and will give you an
update. Looking at what vixen and/or dasher generates
from DEBUG3 would be interesting.
For now, may I point out something I noticed out of the
DEBUG3 Output last night?
I found this line:
Hi Tena
I hope somebody more knowledgeable in ssh
takes a look at the debug3 session log that you included.
I can't see if/where/why ssh is failing for you in EC2.
See other answers inline, please.
Tena Sakai wrote:
Hi Gus,
Thank you again for your reply.
A slight difference is that on vix
Hi Gus,
Thank you again for your reply.
> A slight difference is that on vixen and dashen you ran the
> MPI hostname tests as a regular user, not as root, right?
> Not sure if this will make much of a difference,
> but it may be worth trying to run it as a regular user in EC2 also.
> I general mo
Tena Sakai wrote:
Hi,
I am trying to reproduce what I was able to show last Friday on Amazon
EC2 instances, but I am having a problem. What I was able to show last
Friday as root was with this command:
mpirun –app app.ac
with app.ac being:
-H dns-entry-A –np 1 (linux command)
-H dns-entry
Hi,
I am trying to reproduce what I was able to show last Friday on Amazon
EC2 instances, but I am having a problem. What I was able to show last
Friday as root was with this command:
mpirun –app app.ac
with app.ac being:
-H dns-entry-A –np 1 (linux command)
-H dns-entry-A –np 1 (linux comm
15 matches
Mail list logo
