[mpich-discuss] MPICH2 for ARM

[Pavan Balaji]

Which Linux variant are you using? For Ubuntu/Debian, do:

% sudo apt-get install openssh-server openssh-client

For Fedora/Redhat, you'll need to do sudo yum install some-ssh-package. 
Try google.

  -- Pavan

On 11/22/2011 08:50 AM, Harald Schuster wrote:
> Hi
>
> I know taht this is not a mpich2 question but i dont know where to
> search for help. After a lot of unsuccessfully test ssh is not running
> yet. I installed the openssh packet by the make menuconfig command in
> the buildroot. Then I create a new root file system with the buildroot.
> That works and the linux now knows the ssh command. When i go to
> /etc/init.d I found S50sshd and I executed ./S50sshd restart. After
> restarting he said ok but it doesn't works. When I start ssh
> root at localhost i got an connection refused message. Is there a special
> configuration necessary?! It is all running on a arm controller.
>
> Best regards
> Harald
>
>
> On 18.11.2011 17:34, Pavan Balaji wrote:
>> Hello,
>>
>> On 11/18/2011 07:10 AM, Harald Schuster wrote:
>>> So with the MPICH2 version 1.3.2 it works fine when I start the
>>> applications with -launcher fork. This is a big step forward and my next
>>> step is do start to controllers and let them communicate together. Until
>>> now it is possible to ping one controller from the other but i can not
>>> start Mpi via ssh. I installed openssh with make menuconfig in the
>>> buildroot butI always get the error “connection refused”. Do I need to
>>> include ssh in the kernel? I think it is a problem with the
>>> configuration of ssh but i have to lock. If you have any advice please
>>> write back. Thanks
>>
>> This is not really an MPICH2 related question, but I'll answer it
>> anyway. In the future, you might want to try other mailing lists that
>> help you with networking setup on your cluster.
>>
>> 1. I believe you need to install both openssh-server and
>> openssh-client. The openssh-client part gives you the "ssh" executable
>> and the server part gives you the "sshd" daemon that runs on all the
>> nodes. Once you install it, it should automatically start up; no extra
>> settings should be required. For example, on Ubuntu/Debian you can do
>> "sudo apt-get install openssh-server openssh-client".
>>
>> 2. You should setup password-less ssh. You should be able to google
>> for "ssh passwordless" and find a zillion links to tutorials on how to
>> do this.
>>
>> 3. Make sure your firewall is disabled. On Ubuntu/Debian, you can
>> disable it with "sudo ufw disable". On other platforms, google is your
>> friend.
>>
>> Once your ssh is setup fine, MPICH2 should automatically be able to
>> use it to launch processes remotely.
>>
>>   -- Pavan
>
> _______________________________________________
> mpich-discuss mailing list     mpich-discuss at mcs.anl.gov
> To manage subscription options or unsubscribe:
> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss

-- 
Pavan Balaji
http://www.mcs.anl.gov/~balaji