Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [OMPI users] Accessing OpenMPI processes over Internet using ssh
From: Ralph Castain (rhc_at_[hidden])
Date: 2011-11-30 16:14:41


As I said, please do a quick search on the "user" mailing list. There are numerous discussions there about how to do this. Here is another one that dealt with getting thru the Amazon firewall:

http://www.open-mpi.org/community/lists/users/2011/02/15646.php

On Nov 30, 2011, at 1:58 PM, Jaison Paul wrote:

> Ralph Castain <rhc <at> open-mpi.org> writes:
>
>>
>> This has come up before - I would suggest doing a quick search of "ec2" on our
> user list. Here is one solution:
>> On Jun 14, 2011, at 10:50 AM, Barnet Wagman wrote:I've put together a simple
> system for running OMPI on EC2 (Amazon's cloud computing service). If you're
> interested, see
>>
>>
>>
>> http://norbl.com/ppe-ompi.html
>>
>
> I have tried little bit more:
>
> I have set the MCA parameters as follows:
> mpirun -np 1 --mca btl tcp,self --mca btl_tcp_if_exclude lo,eth0 -hostfile
> hostinfo nbs-client -bynode
>
> But still failed and got the following error:
>
> Permission denied (publickey).
> --------------------------------------------------------------------------
> A daemon (pid 24744) died unexpectedly with status 255 while attempting
> to launch so we are aborting.
>
> There may be more information reported by the environment (see above).
>
> This may be because the daemon was unable to find all the needed shared
> libraries on the remote node. You may set your LD_LIBRARY_PATH to have the
> location of the shared libraries on the remote nodes and this will
> automatically be forwarded to the remote nodes.
> --------------------------------------------------------------------------
> mpirun: clean termination accomplished
>
> I dont understand the "Permission denied (publickey)" error. I access the EC2
> instance using password-less ssh as follows:
>
> ssh ubuntu <at> ec2-67-202-**-***.compute-1.amazonaws.com
>
> So, what went wrong?
>
> hostinfo file is:
>
> [jmulerik <at> jaison Client]$ cat hostinfo
> localhost
> ubuntu <at> ec2-67-202-48-118.compute-1.amazonaws.com
>
> Jaison
>
>
> _______________________________________________
> users mailing list
> users_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/users