Re: Problem adding starcluster to existing image
This archive was generated by
That's because your AMI does not have Grid Engine (boot up a
StarCluster instance and look in /opt/sge6 ) and other StarCluster
What is the main reason to go with the stock Ubuntu image?
Open Grid Scheduler - The Official Open Source Grid Engine
On Tue, Feb 4, 2014 at 11:49 AM, James Bullard <scientificb_at_gmail.com> wrote:
> Hi, this question has got to be an easy one to answer, but I couldn't
> contrive the right search terms to find it. I am trying to launch a
> starcluster using an AMI which I already have. Briefly, I installed
> starcluster on my AMI (ami-323f5c02), I then launched the small cluster
> using the default starcluster without issue (using ami-765b3e1f for both
> both MASTER and NODE).
> Now, I changed the following two values in starcluster's configuration:
> NODE_IMAGE_ID = ami-323f5c02
> MASTER_IMAGE_ID = ami-323f5c02
> And try to launch the same cluster, and I get the following error:
>>>> Starting NFS server on master
> !!! ERROR - Error occured while running plugin
> !!! ERROR - remote command 'source /etc/profile && /etc/init.d/nfs
> !!! ERROR - start' failed with status 127:
> !!! ERROR - bash: /etc/init.d/nfs: No such file or directory
> Naturally, I installed NFS on the image and rolled a new one and tried
> again, but that didn't help. I'm guessing starcluster has a custom NFS
> Do I have to start with a starcluster image? If so, how do I absorb updates
> -- that would seem like a great deal of work. I couldn't find a page which
> said, "Starcluster needs the following packages: ..."
> I'm on a stock ubuntu 12.04 64x image.
> thanks much in advance, this is going to be an amazing time saver.
> StarCluster mailing list
Received on Tue Feb 04 2014 - 12:56:33 EST