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