Return-Path: X-Original-To: apmail-mesos-user-archive@www.apache.org Delivered-To: apmail-mesos-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8474210929 for ; Mon, 3 Nov 2014 04:54:31 +0000 (UTC) Received: (qmail 9794 invoked by uid 500); 3 Nov 2014 04:54:31 -0000 Delivered-To: apmail-mesos-user-archive@mesos.apache.org Received: (qmail 9742 invoked by uid 500); 3 Nov 2014 04:54:31 -0000 Mailing-List: contact user-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@mesos.apache.org Delivered-To: mailing list user@mesos.apache.org Received: (qmail 9715 invoked by uid 99); 3 Nov 2014 04:54:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Nov 2014 04:54:31 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,MIME_QP_LONG_LINE,NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.218.49] (HELO mail-oi0-f49.google.com) (209.85.218.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Nov 2014 04:54:05 +0000 Received: by mail-oi0-f49.google.com with SMTP id u20so8092669oif.22 for ; Sun, 02 Nov 2014 20:53:18 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:content-transfer-encoding :mime-version:subject:message-id:date:references:in-reply-to:to; bh=mtQNM87iU/ZcwOI0m9yNZB+dApdDfy+NB1bW5WRYORA=; b=Rh0Kv7+VTJBllMDNVA6JB763vYGNS+fv5tNxiDn2SK7lQ573qtqrvyEvwCGtKErghD KGQOL816DqyQlZVuoTk0OBRu6pJiieq5ScrPibTp5XY2Hiy+RVlaAKpHXXfaA6FrW+r1 QLwUyD9vmvJI21FYKGy3yd5MCUw1a2MowwdC/ioZbVxbcqFShpC34+JzDWyFiyKJz9QN s4MMU92rCpTjgSFmwUZberSHMpsUGNudwgu4cz5gQclvS8Ky23Tzo/rPtQB40asp34CW u0iIwccQOOFDKemGec5N5+TvDI3av0ZfNvGexFz/R7McshWR6VnV+kGCJoasdtIlJcLd V4pw== X-Gm-Message-State: ALoCoQlUsCrVyd8dynieRcI2IyIzJlhr+hTGyh6Aud34DocIg7hCJguRXb2gqvSQqPKQGacyyNnm X-Received: by 10.60.67.233 with SMTP id q9mr35119355oet.30.1414990398480; Sun, 02 Nov 2014 20:53:18 -0800 (PST) Received: from [10.48.197.167] ([173.209.212.205]) by mx.google.com with ESMTPSA id s67sm7464473oie.24.2014.11.02.20.53.17 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 02 Nov 2014 20:53:17 -0800 (PST) From: Ankur Chauhan Content-Type: multipart/alternative; boundary=Apple-Mail-1F003D9D-7E82-4E15-8CEC-2936B98771BE Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (1.0) Subject: Re: AWS - Master and Slave can't communicate Message-Id: Date: Sun, 2 Nov 2014 20:53:15 -0800 References: <1AFA6E89-7DCE-4AA1-8BFB-9BDF217F845E@malloc64.com> In-Reply-To: To: "user@mesos.apache.org" X-Mailer: iPhone Mail (12B411) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-1F003D9D-7E82-4E15-8CEC-2936B98771BE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable I think I know what your problem is. The master and slave need to communicat= e with each other I generally set up the security groups such that they can c= ommunicate freely. try setting up for the security group between the master= and slave to allow full access and once you get that working you can look a= t the open ports to set a more strict rule set.=20 Sent from my iPhone > On Nov 2, 2014, at 8:40 PM, Matt Ivankov wrote: >=20 > Thanks for your reply. >=20 > Yes. I didn't set the rules up and the guy who did it in vacation. I have c= reated a new security group and have written down the mesos, marathon, zooke= eper ports. >=20 >=20 > This is what I have written: >=20 > Type - Protocol - Port Range - Source > Custom TCP Rule - TCP - 5050 - 0.0.0.0/0 > Custom TCP Rule - TCP - 8080 - 0.0.0.0/0 > Custom TCP Rule - TCP - 2181 - 0.0.0.0/0 > Custom TCP Rule - TCP - 2888 - 0.0.0.0/0 > Custom TCP Rule - TCP - 3888 - 0.0.0.0/0 >=20 >=20 > I don't know if this is correct or I've missed to open some other port. >=20 >> On Mon, Nov 3, 2014 at 2:55 PM, Ankur Chauhan wrote:= >> Are you running VPC? If so, what are your routing /security group rules ?= >>=20 >> -- Ankur >>=20 >>> On 2 Nov 2014, at 19:27, Matt Ivankov wrote: >>>=20 >>> Hi, >>>=20 >>> I'm new to Mesos and Marathon and I'd like to install it on AWS. For sta= rt, I wanted to create 1 master and 1 slave (Mesos version 0.20.1). >>>=20 >>> I've followed the steps on these links numerous times: >>> - https://www.digitalocean.com/community/tutorials/how-to-configure-a-pr= oduction-ready-mesosphere-cluster-on-ubuntu-14-04 >>> - http://mesosphere.com/docs/getting-started/datacenter/install/ >>>=20 >>>=20 >>> However, master and slave can't communicate. I don't see the slave on ma= ster. >>>=20 >>> When I run mesos-execute --master=3D$MASTER --name=3D"cluster-test" --co= mmand=3D"sleep 5", this is the output: >>>=20 >>> New master detected at master@172.30.24.22:5050 >>> No credentials provided. Attempting to register without authenticati= on >>>=20 >>>=20 >>> and it just hangs. When I look at the logs (cat /var/log/mesos/mesos-sl= ave.WARNING), this is what I see: >>>=20 >>> Master disconnected! Waiting for a new master to be elected >>>=20 >>>=20 >>> When I type MASTER=3D$(mesos-resolve `cat /etc/mesos/zk`), I can actuall= y see that slave finds the master (zookeeper is running on the master with m= esos) >>>=20 >>> A new leading master (UPID=3Dmaster@172.30.24.22:5050) is detected >>>=20 >>>=20 >>> Clearly I'm missing something but I've run out of ideas. I'd appreciate i= t if someone could point out what I'm missing. >>>=20 >>>=20 >>> Thanks in advance, >=20 --Apple-Mail-1F003D9D-7E82-4E15-8CEC-2936B98771BE Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
I think I know what your problem is. T= he master and slave need to communicate with each other I generally set up t= he security groups such that they can communicate freely.  try setting u= p for the security group between the master and slave to allow full access a= nd once you get that working you can look at the open ports to set a more st= rict rule set. 

Sent from my iPhone

On Nov 2, 2014= , at 8:40 PM, Matt Ivankov <mat= t.ivankov@gmail.com> wrote:

Thanks for your reply.

Yes. I didn't set the rule= s up and the guy who did it in vacation. I have created a new security group= and have written down the mesos, marathon, zookeeper ports.


This= is what I have written:

Type - Protocol - Port Range - Source
Cus= tom TCP Rule - TCP - 5050 - 0.0.0.0/0
Cu= stom TCP Rule - TCP - 8080 - 0.0.0.0/0
C= ustom TCP Rule - TCP - 2181 - 0.0.0.0/0
= Custom TCP Rule - TCP - 2888 - 0.0.0.0/0Custom TCP Rule - TCP - 3888 - 0.0.0.0/0

I don't know if this is correct or I've missed to open some other p= ort.

On M= on, Nov 3, 2014 at 2:55 PM, Ankur Chauhan <ankur@malloc64.com> wrote:
Are you running VPC? If so, what are your routing /security group rules ?<= span class=3D"HOEnZb">

-- Ankur

On 2 Nov 2014, at 19:27, Matt Ivankov <matt.ivankov@gmail.com> wrote:
Hi,

I'm new to Mesos and Marathon and I'= d like to install it on AWS. For start, I wanted to create 1 master and 1 sl= ave (Mesos version 0.20.1).

I've followed the steps on these links nu= merous times:
- https://www.digitalocean.com/community/tutorials/how-to-con= figure-a-production-ready-mesosphere-cluster-on-ubuntu-14-04
- http://mesosphere.com/docs/getting-started/datacenter/install/<= br>

However, master and slave can't communicate. I don't see the slav= e on master.

When I run mesos-execute --master=3D$MASTER --name=3D"cl= uster-test" --command=3D"sleep 5", this is the output:

  &n= bsp; New master detected at master@172.30.24.22:5050
    No credent= ials provided. Attempting to register without authentication


and&= nbsp; it just hangs. When I look at the logs (cat /var/log/mesos/mesos-slave= .WARNING), this is what I see:

    Master disconnected= ! Waiting for a new master to be elected


When I type MASTER=3D$(m= esos-resolve `cat /etc/mesos/zk`), I can actually see that slave finds the m= aster (zookeeper is running on the master with mesos)

  &nb= sp; A new leading master (UPID=3Dmaster@172.30.24.22:5050) is detected


Cle= arly I'm missing something but I've run out of ideas. I'd appreciate it if s= omeone could point out what I'm missing.


Thanks in advance,


=
= --Apple-Mail-1F003D9D-7E82-4E15-8CEC-2936B98771BE--