More info on this.<div>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.</div>
<div><br></div><div>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:</div><div><br></div><div><div>volume.py:186 - ERROR - exception thrown: EC2ResponseError: 400 Bad Request</div>
<div><?xml version="1.0" encoding="UTF-8"?></div><div><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></div>
<div>cli.py:566 - ERROR - failed to create new volume</div><div><br></div><div>Also, when I do not specify an AMI id, and I then type:<br>starcluster stop volumecreator</div><div><br></div><div>I see this:</div><div><div>
StarCluster - (<a href="http://web.mit.edu/starcluster">http://web.mit.edu/starcluster</a>)</div><div>Software Tools for Academics and Researchers (STAR)</div><div>Please submit bug reports to <a href="mailto:starcluster@mit.edu">starcluster@mit.edu</a></div>
<div><br></div><div>Shutdown cluster volumecreator (y/n)? y</div><div>>>> Shutting down i-de04a5b3</div><div>>>> Shutting down i-0209a86f</div><div>>>> Shutting down i-f60eaf9b</div><div>>>> Removing cluster security group @sc-volumecreator</div>
</div><div><br></div><div>Why are three instances required just to create a volume?</div><div>Thanks</div><div>Dan</div><div><br></div><br><div class="gmail_quote">On Wed, Oct 27, 2010 at 12:51 PM, Dan Tenenbaum <span dir="ltr"><<a href="mailto:dtenenba@fhcrc.org">dtenenba@fhcrc.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">I didn't reply to the list:<div><br></div></div><div><br><br><div class="gmail_quote"><div class="im">
---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Dan Tenenbaum</b> <span dir="ltr"><<a href="mailto:dtenenba@fhcrc.org" target="_blank">dtenenba@fhcrc.org</a>></span><br>
Date: Wed, Oct 27, 2010 at 12:40 PM<br>Subject: Re: [StarCluster] StarCluster not mounting EBS volume correctly<br></div><div><div></div><div class="h5">To: Austin Godber <<a href="mailto:godber@uberhip.com" target="_blank">godber@uberhip.com</a>><br>
<br><br><br><br><div class="gmail_quote">
<div>On Wed, Oct 27, 2010 at 12:36 PM, Austin Godber <span dir="ltr"><<a href="mailto:godber@uberhip.com" target="_blank">godber@uberhip.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#ffffff">
Hi Dan,<br>
There is a command that will create volumes for you:<br>
starcluster createvolume 30 us-east-1b<br>
<br>
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 :)<br>
<br>
Austin<div><div></div><div><br>
<br></div></div></div></blockquote><div><br></div></div><div>Thanks for the tip, but that doesn't seem to work either, I get this (and the output keeps repeating):</div><div><br></div><div><div> starcluster createvolume 30 us-east-1d</div>
<div>StarCluster - (<a href="http://web.mit.edu/starcluster" target="_blank">http://web.mit.edu/starcluster</a>)</div><div>Software Tools for Academics and Researchers (STAR)</div><div>Please submit bug reports to <a href="mailto:starcluster@mit.edu" target="_blank">starcluster@mit.edu</a></div>
<div><br></div><div>>>> Using keypair bioc-keypair</div><div>>>> Requesting host instance in zone us-east-1d to attach volume to...</div><div>>>> Creating security group @sc-volumecreator...</div>
<div>>>> No instance in group @sc-volumecreator for zone us-east-1d, launching one now.</div><div>>>> Waiting for instance i-de04a5b3 to come up...</div><div><div>|ssh.py:77 - WARNING - specified key does not end in either rsa or dsa, trying both</div>
<div>>>> Using private key /Users/dtenenba/.ec2/bioc-keypair.pem (rsa)</div></div><div>failed to authenticate to host root as user </div><div>/ssh.py:77 - WARNING - specified key does not end in either rsa or dsa, trying both</div>
<div>
<div>>>> Using private key /Users/dtenenba/.ec2/bioc-keypair.pem (rsa)</div></div><div>failed to authenticate to host root as user </div><div>/ssh.py:77 - WARNING - specified key does not end in either rsa or dsa, trying both</div>
<div>
<div>>>> Using private key /Users/dtenenba/.ec2/bioc-keypair.pem (rsa)</div></div><div>-failed to authenticate to host root as user </div><div>-ssh.py:77 - WARNING - specified key does not end in either rsa or dsa, trying both</div>
<div>
<div>>>> Using private key /Users/dtenenba/.ec2/bioc-keypair.pem (rsa)</div></div><div>\failed to authenticate to host root as user </div><div>\</div></div><div><br></div><div>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).</div>
<div><br></div><div>Dan</div><div><br></div></div>
</div></div></div><br></div>
<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></blockquote></div><br></div>