[prev in list] [next in list] [prev in thread] [next in thread]
List: mesos-user
Subject: Re: Troubles with setting up master/slave
From: Adam Bordelon <adam () mesosphere ! io>
Date: 2015-02-22 9:09:32
Message-ID: CAK8jAgMCD3y2CPGD01SrSSw-za=t0aEMdTvD+WL-wJjfj371pQ () mail ! gmail ! com
[Download RAW message or body]
You could also try setting the LIBPROCESS_IP environment variable, which
should override the IP that the scheduler reports for its PID.
On Thu, Feb 12, 2015 at 1:01 PM, Nils-Helge Garli Hegvik <nilsga@gmail.com>
wrote:
> Hi!
>
> I'm following [1] to set up a master/slave configuration with Vagrant.
> I have set up networking and hostnames so the master and slave can
> resolve each other. I can get to the ui, and see that a framework
> (marathon) and a slave is registered. I can also successfully verify
> the installation by issuing a task with
>
> mesos-execute --master=$MASTER --name="cluster-test" --command="sleep 5"
>
> on the master. However, when launching the same task from the slave
> vm, it fails. It seems to go into an error loop, where the master
> keeps logging
>
> ---
>
> I0212 20:28:36.912345 9244 master.cpp:3843] Sending 1 offers to
> framework 20150212-200948-46704832-5050-9196-0000 (marathon) at
> scheduler-9cf62fe9-c24d-451e-821d-f3e9aefa8d2c@127.0.1.1:40413
>
> I0212 20:28:36.984591 9242 master.cpp:2344] Processing reply for
> offers: [ 20150212-200948-46704832-5050-9196-O175 ] on slave
> 20150212-200948-46704832-5050-9196-S0 at slave(1)@192.168.200.3:5051
> (192.168.200.3) for framework 20150212-200948-46704832-5050-9196-0000
> (marathon) at
> scheduler-9cf62fe9-c24d-451e-821d-f3e9aefa8d2c@127.0.1.1:40413
>
> I0212 20:28:36.985373 9242 hierarchical_allocator_process.hpp:563]
> Recovered cpus(*):2; mem(*):496; disk(*):32297; ports(*):[31000-32000]
> (total allocatable: cpus(*):2; mem(*):496; disk(*):32297;
> ports(*):[31000-32000]) on slave 20150212-200948-46704832-5050-9196-S0
> from framework 20150212-200948-46704832-5050-9196-0000
>
> I0212 20:28:37.749330 9242 http.cpp:478] HTTP request for
> '/master/state.json'
>
> I0212 20:28:37.820500 9242 master.cpp:1383] Received registration
> request for framework '' at
> scheduler-f5510035-c6ea-4074-ad49-2b16d855b127@127.0.1.1:47664
>
> I0212 20:28:37.821678 9242 master.cpp:1447] Registering framework
> 20150212-200948-46704832-5050-9196-0059 () at
> scheduler-f5510035-c6ea-4074-ad49-2b16d855b127@127.0.1.1:47664
>
> I0212 20:28:37.822754 9238 hierarchical_allocator_process.hpp:329]
> Added framework 20150212-200948-46704832-5050-9196-0059
>
> I0212 20:28:37.823096 9244 master.cpp:789] Framework
> 20150212-200948-46704832-5050-9196-0059 () at
> scheduler-f5510035-c6ea-4074-ad49-2b16d855b127@127.0.1.1:47664
> disconnected
>
> I0212 20:28:37.824023 9244 master.cpp:1752] Disconnecting framework
> 20150212-200948-46704832-5050-9196-0059 () at
> scheduler-f5510035-c6ea-4074-ad49-2b16d855b127@127.0.1.1:47664
>
> I0212 20:28:37.824358 9244 master.cpp:1768] Deactivating framework
> 20150212-200948-46704832-5050-9196-0059 () at
> scheduler-f5510035-c6ea-4074-ad49-2b16d855b127@127.0.1.1:47664
>
> I0212 20:28:37.824725 9244 master.cpp:811] Giving framework
> 20150212-200948-46704832-5050-9196-0059 () at
> scheduler-f5510035-c6ea-4074-ad49-2b16d855b127@127.0.1.1:47664 0ns to
> failover
>
> W0212 20:28:37.825021 9244 master.cpp:3726] Master returning
> resources offered to framework 20150212-200948-46704832-5050-9196-0059
> because the framework has terminated or is inactive
>
> I0212 20:28:37.825500 9244 hierarchical_allocator_process.hpp:405]
> Deactivated framework 20150212-200948-46704832-5050-9196-0059
>
> ---
>
> I do notice that the ip of the scheduler reports as 127.0.1.1:47664,
> but I have set all of /etc/mesos-master/hostname, /etc/mesos-master/ip
> and /etc/marathon/conf/hostname to the private network of the vagrant
> vms.
>
>
> [1] - http://mesosphere.com/docs/getting-started/datacenter/install/
>
[Attachment #3 (text/html)]
<div dir="ltr">You could also try setting the LIBPROCESS_IP environment variable, \
which should override the IP that the scheduler reports for its PID.<br></div><div \
class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 12, 2015 at 1:01 PM, \
Nils-Helge Garli Hegvik <span dir="ltr"><<a href="mailto:nilsga@gmail.com" \
target="_blank">nilsga@gmail.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">Hi!<br> <br>
I'm following [1] to set up a master/slave configuration with Vagrant.<br>
I have set up networking and hostnames so the master and slave can<br>
resolve each other. I can get to the ui, and see that a framework<br>
(marathon) and a slave is registered. I can also successfully verify<br>
the installation by issuing a task with<br>
<br>
mesos-execute --master=$MASTER --name="cluster-test" --command="sleep \
5"<br> <br>
on the master. However, when launching the same task from the slave<br>
vm, it fails. It seems to go into an error loop, where the master<br>
keeps logging<br>
<br>
---<br>
<br>
I0212 20:28:36.<a href="tel:912345%20%209244" value="+19123459244">912345 9244</a> \
master.cpp:3843] Sending 1 offers to<br> framework \
20150212-200948-46704832-5050-9196-0000 (marathon) at<br> <a \
href="http://scheduler-9cf62fe9-c24d-451e-821d-f3e9aefa8d2c@127.0.1.1:40413" \
target="_blank">scheduler-9cf62fe9-c24d-451e-821d-f3e9aefa8d2c@127.0.1.1:40413</a><br>
<br>
I0212 20:28:36.<a href="tel:984591%20%209242" value="+19845919242">984591 9242</a> \
master.cpp:2344] Processing reply for<br>
offers: [ 20150212-200948-46704832-5050-9196-O175 ] on slave<br>
20150212-200948-46704832-5050-9196-S0 at slave(1)@<a href="http://192.168.200.3:5051" \
target="_blank">192.168.200.3:5051</a><br> (192.168.200.3) for framework \
20150212-200948-46704832-5050-9196-0000<br> (marathon) at <a \
href="http://scheduler-9cf62fe9-c24d-451e-821d-f3e9aefa8d2c@127.0.1.1:40413" \
target="_blank">scheduler-9cf62fe9-c24d-451e-821d-f3e9aefa8d2c@127.0.1.1:40413</a><br>
<br>
I0212 20:28:36.<a href="tel:985373%20%209242" value="+19853739242">985373 9242</a> \
hierarchical_allocator_process.hpp:563]<br> Recovered cpus(*):2; mem(*):496; \
disk(*):32297; ports(*):[31000-32000]<br> (total allocatable: cpus(*):2; mem(*):496; \
disk(*):32297;<br> ports(*):[31000-32000]) on slave \
20150212-200948-46704832-5050-9196-S0<br> from framework \
20150212-200948-46704832-5050-9196-0000<br> <br>
I0212 20:28:37.749330 9242 http.cpp:478] HTTP request for \
'/master/state.json'<br> <br>
I0212 20:28:37.820500 9242 master.cpp:1383] Received registration<br>
request for framework '' at<br>
<a href="http://scheduler-f5510035-c6ea-4074-ad49-2b16d855b127@127.0.1.1:47664" \
target="_blank">scheduler-f5510035-c6ea-4074-ad49-2b16d855b127@127.0.1.1:47664</a><br>
<br>
I0212 20:28:37.821678 9242 master.cpp:1447] Registering framework<br>
20150212-200948-46704832-5050-9196-0059 () at<br>
<a href="http://scheduler-f5510035-c6ea-4074-ad49-2b16d855b127@127.0.1.1:47664" \
target="_blank">scheduler-f5510035-c6ea-4074-ad49-2b16d855b127@127.0.1.1:47664</a><br>
<br>
I0212 20:28:37.822754 9238 hierarchical_allocator_process.hpp:329]<br>
Added framework 20150212-200948-46704832-5050-9196-0059<br>
<br>
I0212 20:28:37.823096 9244 master.cpp:789] Framework<br>
20150212-200948-46704832-5050-9196-0059 () at<br>
<a href="http://scheduler-f5510035-c6ea-4074-ad49-2b16d855b127@127.0.1.1:47664" \
target="_blank">scheduler-f5510035-c6ea-4074-ad49-2b16d855b127@127.0.1.1:47664</a><br>
disconnected<br>
<br>
I0212 20:28:37.824023 9244 master.cpp:1752] Disconnecting framework<br>
20150212-200948-46704832-5050-9196-0059 () at<br>
<a href="http://scheduler-f5510035-c6ea-4074-ad49-2b16d855b127@127.0.1.1:47664" \
target="_blank">scheduler-f5510035-c6ea-4074-ad49-2b16d855b127@127.0.1.1:47664</a><br>
<br>
I0212 20:28:37.824358 9244 master.cpp:1768] Deactivating framework<br>
20150212-200948-46704832-5050-9196-0059 () at<br>
<a href="http://scheduler-f5510035-c6ea-4074-ad49-2b16d855b127@127.0.1.1:47664" \
target="_blank">scheduler-f5510035-c6ea-4074-ad49-2b16d855b127@127.0.1.1:47664</a><br>
<br>
I0212 20:28:37.824725 9244 master.cpp:811] Giving framework<br>
20150212-200948-46704832-5050-9196-0059 () at<br>
<a href="http://scheduler-f5510035-c6ea-4074-ad49-2b16d855b127@127.0.1.1:47664" \
target="_blank">scheduler-f5510035-c6ea-4074-ad49-2b16d855b127@127.0.1.1:47664</a> \
0ns to<br> failover<br>
<br>
W0212 20:28:37.825021 9244 master.cpp:3726] Master returning<br>
resources offered to framework 20150212-200948-46704832-5050-9196-0059<br>
because the framework has terminated or is inactive<br>
<br>
I0212 20:28:37.825500 9244 hierarchical_allocator_process.hpp:405]<br>
Deactivated framework 20150212-200948-46704832-5050-9196-0059<br>
<br>
---<br>
<br>
I do notice that the ip of the scheduler reports as <a href="http://127.0.1.1:47664" \
target="_blank">127.0.1.1:47664</a>,<br> but I have set all of \
/etc/mesos-master/hostname, /etc/mesos-master/ip<br> and /etc/marathon/conf/hostname \
to the private network of the vagrant<br> vms.<br>
<br>
<br>
[1] - <a href="http://mesosphere.com/docs/getting-started/datacenter/install/" \
target="_blank">http://mesosphere.com/docs/getting-started/datacenter/install/</a><br>
</blockquote></div><br></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic