More info on this.
I tried passing "starcluster createvolume" an -i flag with the ami-id for
the Starcluster 32-bit image and got the same result. BTW, the message that
login had failed came up very quickly, quicker than I would expect an
instance to spin up.
Then I tried passing the ami id for my own 64-bit image based on the
starcluster image, and apparently the createvolume command expects to run
with a 32-bit AMI:
volume.py:186 - ERROR - exception thrown: EC2ResponseError: 400 Bad Request
<?xml version="1.0" encoding="UTF-8"?>
<Response><Errors><Error><Code>InvalidParameterValue</Code><Message>The
requested instance type's architecture (i386) does not match the
architecture in the manifest for ami-6a51a503
(x86_64)</Message></Error></Errors><RequestID>ce2a77a3-866d-4213-9b34-57266f99826a</RequestID></Response>
cli.py:566 - ERROR - failed to create new volume
Also, when I do not specify an AMI id, and I then type:
starcluster stop volumecreator
I see this:
StarCluster - (
http://web.mit.edu/starcluster)
Software Tools for Academics and Researchers (STAR)
Please submit bug reports to starcluster_at_mit.edu
Shutdown cluster volumecreator (y/n)? y
>>> Shutting down i-de04a5b3
>>> Shutting down i-0209a86f
>>> Shutting down i-f60eaf9b
>>> Removing cluster security group _at_sc-volumecreator
Why are three instances required just to create a volume?
Thanks
Dan
On Wed, Oct 27, 2010 at 12:51 PM, Dan Tenenbaum <dtenenba_at_fhcrc.org> wrote:
> I didn't reply to the list:
>
>
>
> ---------- Forwarded message ----------
> From: Dan Tenenbaum <dtenenba_at_fhcrc.org>
> Date: Wed, Oct 27, 2010 at 12:40 PM
> Subject: Re: [StarCluster] StarCluster not mounting EBS volume correctly
> To: Austin Godber <godber_at_uberhip.com>
>
>
>
>
> On Wed, Oct 27, 2010 at 12:36 PM, Austin Godber <godber_at_uberhip.com>wrote:
>
>> Hi Dan,
>> There is a command that will create volumes for you:
>> starcluster createvolume 30 us-east-1b
>>
>> Have you tried that? Starcluster expects a partition, thats probably why
>> its failing. I'd use the command unless I had some specific reason I
>> couldn't. I was unaware of it for about 3 months though :)
>>
>> Austin
>>
>>
>>
> Thanks for the tip, but that doesn't seem to work either, I get this (and
> the output keeps repeating):
>
> starcluster createvolume 30 us-east-1d
> StarCluster - (http://web.mit.edu/starcluster)
> Software Tools for Academics and Researchers (STAR)
> Please submit bug reports to starcluster_at_mit.edu
>
> >>> Using keypair bioc-keypair
> >>> Requesting host instance in zone us-east-1d to attach volume to...
> >>> Creating security group _at_sc-volumecreator...
> >>> No instance in group _at_sc-volumecreator for zone us-east-1d, launching
> one now.
> >>> Waiting for instance i-de04a5b3 to come up...
> |ssh.py:77 - WARNING - specified key does not end in either rsa or dsa,
> trying both
> >>> Using private key /Users/dtenenba/.ec2/bioc-keypair.pem (rsa)
> failed to authenticate to host root as user
> /ssh.py:77 - WARNING - specified key does not end in either rsa or dsa,
> trying both
> >>> Using private key /Users/dtenenba/.ec2/bioc-keypair.pem (rsa)
> failed to authenticate to host root as user
> /ssh.py:77 - WARNING - specified key does not end in either rsa or dsa,
> trying both
> >>> Using private key /Users/dtenenba/.ec2/bioc-keypair.pem (rsa)
> -failed to authenticate to host root as user
> -ssh.py:77 - WARNING - specified key does not end in either rsa or dsa,
> trying both
> >>> Using private key /Users/dtenenba/.ec2/bioc-keypair.pem (rsa)
> \failed to authenticate to host root as user
> \
>
> I am able to start clusters without attached volumes, so I don't think
> there's a problem with my key (other than the fact that its name doesn't end
> in rsa or dsa).
>
> Dan
>
>
>
> _______________________________________________
> StarCluster mailing list
> StarCluster_at_mit.edu
> http://mailman.mit.edu/mailman/listinfo/starcluster
>
>
Received on Wed Oct 27 2010 - 16:01:00 EDT