[StarCluster] SSH on all nodes

Vasisht Reddy T. vasishtreddy at gmail.com
Mon Sep 15 14:38:46 EDT 2014


The regular AMI’s are not configured to run StarCluster. Have you tried one of the StarCluster AMIs. You can get a list of public images by running ‘starcluster list public’  

Vasisht


On Monday, September 15, 2014 at 2:32 PM, David Von Dollen wrote:

> Hello Rayson,
>  
> I used the Linux free AMI listed on  
>  
> www.aws.amazon.com/amazon-linux-ami/ (http://www.aws.amazon.com/amazon-linux-ami/)
>  
> currently just trying the first one listed - ami-7c807d14 (https://console.aws.amazon.com/ec2/v2/home?region=us-east-1#LaunchInstanceWizard:ami=ami-7c807d14)
>  
> Tried most of the EBS backed variants -  
>  
> If I get a "Permission denied - public key" when ssh'ing  and the node/master in the console appears to be fine- what would be the next steps?
>  
> I terminated the cluster, and I tried creating a new keypair and key and updated keys in the console the config file- restarted the cluster, the instances started up and terminated fine from starcluster but still was not able to ssh into the master or node using the new key.
>  
> Thanks in advance for your advisement
>  
> David
>  
>  
> Thanks,
>  
> On Mon, Sep 15, 2014 at 11:02 AM, Rayson Ho <raysonlogin at gmail.com (mailto:raysonlogin at gmail.com)> wrote:
> > Sounds like starcluster is not able to SSH into the nodes. How did you create the AMI?
> >  
> > As a quick test, use the SSH key that you specified in the starcluster config to ssh into one of the instances - note that you can get the instance names & IP from the AWS web management console.
> >  
> > Rayson
> >  
> > ==================================================
> > Open Grid Scheduler - The Official Open Source Grid Engine
> > http://gridscheduler.sourceforge.net/
> > http://gridscheduler.sourceforge.net/GridEngine/GridEngineCloud.html  
> > On Mon, Sep 15, 2014 at 12:52 PM, David Von Dollen <davidvondollen at gmail.com (mailto:davidvondollen at gmail.com)> wrote:
> > > Hello  
> > >  
> > > After changing the ami- (made a note to match the region and EBS backed instance) I notice that on starcluster start it seems to hang on the "Waiting for SSH to come up on all nodes..."step-
> > >  
> > > just wondering if this is this a known issue? any reasons for why this could be happening? just wondering if I am doing something wrong...
> > >  
> > > Thanks  
> > > _______________________________________________
> > > StarCluster mailing list
> > > StarCluster at mit.edu (mailto:StarCluster at mit.edu)
> > > http://mailman.mit.edu/mailman/listinfo/starcluster
> > >  
> >  
>  
> _______________________________________________
> StarCluster mailing list
> StarCluster at mit.edu (mailto:StarCluster at mit.edu)
> http://mailman.mit.edu/mailman/listinfo/starcluster
>  
>  


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/starcluster/attachments/20140915/7d7bb797/attachment.htm


More information about the StarCluster mailing list