You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by Zhi Dou <ha...@gmail.com> on 2012/06/14 08:56:07 UTC
Problem in setting up mesos for spark
Dear all,
I am trying to set up mesos for spark. Following the instruction at
https://github.com/mesos/spark/wiki/Running-Spark-on-Mesos, I use spark 0.4
and get revision 1205738 of Mesos.
OS: Ubuntu 10.04.4
Java: 1.6
There is nothing wrong in /configure. However, I got following errors in *
make*:
g++: error: java/jni/convert.o: No such file or directory
make[1]: *** [java/jni/convert.o] Error 1
make[1]: Leaving directory `/home/zdou/mesos/src'
make: *** [src] Error 2
I also tried the master branch of mesos, but still it does not work.
Could you help me solve this problem? Thank you very much in advance!
Bests,
Harry
Re: Problem in setting up mesos for spark
Posted by Xiaoying Zheng <zh...@sari.ac.cn>.
δΊ 2012/6/14 14:56, Zhi Dou ει:
> Dear all,
>
> I am trying to set up mesos for spark. Following the instruction at
> https://github.com/mesos/spark/wiki/Running-Spark-on-Mesos, I use spark 0.4
> and get revision 1205738 of Mesos.
> OS: Ubuntu 10.04.4
> Java: 1.6
>
> There is nothing wrong in /configure. However, I got following errors in *
> make*:
> g++: error: java/jni/convert.o: No such file or directory
> make[1]: *** [java/jni/convert.o] Error 1
> make[1]: Leaving directory `/home/zdou/mesos/src'
> make: *** [src] Error 2
>
> I also tried the master branch of mesos, but still it does not work.
>
> Could you help me solve this problem? Thank you very much in advance!
>
> Bests,
> Harry
>
hi,
I suppose you're working on the version 1205738 of Mesos. In Makefile
(or Makefile in src folder), there is one redundant flag "-I", which
tries to read Convert.o as an input. Remove this additional "-I", and
make will go though. Anyway, there are more need to be fixed. I couldn't
correct all of them and finally gave up and swithed to the master branch.
RE: WebUI problems
Posted by Jim Donahue <jd...@adobe.com>.
Think I understand the problem -- I failed to set up the master and server ports quite right.
Thanks,
Jim
-----Original Message-----
From: Jim Donahue [mailto:jdonahue@adobe.com]
Sent: Friday, November 02, 2012 1:21 PM
To: mesos-dev@incubator.apache.org
Subject: RE: WebUI problems
Yes, I did start the slave with the --ip parameter set properly.
Let me try having the master use the public IP address of the slave (rather than the AWS internal one) and see what happens. So if I have only one slave and that slave gets removed, would the master log remain empty after the removal even though the master was still ready to handle requests? If so, then I think we know what happened.
Jim
-----Original Message-----
From: Vinod Kone [mailto:vinod@twitter.com]
Sent: Friday, November 02, 2012 12:54 PM
To: mesos-dev@incubator.apache.org
Subject: Re: WebUI problems
>From the logs, the slave never got the 'registered' message from the
master. The master removes/disconnects a slave, when the slave doesn't
respond to its health checks, after a timeout.
Did you try to start the slave with --ip=<public ip> as suggested earlier?
I'm not familiar with AWS networking semantics, but I suspect you cannot
connect from 107.22.185.93 --> 10.96.130.119?
@vinodkone
On Fri, Nov 2, 2012 at 12:36 PM, Jim Donahue <jd...@adobe.com> wrote:
> Ben,
>
> Complete logs are attached. Note that the master log ends long before the
> slave -- seems like the master has decided to go autistic.
>
> The master is using an AWS elastic IP address, which the slave uses to
> connect. The master has a "slaves" file in its deploy directory with an
> entry giving the AWS internal IP address of the slave (and the address in
> the file matches the internal IP address in the AWS management console).
> And it looks like they did rendezvous for a moment -- when I (briefly) got
> the webUI up everything looked right.
>
> Thanks,
>
> Jim
>
> -----Original Message-----
> From: Benjamin Mahler [mailto:bmahler@twitter.com]
> Sent: Friday, November 02, 2012 11:59 AM
> To: mesos-dev@incubator.apache.org
> Subject: Re: WebUI problems
>
> "But I can't connect to the webUI on the slave." -- right, slaves do not
> have their own webuis anymore, the master collects slave information and
> displays it in it's webui.
>
> Do you run in an environment where you have public and private IPs? It
> looks like the slave cannot receive messages from the master. It looks like
> you may want to try --ip=<public_slave_ip> when you start your slave.
>
> Can you provide the full master / slave logs for this?
> Can you also provide the commands you're using to start the master / slave?
>
> On Fri, Nov 2, 2012 at 11:35 AM, Jim Donahue <jd...@adobe.com> wrote:
>
> > Now I'm seeing the master and slave go autistic.
> >
> > Using port 5050, I was able to get the webUI up exactly once and then
> > everything looks like it dies. The log on the master shows a bunch of
> > "slave already registered, resending ack" messages, followed by the slave
> > disconnecting and reconnecting on the same port. Finally, the INFO log
> > ends with an "adding slave" message and then just stops.
> >
> > As far as I can tell, the master is still running. But I can't connect to
> > it again through the webUI.
> >
> > Looking at the slave log, the slave detected the master and then shows
> > periodic reporting of its current disk usage and "allowed age" -- there's
> > no indication of any disconnect in the slave log. But I can't connect to
> > the webUI on the slave.
> >
> >
> > Thanks,
> >
> >
> > Jim
> >
> > -----Original Message-----
> > From: Benjamin Mahler [mailto:bmahler@twitter.com]
> > Sent: Friday, November 02, 2012 10:29 AM
> > To: mesos-dev@incubator.apache.org
> > Subject: Re: WebUI problems
> >
> > We've recently killed the old webui: https://reviews.apache.org/r/7708/
> >
> > In the process, the --webui_port flag was removed as it was no longer
> > applicable. I was under the assumption our flag system would not allow
> > extraneous flags to be provided, but perhaps that not the case.
> >
> > The new webui runs on 5050 as Erich indicated. Please report any issues
> you
> > find!
> >
> > On Fri, Nov 2, 2012 at 10:21 AM, Erich Nachbar <er...@quantifind.com>
> > wrote:
> >
> > > Had the same problem. Try using port 5050 instead of the old 8080. The
> > > webui_port option was ignored when I tried it.
> > >
> > >
> > > On Fri, Nov 2, 2012 at 10:17 AM, Jim Donahue <jd...@adobe.com>
> wrote:
> > >
> > > > Yesterday I built a new AMI using the latest Mesos and now I can't
> > > connect
> > > > to the web UI (which used to work). Logging into the instances (a
> > master
> > > > and a slave), all looks well -- the master sees the slave and the
> slave
> > > > sees the master. Both master and slave were started with the option
> > > >
> > > > --webui_port=5051
> > > >
> > > > But no luck connecting to them with a browser. Has something changed
> > > > recently that I missed? I noticed that I did have to change the
> build
> > > > recipe for my AMI to install some new libraries, but I didn't see any
> > > > errors in the build and the tests all ran, except for the cgroup
> ones.
> > > >
> > > > The other thing I noticed is that the logs on both master and slave
> > have
> > > > names of the form:
> > > >
> > > > ...invalid-user.log.INFO....
> > > >
> > > > Is this something I should worry about?
> > > >
> > > > Thanks,
> > > >
> > > > Jim Donahue
> > > > Adobe Systems
> > > >
> > >
> > >
> > >
> > > --
> > > Erich Nachbar
> > > CTO | Quantifind <http://quantifind.com/>| 650-430-5500
> > >
> >
>
RE: WebUI problems
Posted by Jim Donahue <jd...@adobe.com>.
Yes, I did start the slave with the --ip parameter set properly.
Let me try having the master use the public IP address of the slave (rather than the AWS internal one) and see what happens. So if I have only one slave and that slave gets removed, would the master log remain empty after the removal even though the master was still ready to handle requests? If so, then I think we know what happened.
Jim
-----Original Message-----
From: Vinod Kone [mailto:vinod@twitter.com]
Sent: Friday, November 02, 2012 12:54 PM
To: mesos-dev@incubator.apache.org
Subject: Re: WebUI problems
>From the logs, the slave never got the 'registered' message from the
master. The master removes/disconnects a slave, when the slave doesn't
respond to its health checks, after a timeout.
Did you try to start the slave with --ip=<public ip> as suggested earlier?
I'm not familiar with AWS networking semantics, but I suspect you cannot
connect from 107.22.185.93 --> 10.96.130.119?
@vinodkone
On Fri, Nov 2, 2012 at 12:36 PM, Jim Donahue <jd...@adobe.com> wrote:
> Ben,
>
> Complete logs are attached. Note that the master log ends long before the
> slave -- seems like the master has decided to go autistic.
>
> The master is using an AWS elastic IP address, which the slave uses to
> connect. The master has a "slaves" file in its deploy directory with an
> entry giving the AWS internal IP address of the slave (and the address in
> the file matches the internal IP address in the AWS management console).
> And it looks like they did rendezvous for a moment -- when I (briefly) got
> the webUI up everything looked right.
>
> Thanks,
>
> Jim
>
> -----Original Message-----
> From: Benjamin Mahler [mailto:bmahler@twitter.com]
> Sent: Friday, November 02, 2012 11:59 AM
> To: mesos-dev@incubator.apache.org
> Subject: Re: WebUI problems
>
> "But I can't connect to the webUI on the slave." -- right, slaves do not
> have their own webuis anymore, the master collects slave information and
> displays it in it's webui.
>
> Do you run in an environment where you have public and private IPs? It
> looks like the slave cannot receive messages from the master. It looks like
> you may want to try --ip=<public_slave_ip> when you start your slave.
>
> Can you provide the full master / slave logs for this?
> Can you also provide the commands you're using to start the master / slave?
>
> On Fri, Nov 2, 2012 at 11:35 AM, Jim Donahue <jd...@adobe.com> wrote:
>
> > Now I'm seeing the master and slave go autistic.
> >
> > Using port 5050, I was able to get the webUI up exactly once and then
> > everything looks like it dies. The log on the master shows a bunch of
> > "slave already registered, resending ack" messages, followed by the slave
> > disconnecting and reconnecting on the same port. Finally, the INFO log
> > ends with an "adding slave" message and then just stops.
> >
> > As far as I can tell, the master is still running. But I can't connect to
> > it again through the webUI.
> >
> > Looking at the slave log, the slave detected the master and then shows
> > periodic reporting of its current disk usage and "allowed age" -- there's
> > no indication of any disconnect in the slave log. But I can't connect to
> > the webUI on the slave.
> >
> >
> > Thanks,
> >
> >
> > Jim
> >
> > -----Original Message-----
> > From: Benjamin Mahler [mailto:bmahler@twitter.com]
> > Sent: Friday, November 02, 2012 10:29 AM
> > To: mesos-dev@incubator.apache.org
> > Subject: Re: WebUI problems
> >
> > We've recently killed the old webui: https://reviews.apache.org/r/7708/
> >
> > In the process, the --webui_port flag was removed as it was no longer
> > applicable. I was under the assumption our flag system would not allow
> > extraneous flags to be provided, but perhaps that not the case.
> >
> > The new webui runs on 5050 as Erich indicated. Please report any issues
> you
> > find!
> >
> > On Fri, Nov 2, 2012 at 10:21 AM, Erich Nachbar <er...@quantifind.com>
> > wrote:
> >
> > > Had the same problem. Try using port 5050 instead of the old 8080. The
> > > webui_port option was ignored when I tried it.
> > >
> > >
> > > On Fri, Nov 2, 2012 at 10:17 AM, Jim Donahue <jd...@adobe.com>
> wrote:
> > >
> > > > Yesterday I built a new AMI using the latest Mesos and now I can't
> > > connect
> > > > to the web UI (which used to work). Logging into the instances (a
> > master
> > > > and a slave), all looks well -- the master sees the slave and the
> slave
> > > > sees the master. Both master and slave were started with the option
> > > >
> > > > --webui_port=5051
> > > >
> > > > But no luck connecting to them with a browser. Has something changed
> > > > recently that I missed? I noticed that I did have to change the
> build
> > > > recipe for my AMI to install some new libraries, but I didn't see any
> > > > errors in the build and the tests all ran, except for the cgroup
> ones.
> > > >
> > > > The other thing I noticed is that the logs on both master and slave
> > have
> > > > names of the form:
> > > >
> > > > ...invalid-user.log.INFO....
> > > >
> > > > Is this something I should worry about?
> > > >
> > > > Thanks,
> > > >
> > > > Jim Donahue
> > > > Adobe Systems
> > > >
> > >
> > >
> > >
> > > --
> > > Erich Nachbar
> > > CTO | Quantifind <http://quantifind.com/>| 650-430-5500
> > >
> >
>
Re: WebUI problems
Posted by Vinod Kone <vi...@twitter.com>.
>From the logs, the slave never got the 'registered' message from the
master. The master removes/disconnects a slave, when the slave doesn't
respond to its health checks, after a timeout.
Did you try to start the slave with --ip=<public ip> as suggested earlier?
I'm not familiar with AWS networking semantics, but I suspect you cannot
connect from 107.22.185.93 --> 10.96.130.119?
@vinodkone
On Fri, Nov 2, 2012 at 12:36 PM, Jim Donahue <jd...@adobe.com> wrote:
> Ben,
>
> Complete logs are attached. Note that the master log ends long before the
> slave -- seems like the master has decided to go autistic.
>
> The master is using an AWS elastic IP address, which the slave uses to
> connect. The master has a "slaves" file in its deploy directory with an
> entry giving the AWS internal IP address of the slave (and the address in
> the file matches the internal IP address in the AWS management console).
> And it looks like they did rendezvous for a moment -- when I (briefly) got
> the webUI up everything looked right.
>
> Thanks,
>
> Jim
>
> -----Original Message-----
> From: Benjamin Mahler [mailto:bmahler@twitter.com]
> Sent: Friday, November 02, 2012 11:59 AM
> To: mesos-dev@incubator.apache.org
> Subject: Re: WebUI problems
>
> "But I can't connect to the webUI on the slave." -- right, slaves do not
> have their own webuis anymore, the master collects slave information and
> displays it in it's webui.
>
> Do you run in an environment where you have public and private IPs? It
> looks like the slave cannot receive messages from the master. It looks like
> you may want to try --ip=<public_slave_ip> when you start your slave.
>
> Can you provide the full master / slave logs for this?
> Can you also provide the commands you're using to start the master / slave?
>
> On Fri, Nov 2, 2012 at 11:35 AM, Jim Donahue <jd...@adobe.com> wrote:
>
> > Now I'm seeing the master and slave go autistic.
> >
> > Using port 5050, I was able to get the webUI up exactly once and then
> > everything looks like it dies. The log on the master shows a bunch of
> > "slave already registered, resending ack" messages, followed by the slave
> > disconnecting and reconnecting on the same port. Finally, the INFO log
> > ends with an "adding slave" message and then just stops.
> >
> > As far as I can tell, the master is still running. But I can't connect to
> > it again through the webUI.
> >
> > Looking at the slave log, the slave detected the master and then shows
> > periodic reporting of its current disk usage and "allowed age" -- there's
> > no indication of any disconnect in the slave log. But I can't connect to
> > the webUI on the slave.
> >
> >
> > Thanks,
> >
> >
> > Jim
> >
> > -----Original Message-----
> > From: Benjamin Mahler [mailto:bmahler@twitter.com]
> > Sent: Friday, November 02, 2012 10:29 AM
> > To: mesos-dev@incubator.apache.org
> > Subject: Re: WebUI problems
> >
> > We've recently killed the old webui: https://reviews.apache.org/r/7708/
> >
> > In the process, the --webui_port flag was removed as it was no longer
> > applicable. I was under the assumption our flag system would not allow
> > extraneous flags to be provided, but perhaps that not the case.
> >
> > The new webui runs on 5050 as Erich indicated. Please report any issues
> you
> > find!
> >
> > On Fri, Nov 2, 2012 at 10:21 AM, Erich Nachbar <er...@quantifind.com>
> > wrote:
> >
> > > Had the same problem. Try using port 5050 instead of the old 8080. The
> > > webui_port option was ignored when I tried it.
> > >
> > >
> > > On Fri, Nov 2, 2012 at 10:17 AM, Jim Donahue <jd...@adobe.com>
> wrote:
> > >
> > > > Yesterday I built a new AMI using the latest Mesos and now I can't
> > > connect
> > > > to the web UI (which used to work). Logging into the instances (a
> > master
> > > > and a slave), all looks well -- the master sees the slave and the
> slave
> > > > sees the master. Both master and slave were started with the option
> > > >
> > > > --webui_port=5051
> > > >
> > > > But no luck connecting to them with a browser. Has something changed
> > > > recently that I missed? I noticed that I did have to change the
> build
> > > > recipe for my AMI to install some new libraries, but I didn't see any
> > > > errors in the build and the tests all ran, except for the cgroup
> ones.
> > > >
> > > > The other thing I noticed is that the logs on both master and slave
> > have
> > > > names of the form:
> > > >
> > > > ...invalid-user.log.INFO....
> > > >
> > > > Is this something I should worry about?
> > > >
> > > > Thanks,
> > > >
> > > > Jim Donahue
> > > > Adobe Systems
> > > >
> > >
> > >
> > >
> > > --
> > > Erich Nachbar
> > > CTO | Quantifind <http://quantifind.com/>| 650-430-5500
> > >
> >
>
RE: WebUI problems
Posted by Jim Donahue <jd...@adobe.com>.
Ben,
Complete logs are attached. Note that the master log ends long before the slave -- seems like the master has decided to go autistic.
The master is using an AWS elastic IP address, which the slave uses to connect. The master has a "slaves" file in its deploy directory with an entry giving the AWS internal IP address of the slave (and the address in the file matches the internal IP address in the AWS management console). And it looks like they did rendezvous for a moment -- when I (briefly) got the webUI up everything looked right.
Thanks,
Jim
-----Original Message-----
From: Benjamin Mahler [mailto:bmahler@twitter.com]
Sent: Friday, November 02, 2012 11:59 AM
To: mesos-dev@incubator.apache.org
Subject: Re: WebUI problems
"But I can't connect to the webUI on the slave." -- right, slaves do not
have their own webuis anymore, the master collects slave information and
displays it in it's webui.
Do you run in an environment where you have public and private IPs? It
looks like the slave cannot receive messages from the master. It looks like
you may want to try --ip=<public_slave_ip> when you start your slave.
Can you provide the full master / slave logs for this?
Can you also provide the commands you're using to start the master / slave?
On Fri, Nov 2, 2012 at 11:35 AM, Jim Donahue <jd...@adobe.com> wrote:
> Now I'm seeing the master and slave go autistic.
>
> Using port 5050, I was able to get the webUI up exactly once and then
> everything looks like it dies. The log on the master shows a bunch of
> "slave already registered, resending ack" messages, followed by the slave
> disconnecting and reconnecting on the same port. Finally, the INFO log
> ends with an "adding slave" message and then just stops.
>
> As far as I can tell, the master is still running. But I can't connect to
> it again through the webUI.
>
> Looking at the slave log, the slave detected the master and then shows
> periodic reporting of its current disk usage and "allowed age" -- there's
> no indication of any disconnect in the slave log. But I can't connect to
> the webUI on the slave.
>
>
> Thanks,
>
>
> Jim
>
> -----Original Message-----
> From: Benjamin Mahler [mailto:bmahler@twitter.com]
> Sent: Friday, November 02, 2012 10:29 AM
> To: mesos-dev@incubator.apache.org
> Subject: Re: WebUI problems
>
> We've recently killed the old webui: https://reviews.apache.org/r/7708/
>
> In the process, the --webui_port flag was removed as it was no longer
> applicable. I was under the assumption our flag system would not allow
> extraneous flags to be provided, but perhaps that not the case.
>
> The new webui runs on 5050 as Erich indicated. Please report any issues you
> find!
>
> On Fri, Nov 2, 2012 at 10:21 AM, Erich Nachbar <er...@quantifind.com>
> wrote:
>
> > Had the same problem. Try using port 5050 instead of the old 8080. The
> > webui_port option was ignored when I tried it.
> >
> >
> > On Fri, Nov 2, 2012 at 10:17 AM, Jim Donahue <jd...@adobe.com> wrote:
> >
> > > Yesterday I built a new AMI using the latest Mesos and now I can't
> > connect
> > > to the web UI (which used to work). Logging into the instances (a
> master
> > > and a slave), all looks well -- the master sees the slave and the slave
> > > sees the master. Both master and slave were started with the option
> > >
> > > --webui_port=5051
> > >
> > > But no luck connecting to them with a browser. Has something changed
> > > recently that I missed? I noticed that I did have to change the build
> > > recipe for my AMI to install some new libraries, but I didn't see any
> > > errors in the build and the tests all ran, except for the cgroup ones.
> > >
> > > The other thing I noticed is that the logs on both master and slave
> have
> > > names of the form:
> > >
> > > ...invalid-user.log.INFO....
> > >
> > > Is this something I should worry about?
> > >
> > > Thanks,
> > >
> > > Jim Donahue
> > > Adobe Systems
> > >
> >
> >
> >
> > --
> > Erich Nachbar
> > CTO | Quantifind <http://quantifind.com/>| 650-430-5500
> >
>
Re: Slave ports that need to be opened?
Posted by Benjamin Mahler <bm...@twitter.com>.
These ports are not used for master -> slave communication. Rather, there
are part of what the slave considered to be the resources available to
mesos on your slave machine. Along with cpus, memory, and disk, ports are
considered to be a consumable resource in mesos.
> Is there any way to change this?
Yes they can be changed, along with other available resources, for example:
./mesos-slave <master>
--resources=cpus:4.0;mem:4096;ports:[30000-31000];disk:10240
When the available resources are not specified, we make some assumptions
about what resources to consider available to mesos. This means all the
CPUs, most of the memory, most of the disk, and currently the port range
31000-32000 (the top 1000 non-ephemeral ports).
On Fri, Nov 2, 2012 at 2:18 PM, Jim Donahue <jd...@adobe.com> wrote:
> I notice that my master log has the following entry when my slave connects:
>
> Adding slave 201211021752-3489055242-5050-1589-0 at domU-12-31-39-16-81-89.
> compute-1.internal with cpus=2; mem=6430; ports=[31000-32000]; disk=5301
>
> Are the ports in the range 31000-32000 always used for master->slave
> communication? Is there any way to change this? (Not that I particularly
> need to, but I'm curious.)
>
> Thanks,
>
> Jim Donahue
> Adobe
>
Slave ports that need to be opened?
Posted by Jim Donahue <jd...@adobe.com>.
I notice that my master log has the following entry when my slave connects:
Adding slave 201211021752-3489055242-5050-1589-0 at domU-12-31-39-16-81-89.
compute-1.internal with cpus=2; mem=6430; ports=[31000-32000]; disk=5301
Are the ports in the range 31000-32000 always used for master->slave communication? Is there any way to change this? (Not that I particularly need to, but I'm curious.)
Thanks,
Jim Donahue
Adobe
Re: WebUI problems
Posted by Benjamin Mahler <bm...@twitter.com>.
"But I can't connect to the webUI on the slave." -- right, slaves do not
have their own webuis anymore, the master collects slave information and
displays it in it's webui.
Do you run in an environment where you have public and private IPs? It
looks like the slave cannot receive messages from the master. It looks like
you may want to try --ip=<public_slave_ip> when you start your slave.
Can you provide the full master / slave logs for this?
Can you also provide the commands you're using to start the master / slave?
On Fri, Nov 2, 2012 at 11:35 AM, Jim Donahue <jd...@adobe.com> wrote:
> Now I'm seeing the master and slave go autistic.
>
> Using port 5050, I was able to get the webUI up exactly once and then
> everything looks like it dies. The log on the master shows a bunch of
> "slave already registered, resending ack" messages, followed by the slave
> disconnecting and reconnecting on the same port. Finally, the INFO log
> ends with an "adding slave" message and then just stops.
>
> As far as I can tell, the master is still running. But I can't connect to
> it again through the webUI.
>
> Looking at the slave log, the slave detected the master and then shows
> periodic reporting of its current disk usage and "allowed age" -- there's
> no indication of any disconnect in the slave log. But I can't connect to
> the webUI on the slave.
>
>
> Thanks,
>
>
> Jim
>
> -----Original Message-----
> From: Benjamin Mahler [mailto:bmahler@twitter.com]
> Sent: Friday, November 02, 2012 10:29 AM
> To: mesos-dev@incubator.apache.org
> Subject: Re: WebUI problems
>
> We've recently killed the old webui: https://reviews.apache.org/r/7708/
>
> In the process, the --webui_port flag was removed as it was no longer
> applicable. I was under the assumption our flag system would not allow
> extraneous flags to be provided, but perhaps that not the case.
>
> The new webui runs on 5050 as Erich indicated. Please report any issues you
> find!
>
> On Fri, Nov 2, 2012 at 10:21 AM, Erich Nachbar <er...@quantifind.com>
> wrote:
>
> > Had the same problem. Try using port 5050 instead of the old 8080. The
> > webui_port option was ignored when I tried it.
> >
> >
> > On Fri, Nov 2, 2012 at 10:17 AM, Jim Donahue <jd...@adobe.com> wrote:
> >
> > > Yesterday I built a new AMI using the latest Mesos and now I can't
> > connect
> > > to the web UI (which used to work). Logging into the instances (a
> master
> > > and a slave), all looks well -- the master sees the slave and the slave
> > > sees the master. Both master and slave were started with the option
> > >
> > > --webui_port=5051
> > >
> > > But no luck connecting to them with a browser. Has something changed
> > > recently that I missed? I noticed that I did have to change the build
> > > recipe for my AMI to install some new libraries, but I didn't see any
> > > errors in the build and the tests all ran, except for the cgroup ones.
> > >
> > > The other thing I noticed is that the logs on both master and slave
> have
> > > names of the form:
> > >
> > > ...invalid-user.log.INFO....
> > >
> > > Is this something I should worry about?
> > >
> > > Thanks,
> > >
> > > Jim Donahue
> > > Adobe Systems
> > >
> >
> >
> >
> > --
> > Erich Nachbar
> > CTO | Quantifind <http://quantifind.com/>| 650-430-5500
> >
>
RE: WebUI problems
Posted by Jim Donahue <jd...@adobe.com>.
Now I'm seeing the master and slave go autistic.
Using port 5050, I was able to get the webUI up exactly once and then everything looks like it dies. The log on the master shows a bunch of "slave already registered, resending ack" messages, followed by the slave disconnecting and reconnecting on the same port. Finally, the INFO log ends with an "adding slave" message and then just stops.
As far as I can tell, the master is still running. But I can't connect to it again through the webUI.
Looking at the slave log, the slave detected the master and then shows periodic reporting of its current disk usage and "allowed age" -- there's no indication of any disconnect in the slave log. But I can't connect to the webUI on the slave.
Thanks,
Jim
-----Original Message-----
From: Benjamin Mahler [mailto:bmahler@twitter.com]
Sent: Friday, November 02, 2012 10:29 AM
To: mesos-dev@incubator.apache.org
Subject: Re: WebUI problems
We've recently killed the old webui: https://reviews.apache.org/r/7708/
In the process, the --webui_port flag was removed as it was no longer
applicable. I was under the assumption our flag system would not allow
extraneous flags to be provided, but perhaps that not the case.
The new webui runs on 5050 as Erich indicated. Please report any issues you
find!
On Fri, Nov 2, 2012 at 10:21 AM, Erich Nachbar <er...@quantifind.com> wrote:
> Had the same problem. Try using port 5050 instead of the old 8080. The
> webui_port option was ignored when I tried it.
>
>
> On Fri, Nov 2, 2012 at 10:17 AM, Jim Donahue <jd...@adobe.com> wrote:
>
> > Yesterday I built a new AMI using the latest Mesos and now I can't
> connect
> > to the web UI (which used to work). Logging into the instances (a master
> > and a slave), all looks well -- the master sees the slave and the slave
> > sees the master. Both master and slave were started with the option
> >
> > --webui_port=5051
> >
> > But no luck connecting to them with a browser. Has something changed
> > recently that I missed? I noticed that I did have to change the build
> > recipe for my AMI to install some new libraries, but I didn't see any
> > errors in the build and the tests all ran, except for the cgroup ones.
> >
> > The other thing I noticed is that the logs on both master and slave have
> > names of the form:
> >
> > ...invalid-user.log.INFO....
> >
> > Is this something I should worry about?
> >
> > Thanks,
> >
> > Jim Donahue
> > Adobe Systems
> >
>
>
>
> --
> Erich Nachbar
> CTO | Quantifind <http://quantifind.com/>| 650-430-5500
>
Re: WebUI problems
Posted by Benjamin Mahler <bm...@twitter.com>.
That's my fault, I should have sent a quick email to this list when this
made it's way to trunk. On that note..
On Fri, Nov 2, 2012 at 10:32 AM, Jim Donahue <jd...@adobe.com> wrote:
> Thanks! I guess I wasn't paying attention when that one went flying by ...
>
> Jim
>
> -----Original Message-----
> From: Benjamin Mahler [mailto:bmahler@twitter.com]
> Sent: Friday, November 02, 2012 10:29 AM
> To: mesos-dev@incubator.apache.org
> Subject: Re: WebUI problems
>
> We've recently killed the old webui: https://reviews.apache.org/r/7708/
>
> In the process, the --webui_port flag was removed as it was no longer
> applicable. I was under the assumption our flag system would not allow
> extraneous flags to be provided, but perhaps that not the case.
>
> The new webui runs on 5050 as Erich indicated. Please report any issues you
> find!
>
> On Fri, Nov 2, 2012 at 10:21 AM, Erich Nachbar <er...@quantifind.com>
> wrote:
>
> > Had the same problem. Try using port 5050 instead of the old 8080. The
> > webui_port option was ignored when I tried it.
> >
> >
> > On Fri, Nov 2, 2012 at 10:17 AM, Jim Donahue <jd...@adobe.com> wrote:
> >
> > > Yesterday I built a new AMI using the latest Mesos and now I can't
> > connect
> > > to the web UI (which used to work). Logging into the instances (a
> master
> > > and a slave), all looks well -- the master sees the slave and the slave
> > > sees the master. Both master and slave were started with the option
> > >
> > > --webui_port=5051
> > >
> > > But no luck connecting to them with a browser. Has something changed
> > > recently that I missed? I noticed that I did have to change the build
> > > recipe for my AMI to install some new libraries, but I didn't see any
> > > errors in the build and the tests all ran, except for the cgroup ones.
> > >
> > > The other thing I noticed is that the logs on both master and slave
> have
> > > names of the form:
> > >
> > > ...invalid-user.log.INFO....
> > >
> > > Is this something I should worry about?
> > >
> > > Thanks,
> > >
> > > Jim Donahue
> > > Adobe Systems
> > >
> >
> >
> >
> > --
> > Erich Nachbar
> > CTO | Quantifind <http://quantifind.com/>| 650-430-5500
> >
>
RE: WebUI problems
Posted by Jim Donahue <jd...@adobe.com>.
Thanks! I guess I wasn't paying attention when that one went flying by ...
Jim
-----Original Message-----
From: Benjamin Mahler [mailto:bmahler@twitter.com]
Sent: Friday, November 02, 2012 10:29 AM
To: mesos-dev@incubator.apache.org
Subject: Re: WebUI problems
We've recently killed the old webui: https://reviews.apache.org/r/7708/
In the process, the --webui_port flag was removed as it was no longer
applicable. I was under the assumption our flag system would not allow
extraneous flags to be provided, but perhaps that not the case.
The new webui runs on 5050 as Erich indicated. Please report any issues you
find!
On Fri, Nov 2, 2012 at 10:21 AM, Erich Nachbar <er...@quantifind.com> wrote:
> Had the same problem. Try using port 5050 instead of the old 8080. The
> webui_port option was ignored when I tried it.
>
>
> On Fri, Nov 2, 2012 at 10:17 AM, Jim Donahue <jd...@adobe.com> wrote:
>
> > Yesterday I built a new AMI using the latest Mesos and now I can't
> connect
> > to the web UI (which used to work). Logging into the instances (a master
> > and a slave), all looks well -- the master sees the slave and the slave
> > sees the master. Both master and slave were started with the option
> >
> > --webui_port=5051
> >
> > But no luck connecting to them with a browser. Has something changed
> > recently that I missed? I noticed that I did have to change the build
> > recipe for my AMI to install some new libraries, but I didn't see any
> > errors in the build and the tests all ran, except for the cgroup ones.
> >
> > The other thing I noticed is that the logs on both master and slave have
> > names of the form:
> >
> > ...invalid-user.log.INFO....
> >
> > Is this something I should worry about?
> >
> > Thanks,
> >
> > Jim Donahue
> > Adobe Systems
> >
>
>
>
> --
> Erich Nachbar
> CTO | Quantifind <http://quantifind.com/>| 650-430-5500
>
Re: WebUI problems
Posted by Benjamin Mahler <bm...@twitter.com>.
We've recently killed the old webui: https://reviews.apache.org/r/7708/
In the process, the --webui_port flag was removed as it was no longer
applicable. I was under the assumption our flag system would not allow
extraneous flags to be provided, but perhaps that not the case.
The new webui runs on 5050 as Erich indicated. Please report any issues you
find!
On Fri, Nov 2, 2012 at 10:21 AM, Erich Nachbar <er...@quantifind.com> wrote:
> Had the same problem. Try using port 5050 instead of the old 8080. The
> webui_port option was ignored when I tried it.
>
>
> On Fri, Nov 2, 2012 at 10:17 AM, Jim Donahue <jd...@adobe.com> wrote:
>
> > Yesterday I built a new AMI using the latest Mesos and now I can't
> connect
> > to the web UI (which used to work). Logging into the instances (a master
> > and a slave), all looks well -- the master sees the slave and the slave
> > sees the master. Both master and slave were started with the option
> >
> > --webui_port=5051
> >
> > But no luck connecting to them with a browser. Has something changed
> > recently that I missed? I noticed that I did have to change the build
> > recipe for my AMI to install some new libraries, but I didn't see any
> > errors in the build and the tests all ran, except for the cgroup ones.
> >
> > The other thing I noticed is that the logs on both master and slave have
> > names of the form:
> >
> > ...invalid-user.log.INFO....
> >
> > Is this something I should worry about?
> >
> > Thanks,
> >
> > Jim Donahue
> > Adobe Systems
> >
>
>
>
> --
> Erich Nachbar
> CTO | Quantifind <http://quantifind.com/>| 650-430-5500
>
Re: WebUI problems
Posted by Erich Nachbar <er...@quantifind.com>.
Had the same problem. Try using port 5050 instead of the old 8080. The
webui_port option was ignored when I tried it.
On Fri, Nov 2, 2012 at 10:17 AM, Jim Donahue <jd...@adobe.com> wrote:
> Yesterday I built a new AMI using the latest Mesos and now I can't connect
> to the web UI (which used to work). Logging into the instances (a master
> and a slave), all looks well -- the master sees the slave and the slave
> sees the master. Both master and slave were started with the option
>
> --webui_port=5051
>
> But no luck connecting to them with a browser. Has something changed
> recently that I missed? I noticed that I did have to change the build
> recipe for my AMI to install some new libraries, but I didn't see any
> errors in the build and the tests all ran, except for the cgroup ones.
>
> The other thing I noticed is that the logs on both master and slave have
> names of the form:
>
> ...invalid-user.log.INFO....
>
> Is this something I should worry about?
>
> Thanks,
>
> Jim Donahue
> Adobe Systems
>
--
Erich Nachbar
CTO | Quantifind <http://quantifind.com/>| 650-430-5500
WebUI problems
Posted by Jim Donahue <jd...@adobe.com>.
Yesterday I built a new AMI using the latest Mesos and now I can't connect to the web UI (which used to work). Logging into the instances (a master and a slave), all looks well -- the master sees the slave and the slave sees the master. Both master and slave were started with the option
--webui_port=5051
But no luck connecting to them with a browser. Has something changed recently that I missed? I noticed that I did have to change the build recipe for my AMI to install some new libraries, but I didn't see any errors in the build and the tests all ran, except for the cgroup ones.
The other thing I noticed is that the logs on both master and slave have names of the form:
...invalid-user.log.INFO....
Is this something I should worry about?
Thanks,
Jim Donahue
Adobe Systems