Hi Rayson,<div><br></div><div>Just to report that Iīve changed the NODE_IMAGE_ID to ami-12b6477b and everything ran fine.</div><div>Little concern on plugin MPICH2 that is mandatory in our project. Got some errors when the cluster was started but at end said that itīs OK.. Letīs test it now.</div>
<div><br></div><div>We need to use CentOS machines due some libraries compatibility of our model. StarCluster is short of CentOS non-HVM machines. Thereīs only 2 "official" CentOS AMI. It should be interesting to expand the library or to have some recommended non-Ubuntu StarCluster AMIs.</div>
<div><br></div><div>All the best,</div><div><br>Sergio</div><div><br><br><div class="gmail_quote">On Tue, Jun 5, 2012 at 6:05 PM, Rayson Ho <span dir="ltr"><<a href="mailto:raysonlogin@gmail.com" target="_blank">raysonlogin@gmail.com</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">On Tue, Jun 5, 2012 at 4:57 PM, Sergio Mafra <<a href="mailto:sergiohmafra@gmail.com">sergiohmafra@gmail.com</a>> wrote:<br>
> Iīm sure that ami-7ea24a17 is not listed in the official AMIs. I thought<br>
> that we can use anyone... (newbie!!!).<br>
<br>
</div>Ah, that's why it refused to launch a cluster!<br>
<br>
The StarCluster code (the python ones) is designed to provision a<br>
StarCluster AMI, which has OGS/Grid Engine, MPI libraries, SSH, etc. A<br>
vanilla AMI or an Amazon stock AMI does not necessary have all the<br>
components needed.<br>
<br>
You may want to try to provision a small t1.micro clusters first, as<br>
they are free if you are new to AWS or cheap (only $0.03 per instance<br>
hour) if you are not in the free tier. Play with starting & stopping<br>
StarClusters before going for the real cluster instances (the<br>
HVM-based ones) as they are more expensive.<br>
<div class="HOEnZb"><div class="h5"><br>
Rayson<br>
<br>
================================<br>
Open Grid Scheduler / Grid Engine<br>
<a href="http://gridscheduler.sourceforge.net/" target="_blank">http://gridscheduler.sourceforge.net/</a><br>
<br>
Scalable Grid Engine Support Program<br>
<a href="http://www.scalablelogic.com/" target="_blank">http://www.scalablelogic.com/</a><br>
<br>
<br>
> Well, Iīll do it again tomorrow, now using ami-12b6477b that is a CentOS HVM<br>
> Starcluster official one.<br>
><br>
> Best regards,<br>
><br>
> Sergio<br>
><br>
><br>
> On Tue, Jun 5, 2012 at 5:50 PM, Rayson Ho <<a href="mailto:raysonlogin@gmail.com">raysonlogin@gmail.com</a>> wrote:<br>
>><br>
>> Do you know when exactly did StarCluster print that message - was it<br>
>> due to ami-999d49f0 or ami-7ea24a17??<br>
>><br>
>> (StarCluster keeps a debug log in ~/.starcluster/logs/debug.log - in<br>
>> case you want to do more debugging yourself...)<br>
>><br>
>> I haven't looked into the "ami-7ea24a17" AMI myself, however, from the<br>
>> name & manifest I don't think it is an official StarCluster AMI.<br>
>> Justin usually adds "starcluster" in the Manifests of all the<br>
>> StarCluster AMIs.<br>
>><br>
>> Can you run starcluster listpublic to check if ami-7ea24a17 is a<br>
>> starcluster AMI in your region??<br>
>><br>
>><br>
>> <a href="http://web.mit.edu/star/cluster/docs/latest/overview.html#starcluster-machine-images-amis" target="_blank">http://web.mit.edu/star/cluster/docs/latest/overview.html#starcluster-machine-images-amis</a><br>
>><br>
>> Rayson<br>
>><br>
>> ================================<br>
>> Open Grid Scheduler / Grid Engine<br>
>> <a href="http://gridscheduler.sourceforge.net/" target="_blank">http://gridscheduler.sourceforge.net/</a><br>
>><br>
>> Scalable Grid Engine Support Program<br>
>> <a href="http://www.scalablelogic.com/" target="_blank">http://www.scalablelogic.com/</a><br>
>><br>
>><br>
>><br>
>> On Tue, Jun 5, 2012 at 4:26 PM, Sergio Mafra <<a href="mailto:sergiohmafra@gmail.com">sergiohmafra@gmail.com</a>><br>
>> wrote:<br>
>> > Hi Fellows,<br>
>> ><br>
>> > I started a StarCluster today for the first time and got this error<br>
>> > message<br>
>> > at the end of the start process - "ERROR - SGE is not installed on this<br>
>> > AMI"<br>
>> > Looking at some older posts, I noticed that this could caused from an<br>
>> > incorrect AMI.<br>
>> ><br>
>> > The controller node uses ami-999d49f0, thatīs an official one.<br>
>> > The Master and Compute Nodes uses ami-7ea24a17, thatīs a EC2 Amazon<br>
>> > CentOS<br>
>> > image HVM<br>
>> ><br>
>> > Any suggestions?<br>
>> ><br>
>> > All best,<br>
>> ><br>
>> > Sergio<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>
>><br>
>><br>
>> --<br>
>> ==================================================<br>
>> Open Grid Scheduler - The Official Open Source Grid Engine<br>
>> <a href="http://gridscheduler.sourceforge.net/" target="_blank">http://gridscheduler.sourceforge.net/</a><br>
><br>
><br>
<br>
<br>
<br>
--<br>
==================================================<br>
Open Grid Scheduler - The Official Open Source Grid Engine<br>
<a href="http://gridscheduler.sourceforge.net/" target="_blank">http://gridscheduler.sourceforge.net/</a><br>
</div></div></blockquote></div><br></div>