mesos-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dick Davies <d...@hellooperator.net>
Subject Re: how does the web UI get sandbox logs?
Date Thu, 15 May 2014 08:46:18 GMT
Won't that also set the IP the slave will advertise for tasks?

( Might not be a problem but thought it was worth pointing out, since Mike said
that was currently on the internal IP. )

On 13 May 2014 18:38, Adam Bordelon <adam@mesosphere.io> wrote:
> mesos-slave --hostname="foo"
> "The hostname the slave should report."
> "If left unset, system hostname will be used (recommended)."
>
>
> On Tue, May 13, 2014 at 8:41 AM, Mike Milner <mike@immun.io> wrote:
>>
>> I just ran into something similar myself with mesos on EC2. I can reach
>> the master just fine using the master's public dns name but when I go to the
>> sandbox it's trying to connect to the slaves private internal DNS name.
>>
>> Is there a configuration option on the slave to manually specify the
>> hostname that should be used in the web UI? I couldn't find anything on
>> http://mesos.apache.org/documentation/latest/configuration/
>>
>> Thanks!
>> Mike
>>
>>
>> On Mon, May 12, 2014 at 4:27 PM, Ross Allen <ross@mesosphere.io> wrote:
>>>>
>>>> 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
>>> ross@mesosphere.io
>>>
>>>
>>> On 12 May 2014 09:21, Adam Bordelon <adam@mesosphere.io> 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 <dick@hellooperator.net>
>>>> 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.
>>>>
>>>>
>>>
>>
>

Mime
View raw message