This archive was generated by
I used the Linux free AMI listed on
currently just trying the first one listed - 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
On Mon, Sep 15, 2014 at 11:02 AM, Rayson Ho <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.
> Open Grid Scheduler - The Official Open Source Grid Engine
> On Mon, Sep 15, 2014 at 12:52 PM, David Von Dollen <
> davidvondollen_at_gmail.com> wrote:
>> 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...
>> StarCluster mailing list
Received on Mon Sep 15 2014 - 14:32:55 EDT