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 <[email protected]> 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
