My initial guess is that it's a security group setting and/or that you
are lacking a public IP associated with the setup. You can have
Starcluster running on a private subnet, but if you do that you need to
have your NAT setup properly with connections to your Starcluster
cluster. If you are running on a no longer supported version of the OS
like Phil suggested that also is going to cause an issue and you won't
be able to install the packages you need. If this is the case use the
AMI for Ubuntu 12.04 as he suggested. If you need 14.04, upgrade the
12.04 to 14.04 and/or you can take a whirl at using the directions I
sent yesterday with getting Starcluster to run on Ubuntu 14.04 LTS as
provided by Ubuntu.com.
If it isn't the OS, the solution can get complicated so a quick fix
might be just to save an AMI of master node you have right now. Launch
that AMI as a new EC2 instance under the default VPC that AWS provides
(this allows you to connect to the internet and provides public IP).
Login to that new EC2 instance and add all the software you need for
your Starcluster cluster ( including R) and update the OS with the
latest security patches. Stop the instance and save it as an AMI, use
this new AMI (that includes R and OS security patches) to create your
Starcluster cluster as you had originally. Problem solved you have R
and software you need on a running Starcluster cluster.
On 2/20/15 12:53 PM, Philip Montgomery wrote:
> I don't recall seeing any network errors, but I do regularly install R
> on top of starcluster AMIs. I have gotten errors trying to update
> packages, I'm guessing because the last ubuntu release that there's
> starcluster AMIs (13.04) for is no longer supported by ubuntu. So, I
> use the AMI for ubuntu 12.04 as my starting point.
> Attached is a script that I run which installs R and the various
> packages that I use. I then image the instance to a new AMI so that I
> don't need to repeat the process ever time a node comes online.
> Not entirely clear if the problem you're getting is one I've hit, but
> sending along my script in case it happens to help.
> On Fri, Feb 20, 2015 at 12:34 PM, <starcluster-request_at_mit.edu
> <mailto:starcluster-request_at_mit.edu>> wrote:
> Send StarCluster mailing list submissions to
> starcluster_at_mit.edu <mailto:starcluster_at_mit.edu>
> To subscribe or unsubscribe via the World Wide Web, visit
> or, via email, send a message with subject or body 'help' to
> starcluster-request_at_mit.edu <mailto:starcluster-request_at_mit.edu>
> You can reach the person managing the list at
> starcluster-owner_at_mit.edu <mailto:starcluster-owner_at_mit.edu>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of StarCluster digest..."
> Today's Topics:
> 1. cannot install on master node (Vas Ku)
> Message: 1
> Date: Fri, 20 Feb 2015 16:53:51 +0000
> From: Vas Ku <vaskum.tech_at_gmail.com <mailto:vaskum.tech_at_gmail.com>>
> Subject: [StarCluster] cannot install on master node
> To: starcluster_at_mit.edu <mailto:starcluster_at_mit.edu>
> <CANXm8A3qUwmsjO7RVDMKgwiC588T7BhAR=d=vOP_ABVjLyrRQg_at_mail.gmail.com <mailto:vOP_ABVjLyrRQg_at_mail.gmail.com>>
> Content-Type: text/plain; charset="utf-8"
> Apologies for this rather novice question. I have finally been
> able to get
> star cluster installed and running after firefighting with
> different AMI's
> and thing. But now I am stuck with this issue where I need to
> install R and
> when i do apt-get, the networks seems to be dead. Not even ping
> works (just
> hangs any ip and dies with 'failed connection timeout' ) . Must be
> something obvious I haven't or have done with my config setting.
> Could you
> please let me know what diagnostics could I perform?
> -------------- next part --------------
> An HTML attachment was scrubbed...
> StarCluster mailing list
> StarCluster_at_mit.edu <mailto:StarCluster_at_mit.edu>
> End of StarCluster Digest, Vol 66, Issue 7
> StarCluster mailing list
Received on Fri Feb 20 2015 - 13:08:34 EST