Hui...
I had no problem getting it to work for me when I tried to follow the
instructions.
I'm not sure if it matters but I removed the dashes "-" from my AWS User ID
number ?
For the keypair I just used one of my existing AWS keypair's.
Brian
= = = = = = = = = = =
Today's Topics:
1. starcluster start error (Hui Zhao)
2. Re: starcluster start error (Justin Riley)
3. Re: starcluster start error (Hui Zhao)
----------------------------------------------------------------------
Message: 1
Date: Thu, 4 Nov 2010 13:04:56 -0400
From: "Hui Zhao" <zhaoh_at_cbio.mskcc.org>
Subject: [StarCluster] starcluster start error
To: starcluster_at_mit.edu
Message-ID: <4C6285D8-8C04-4A04-9F40-C25CF82A4EFD_at_cbio.mskcc.org>
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
Hi,
What is the minimal parameters needed for the starcluster config file?
I only edited the uncommented ones in the template config before the
section of "configure EBS Volumes". I got error shown as below. I
copied AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEY from my aws account
including the 12 digits AWS_USER_ID. Why does it complain it's
invalid? For the keypair, that is the one with .pem extension, right?
I cannot fine the file cluster.py either. Please advise.
Thanks,
Julia
-bash-3.2$ starcluster start smallcluster
StarCluster - (
http://web.mit.edu/starcluster)
Software Tools for Academics and Researchers (STAR)
Please submit bug reports to starcluster_at_mit.edu
>>> Using default cluster template: smallcluster
>>> Validating cluster template settings...
cluster.py:766 - ERROR - Invalid AWS_ACCESS_KEY_ID/
AWS_SECRET_ACCESS_KEY combination.
cli.py:243 - ERROR - settings for cluster template "smallcluster" are
not valid
------------------------------
Message: 2
Date: Thu, 04 Nov 2010 13:19:15 -0400
From: Justin Riley <jtriley_at_MIT.EDU>
Subject: Re: [StarCluster] starcluster start error
To: starcluster_at_MIT.EDU
Message-ID: <4CD2EB13.60607_at_mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 11/4/10 1:04 PM, Hui Zhao wrote:
> Why does it complain it's
> invalid?
Hmmm, do yo have quotes around the settings (ie AWS_ACCESS_KEY="myid") ?
If so, remove them. Also, are you sure you haven't mixed up your access
key and secret access key in the config? Perhaps you need to swap them.
> For the keypair, that is the one with .pem extension, right?
Well, maybe. Do you recall explicitly creating a new keypair? You do not
automatically get a keypair when you first create an AWS/EC2 account.
You must explicitly create a new keypair either using the AWS Management
Console or running the EC2 command line tool "ec2-add-keypair". The EC2
Getting Started Guide runs you through this. If you don't recall doing
this at some point then the *.pem file(s) you are referring to are
likely your EC2 certificate and private certificate files for your AWS
account which are not the same.
I would recommend logging into the AWS Management Console and checking
to see if you have any keypairs listed. I believe you can download your
existing keys (if any) from the management console as well. If you don't
have any keypairs, it's easy to create a new one and the management
console will prompt you to download the key file. You should then use
the location you download the keypair file to as key_location in a [key]
section. Does that make sense?
~Justin
------------------------------
Message: 3
Date: Thu, 4 Nov 2010 14:06:00 -0400
From: "Hui Zhao" <zhaoh_at_cbio.mskcc.org>
Subject: Re: [StarCluster] starcluster start error
To: "Justin Riley" <jtriley_at_mit.edu>
Cc: starcluster_at_mit.edu
Message-ID: <53475FBA-93F9-4230-8457-C9BE840F9C5E_at_cbio.mskcc.org>
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
Justin,
Thanks for the quick response. It's my mistake - I copied the
AWS_SECRET_ACCESS_KEY from my aws account, somehow the last digit was
modified. Once it's corrected, I was able to start the default
smallcluster. This mailing list is very helpful and I feel more
courage to explore it further.
Thanks again,
Julia
On Nov 4, 2010, at 1:19 PM, Justin Riley wrote:
> On 11/4/10 1:04 PM, Hui Zhao wrote:
>> Why does it complain it's
>> invalid?
> Hmmm, do yo have quotes around the settings (ie
> AWS_ACCESS_KEY="myid") ?
> If so, remove them. Also, are you sure you haven't mixed up your
> access
> key and secret access key in the config? Perhaps you need to swap
> them.
>> For the keypair, that is the one with .pem extension, right?
> Well, maybe. Do you recall explicitly creating a new keypair? You do
> not
> automatically get a keypair when you first create an AWS/EC2 account.
> You must explicitly create a new keypair either using the AWS
> Management
> Console or running the EC2 command line tool "ec2-add-keypair". The
> EC2
> Getting Started Guide runs you through this. If you don't recall doing
> this at some point then the *.pem file(s) you are referring to are
> likely your EC2 certificate and private certificate files for your AWS
> account which are not the same.
>
> I would recommend logging into the AWS Management Console and checking
> to see if you have any keypairs listed. I believe you can download
> your
> existing keys (if any) from the management console as well. If you
> don't
> have any keypairs, it's easy to create a new one and the management
> console will prompt you to download the key file. You should then use
> the location you download the keypair file to as key_location in a
> [key]
> section. Does that make sense?
>
> ~Justin
> _______________________________________________
> StarCluster mailing list
> StarCluster_at_mit.edu
> http://mailman.mit.edu/mailman/listinfo/starcluster
------------------------------
_______________________________________________
StarCluster mailing list
StarCluster_at_mit.edu
http://mailman.mit.edu/mailman/listinfo/starcluster
End of StarCluster Digest, Vol 15, Issue 2
******************************************
Received on Fri Nov 05 2010 - 14:33:05 EDT