> > For example, a particular slave's webUI (forwarded through master) can be > reached at: > http://localhost:5050/#/slaves/201405120912-16777343-5050-23673-0
Though it looks like the requests are being proxied through the master, your browser is talking directly to the slave for any slave data. Your browser first gets HTML, CSS, and JavaScript from the master and then sends requests directly to the slave's webserver via JSONP for any slave data shown in the UI. Ross Allen [email protected] On 12 May 2014 09:21, Adam Bordelon <[email protected]> wrote: > >> Does each slave expose a webserver ...? > Yes. Each slave hosts a webserver not just for the sandbox, but also for > the slave's own webUI and RESTful API > For example, a particular slave's webUI (forwarded through master) can be > reached at: > http://localhost:5050/#/slaves/201405120912-16777343-5050-23673-0 > > > On Thu, May 8, 2014 at 9:21 AM, Dick Davies <[email protected]>wrote: > >> I've found the sandbox logs to be very useful in debugging >> misbehaving frameworks, typos, etc. - the usual n00b stuff I suppose. >> >> I've got a vagrant stack running quite nicely. If i port forward I can >> view marathon and mesos UIs nicely from my host, but I can't get >> the sandbox logs because 'slaveN' isn't resolving from outside the >> Vagrant stack. >> >> I was a bit surprised because I didn't expect to need to reach the >> slaves directly. >> >> Does each slave expose a webserver to serve up >> sandbox logs or something? Just trying to work out how/if I can >> map things so that UI can be tunnelled easily. >> > >
