You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Dan Dong <do...@gmail.com> on 2015/01/21 23:04:21 UTC
Unable to follow "Sandbox" links from Mesos UI.
Hi, All,
When I try to access sandbox on mesos UI, I see the following info( The
same error appears on every slave sandbox.):
"Failed to connect to slave '20150115-144719-3205108908-5050-4552-S0'
on 'centos-2.local:5051'.
Potential reasons:
The slave's hostname, 'centos-2.local', is not accessible from your
network The slave's port, '5051', is not accessible from your network"
I checked that:
slave centos-2.local can be login from any machine in the cluster without
password by "ssh centos-2.local ";
port 5051 on slave centos-2.local could be connected from master by
"telnet centos-2.local 5051"
The stdout and stderr are there on each slave's /tmp/mesos/..., but
seems mesos UI just could not access it.
(and Both master and slaves are on the same network IP ranges).
Should I open any port on slaves? Any hint what's the problem here?
Cheers,
Dan
Re: Unable to follow "Sandbox" links from Mesos UI.
Posted by Dan Dong <do...@gmail.com>.
Hi, Alex,
After I switch to firefox31.3.0 from another server( it is firefox3.6.11
on the previous server when I found firebug could not be installed on it),
all things work now. The link of stdout/stderr still point to the master's
IP when I hover cursor on the link, but now the new popped window can show
all the right contents, what a mess! Thanks a lot.
Cheers,
Dan
2015-01-27 15:41 GMT-06:00 Alex Rukletsov <al...@mesosphere.io>:
> Let's make sure instead of assuming. Could you please add this line:
> console.log('Fetch url:', url);
> between lines 17 and 18, click the link, copy the output from Firebug or
> Chrome dev console and paste it here together with the link corresponding
> to the download button?
>
> Thanks,
> Alex
>
> On Tue, Jan 27, 2015 at 9:19 PM, Dan Dong <do...@gmail.com> wrote:
>
>> Hi, All,
>> Checked again that when I hover cursor on the stdout/stderr, it points
>> to links of IP address of the master node, so that's why when clicking on
>> it nothing will show up. While the "Download" button beside it points
>> correctly to the IP address of slave node, so I can download them without
>> problem. Seems a config problem somewhere? A bit lost here.
>>
>> So seems the "host" in the pailer function is resolved to master instead
>> of slave node:
>>
>> 14 // Invokes the pailer for the specified host and path using the
>> 15 // specified window_title.
>> 16 function pailer(host, path, window_title) {
>> 17 var url = 'http://' + host + '/files/read.json?path=' + path;
>> 18 var pailer =
>> 19 window.open('/static/pailer.html', url, 'width=580px,
>> height=700px');
>> 20
>> 21 // Need to use window.onload instead of document.ready to make
>> 22 // sure the title doesn't get overwritten.
>> 23 pailer.onload = function() {
>> 24 pailer.document.title = window_title + ' (' + host + ')';
>> 25 };
>> 26 }
>> 27
>>
>>
>> Cheers,
>> Dan
>>
>>
>> 2015-01-27 2:51 GMT-06:00 Alex Rukletsov <al...@mesosphere.io>:
>>
>> Dan,
>>>
>>> the link to the sandbox on a slave is prepared in the JS. As Geoffroy
>>> suggests, could you please check that the JS code works correctly and
>>> the url is constructed normally (see controllers.js:16)? If
>>> everything's fine on your side, could you please file a JIRA for this
>>> issue?
>>>
>>> On Tue, Jan 27, 2015 at 8:21 AM, Geoffroy Jabouley
>>> <ge...@gmail.com> wrote:
>>> > Hello
>>> >
>>> > just in case, which internet browser are you using?
>>> >
>>> > Do you have installed any extensions (NoScript, Ghostery, ...) that
>>> could
>>> > prevent the display /statis/pailer display?
>>> >
>>> > I personnaly use NoScript with Firefox, and i have to turn it off on
>>> all @IP
>>> > of our cluster to correctly access slave information from Mesos UI.
>>> >
>>> > My 2 cents
>>> > Regards
>>> >
>>> > 2015-01-26 21:08 GMT+01:00 Suijian Zhou <su...@ige-project.eu>:
>>> >>
>>> >> Hi, Alex,
>>> >> Yes, I can see the link points to the slave machine when I hover on
>>> the
>>> >> "Download" button and stdout/stderr can be downloaded. So do you mean
>>> it is
>>> >> expected/designed that clicking on 'stdout/stderr' themselves will
>>> not show
>>> >> you anything? Thanks!
>>> >>
>>> >> Cheers,
>>> >> Dan
>>> >>
>>> >>
>>> >> 2015-01-26 7:44 GMT-06:00 Alex Rukletsov <al...@mesosphere.io>:
>>> >>>
>>> >>> Dan,
>>> >>>
>>> >>> that's correct. The 'static/pailer.html' is a page that lives on the
>>> >>> master and it gets a url to the actual slave as a parameter. The url
>>> >>> is computed in 'controllers.js' based on where the associated
>>> executor
>>> >>> lives. You should see this 'actual' url if you hover over the
>>> Download
>>> >>> button. Please check this url for correctness and that you can access
>>> >>> it from your browser.
>>> >>>
>>> >>> On Fri, Jan 23, 2015 at 9:24 PM, Dan Dong <do...@gmail.com>
>>> wrote:
>>> >>> > I see the problem: when I move the cursor onto the link, e.g:
>>> stderr,
>>> >>> > it
>>> >>> > actually points to the IP address of the master machine, so it
>>> trys to
>>> >>> > follow links of Master_IP:/tmp/mesos/slaves/...
>>> >>> > which is not there. So why the link does not point to the IP
>>> address
>>> >>> > of
>>> >>> > slaves( config problems somewhere?)?
>>> >>> >
>>> >>> > Cheers,
>>> >>> > Dan
>>> >>> >
>>> >>> >
>>> >>> > 2015-01-23 11:25 GMT-06:00 Dick Davies <di...@hellooperator.net>:
>>> >>> >
>>> >>> >> Start with 'inspect element' in the browser and see if that gives
>>> any
>>> >>> >> clues.
>>> >>> >> Sounds like your network is a little strict so it may be something
>>> >>> >> else needs opening up.
>>> >>> >>
>>> >>> >> On 23 January 2015 at 16:56, Dan Dong <do...@gmail.com>
>>> wrote:
>>> >>> >> > Hi, Alex,
>>> >>> >> > That is what expected, but when I click on it, it pops a new
>>> blank
>>> >>> >> > window(pailer.html) without the content of the file(9KB size).
>>> Any
>>> >>> >> > hints?
>>> >>> >> >
>>> >>> >> > Cheers,
>>> >>> >> > Dan
>>> >>> >> >
>>> >>> >> >
>>> >>> >> > 2015-01-23 4:37 GMT-06:00 Alex Rukletsov <al...@mesosphere.io>:
>>> >>> >> >
>>> >>> >> >> Dan,
>>> >>> >> >>
>>> >>> >> >> you should be able to view file contents just by clicking on
>>> the
>>> >>> >> >> link.
>>> >>> >> >>
>>> >>> >> >> On Thu, Jan 22, 2015 at 9:57 PM, Dan Dong <dongdan39@gmail.com
>>> >
>>> >>> >> >> wrote:
>>> >>> >> >>>
>>> >>> >> >>> Yes, --hostname solves the problem. Now I can see all files
>>> there
>>> >>> >> >>> like
>>> >>> >> >>> stdout, stderr etc, but when I click on e.g stdout, it pops a
>>> new
>>> >>> >> >>> blank
>>> >>> >> >>> window(pailer.html) without the content of the file(9KB size).
>>> >>> >> >>> Although it
>>> >>> >> >>> provides a "Download" link beside, it would be much more
>>> >>> >> >>> convenient if
>>> >>> >> >>> one
>>> >>> >> >>> can view the stdout and stderr directly. Is this normal or
>>> there
>>> >>> >> >>> is
>>> >>> >> >>> still
>>> >>> >> >>> problem on my envs? Thanks!
>>> >>> >> >>>
>>> >>> >> >>> Cheers,
>>> >>> >> >>> Dan
>>> >>> >> >>>
>>> >>> >> >>>
>>> >>> >> >>> 2015-01-22 11:33 GMT-06:00 Adam Bordelon <adam@mesosphere.io
>>> >:
>>> >>> >> >>>
>>> >>> >> >>>> Try the --hostname parameters for master/slave. If you want
>>> to be
>>> >>> >> >>>> extra
>>> >>> >> >>>> explicit about the IP (e.g. publish the public IP instead of
>>> the
>>> >>> >> >>>> private one
>>> >>> >> >>>> in a cloud environment), you can also set the --ip parameter
>>> on
>>> >>> >> >>>> master/slave.
>>> >>> >> >>>>
>>> >>> >> >>>> On Thu, Jan 22, 2015 at 8:43 AM, Dan Dong <
>>> dongdan39@gmail.com>
>>> >>> >> >>>> wrote:
>>> >>> >> >>>>>
>>> >>> >> >>>>> Thanks Ryan, yes, from the machine where the browser is on
>>> slave
>>> >>> >> >>>>> hostnames could not be resolved, so that's why failure, but
>>> it
>>> >>> >> >>>>> can
>>> >>> >> >>>>> reach
>>> >>> >> >>>>> them by IP address( I don't think sys admin would like to
>>> add
>>> >>> >> >>>>> those
>>> >>> >> >>>>> VMs
>>> >>> >> >>>>> entries to /etc/hosts on the server). I tried to change
>>> masters
>>> >>> >> >>>>> and
>>> >>> >> >>>>> slaves
>>> >>> >> >>>>> of mesos to IP addresses instead of hostname but UI still
>>> points
>>> >>> >> >>>>> to
>>> >>> >> >>>>> hostnames of slaves. Is threre a way to let mesos only use
>>> IP
>>> >>> >> >>>>> address of
>>> >>> >> >>>>> master and slaves?
>>> >>> >> >>>>>
>>> >>> >> >>>>> Cheers,
>>> >>> >> >>>>> Dan
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>> 2015-01-22 9:48 GMT-06:00 Ryan Thomas <r.n.thomas@gmail.com
>>> >:
>>> >>> >> >>>>>
>>> >>> >> >>>>>> It is a request from your browser session, not from the
>>> master
>>> >>> >> >>>>>> that
>>> >>> >> >>>>>> is
>>> >>> >> >>>>>> going to the slaves - so in order to view the sandbox you
>>> need
>>> >>> >> >>>>>> to
>>> >>> >> >>>>>> ensure
>>> >>> >> >>>>>> that the machine your browser is on can resolve and route
>>> to
>>> >>> >> >>>>>> the
>>> >>> >> >>>>>> masters
>>> >>> >> >>>>>> _and_ the slaves.
>>> >>> >> >>>>>>
>>> >>> >> >>>>>> The master doesn't proxy the sandbox requests through
>>> itself
>>> >>> >> >>>>>> (yet)
>>> >>> >> >>>>>> -
>>> >>> >> >>>>>> they are made directly from your browser instance to the
>>> >>> >> >>>>>> slaves.
>>> >>> >> >>>>>>
>>> >>> >> >>>>>> Make sure you can resolve the slaves from the machine
>>> you're
>>> >>> >> >>>>>> browsing
>>> >>> >> >>>>>> the UI on.
>>> >>> >> >>>>>>
>>> >>> >> >>>>>> Cheers,
>>> >>> >> >>>>>>
>>> >>> >> >>>>>> ryan
>>> >>> >> >>>>>>
>>> >>> >> >>>>>> On 22 January 2015 at 15:42, Dan Dong <dongdan39@gmail.com
>>> >
>>> >>> >> >>>>>> wrote:
>>> >>> >> >>>>>>>
>>> >>> >> >>>>>>> Thank you all, the master and slaves can resolve each
>>> others'
>>> >>> >> >>>>>>> hostname and ssh login without password, firewalls have
>>> been
>>> >>> >> >>>>>>> switched off on
>>> >>> >> >>>>>>> all the machines too.
>>> >>> >> >>>>>>> So I'm confused what will block such a pull of info of
>>> slaves
>>> >>> >> >>>>>>> from
>>> >>> >> >>>>>>> UI?
>>> >>> >> >>>>>>>
>>> >>> >> >>>>>>> Cheers,
>>> >>> >> >>>>>>> Dan
>>> >>> >> >>>>>>>
>>> >>> >> >>>>>>>
>>> >>> >> >>>>>>> 2015-01-21 16:35 GMT-06:00 Cody Maloney <
>>> cody@mesosphere.io>:
>>> >>> >> >>>>>>>
>>> >>> >> >>>>>>>> Also see
>>> https://issues.apache.org/jira/browse/MESOS-2129 if
>>> >>> >> >>>>>>>> you
>>> >>> >> >>>>>>>> want to track progress on changing this.
>>> >>> >> >>>>>>>>
>>> >>> >> >>>>>>>> Unfortunately it is on hold for me at the moment to fix.
>>> >>> >> >>>>>>>>
>>> >>> >> >>>>>>>> Cody
>>> >>> >> >>>>>>>>
>>> >>> >> >>>>>>>> On Wed, Jan 21, 2015 at 2:07 PM, Ryan Thomas
>>> >>> >> >>>>>>>> <r....@gmail.com>
>>> >>> >> >>>>>>>> wrote:
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> Hey Dan,
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> The UI will attempt to pull that info directly from the
>>> >>> >> >>>>>>>>> slave so
>>> >>> >> >>>>>>>>> you need to make sure the host is resolvable and
>>> routeable
>>> >>> >> >>>>>>>>> from
>>> >>> >> >>>>>>>>> your
>>> >>> >> >>>>>>>>> browser.
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> Cheers,
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> Ryan
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> From my phone
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> On Wednesday, 21 January 2015, Dan Dong
>>> >>> >> >>>>>>>>> <do...@gmail.com>
>>> >>> >> >>>>>>>>> wrote:
>>> >>> >> >>>>>>>>>>
>>> >>> >> >>>>>>>>>> Hi, All,
>>> >>> >> >>>>>>>>>> When I try to access sandbox on mesos UI, I see the
>>> >>> >> >>>>>>>>>> following
>>> >>> >> >>>>>>>>>> info( The
>>> >>> >> >>>>>>>>>> same error appears on every slave sandbox.):
>>> >>> >> >>>>>>>>>>
>>> >>> >> >>>>>>>>>> "Failed to connect to slave
>>> >>> >> >>>>>>>>>> '20150115-144719-3205108908-5050-4552-S0'
>>> >>> >> >>>>>>>>>> on 'centos-2.local:5051'.
>>> >>> >> >>>>>>>>>>
>>> >>> >> >>>>>>>>>> Potential reasons:
>>> >>> >> >>>>>>>>>> The slave's hostname, 'centos-2.local', is not
>>> accessible
>>> >>> >> >>>>>>>>>> from
>>> >>> >> >>>>>>>>>> your
>>> >>> >> >>>>>>>>>> network The slave's port, '5051', is not accessible
>>> from
>>> >>> >> >>>>>>>>>> your
>>> >>> >> >>>>>>>>>> network"
>>> >>> >> >>>>>>>>>>
>>> >>> >> >>>>>>>>>>
>>> >>> >> >>>>>>>>>> I checked that:
>>> >>> >> >>>>>>>>>> slave centos-2.local can be login from any machine in
>>> the
>>> >>> >> >>>>>>>>>> cluster
>>> >>> >> >>>>>>>>>> without
>>> >>> >> >>>>>>>>>> password by "ssh centos-2.local ";
>>> >>> >> >>>>>>>>>>
>>> >>> >> >>>>>>>>>> port 5051 on slave centos-2.local could be connected
>>> from
>>> >>> >> >>>>>>>>>> master
>>> >>> >> >>>>>>>>>> by
>>> >>> >> >>>>>>>>>> "telnet centos-2.local 5051"
>>> >>> >> >>>>>>>>>>
>>> >>> >> >>>>>>>>>> The stdout and stderr are there on each slave's
>>> >>> >> >>>>>>>>>> /tmp/mesos/...,
>>> >>> >> >>>>>>>>>> but seems mesos UI just could not access it.
>>> >>> >> >>>>>>>>>> (and Both master and slaves are on the same network IP
>>> >>> >> >>>>>>>>>> ranges).
>>> >>> >> >>>>>>>>>> Should I open any port on slaves? Any hint what's the
>>> >>> >> >>>>>>>>>> problem
>>> >>> >> >>>>>>>>>> here?
>>> >>> >> >>>>>>>>>>
>>> >>> >> >>>>>>>>>> Cheers,
>>> >>> >> >>>>>>>>>> Dan
>>> >>> >> >>>>>>>>
>>> >>> >> >>>>>>>>
>>> >>> >> >>>>>>>
>>> >>> >> >>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>
>>> >>> >> >>>
>>> >>> >> >>
>>> >>> >> >
>>> >>> >
>>> >>> >
>>> >>
>>> >>
>>> >
>>>
>>
>>
>
Re: Unable to follow "Sandbox" links from Mesos UI.
Posted by Alex Rukletsov <al...@mesosphere.io>.
Let's make sure instead of assuming. Could you please add this line:
console.log('Fetch url:', url);
between lines 17 and 18, click the link, copy the output from Firebug or
Chrome dev console and paste it here together with the link corresponding
to the download button?
Thanks,
Alex
On Tue, Jan 27, 2015 at 9:19 PM, Dan Dong <do...@gmail.com> wrote:
> Hi, All,
> Checked again that when I hover cursor on the stdout/stderr, it points
> to links of IP address of the master node, so that's why when clicking on
> it nothing will show up. While the "Download" button beside it points
> correctly to the IP address of slave node, so I can download them without
> problem. Seems a config problem somewhere? A bit lost here.
>
> So seems the "host" in the pailer function is resolved to master instead
> of slave node:
>
> 14 // Invokes the pailer for the specified host and path using the
> 15 // specified window_title.
> 16 function pailer(host, path, window_title) {
> 17 var url = 'http://' + host + '/files/read.json?path=' + path;
> 18 var pailer =
> 19 window.open('/static/pailer.html', url, 'width=580px,
> height=700px');
> 20
> 21 // Need to use window.onload instead of document.ready to make
> 22 // sure the title doesn't get overwritten.
> 23 pailer.onload = function() {
> 24 pailer.document.title = window_title + ' (' + host + ')';
> 25 };
> 26 }
> 27
>
>
> Cheers,
> Dan
>
>
> 2015-01-27 2:51 GMT-06:00 Alex Rukletsov <al...@mesosphere.io>:
>
> Dan,
>>
>> the link to the sandbox on a slave is prepared in the JS. As Geoffroy
>> suggests, could you please check that the JS code works correctly and
>> the url is constructed normally (see controllers.js:16)? If
>> everything's fine on your side, could you please file a JIRA for this
>> issue?
>>
>> On Tue, Jan 27, 2015 at 8:21 AM, Geoffroy Jabouley
>> <ge...@gmail.com> wrote:
>> > Hello
>> >
>> > just in case, which internet browser are you using?
>> >
>> > Do you have installed any extensions (NoScript, Ghostery, ...) that
>> could
>> > prevent the display /statis/pailer display?
>> >
>> > I personnaly use NoScript with Firefox, and i have to turn it off on
>> all @IP
>> > of our cluster to correctly access slave information from Mesos UI.
>> >
>> > My 2 cents
>> > Regards
>> >
>> > 2015-01-26 21:08 GMT+01:00 Suijian Zhou <su...@ige-project.eu>:
>> >>
>> >> Hi, Alex,
>> >> Yes, I can see the link points to the slave machine when I hover on
>> the
>> >> "Download" button and stdout/stderr can be downloaded. So do you mean
>> it is
>> >> expected/designed that clicking on 'stdout/stderr' themselves will not
>> show
>> >> you anything? Thanks!
>> >>
>> >> Cheers,
>> >> Dan
>> >>
>> >>
>> >> 2015-01-26 7:44 GMT-06:00 Alex Rukletsov <al...@mesosphere.io>:
>> >>>
>> >>> Dan,
>> >>>
>> >>> that's correct. The 'static/pailer.html' is a page that lives on the
>> >>> master and it gets a url to the actual slave as a parameter. The url
>> >>> is computed in 'controllers.js' based on where the associated executor
>> >>> lives. You should see this 'actual' url if you hover over the Download
>> >>> button. Please check this url for correctness and that you can access
>> >>> it from your browser.
>> >>>
>> >>> On Fri, Jan 23, 2015 at 9:24 PM, Dan Dong <do...@gmail.com>
>> wrote:
>> >>> > I see the problem: when I move the cursor onto the link, e.g:
>> stderr,
>> >>> > it
>> >>> > actually points to the IP address of the master machine, so it trys
>> to
>> >>> > follow links of Master_IP:/tmp/mesos/slaves/...
>> >>> > which is not there. So why the link does not point to the IP
>> address
>> >>> > of
>> >>> > slaves( config problems somewhere?)?
>> >>> >
>> >>> > Cheers,
>> >>> > Dan
>> >>> >
>> >>> >
>> >>> > 2015-01-23 11:25 GMT-06:00 Dick Davies <di...@hellooperator.net>:
>> >>> >
>> >>> >> Start with 'inspect element' in the browser and see if that gives
>> any
>> >>> >> clues.
>> >>> >> Sounds like your network is a little strict so it may be something
>> >>> >> else needs opening up.
>> >>> >>
>> >>> >> On 23 January 2015 at 16:56, Dan Dong <do...@gmail.com> wrote:
>> >>> >> > Hi, Alex,
>> >>> >> > That is what expected, but when I click on it, it pops a new
>> blank
>> >>> >> > window(pailer.html) without the content of the file(9KB size).
>> Any
>> >>> >> > hints?
>> >>> >> >
>> >>> >> > Cheers,
>> >>> >> > Dan
>> >>> >> >
>> >>> >> >
>> >>> >> > 2015-01-23 4:37 GMT-06:00 Alex Rukletsov <al...@mesosphere.io>:
>> >>> >> >
>> >>> >> >> Dan,
>> >>> >> >>
>> >>> >> >> you should be able to view file contents just by clicking on the
>> >>> >> >> link.
>> >>> >> >>
>> >>> >> >> On Thu, Jan 22, 2015 at 9:57 PM, Dan Dong <do...@gmail.com>
>> >>> >> >> wrote:
>> >>> >> >>>
>> >>> >> >>> Yes, --hostname solves the problem. Now I can see all files
>> there
>> >>> >> >>> like
>> >>> >> >>> stdout, stderr etc, but when I click on e.g stdout, it pops a
>> new
>> >>> >> >>> blank
>> >>> >> >>> window(pailer.html) without the content of the file(9KB size).
>> >>> >> >>> Although it
>> >>> >> >>> provides a "Download" link beside, it would be much more
>> >>> >> >>> convenient if
>> >>> >> >>> one
>> >>> >> >>> can view the stdout and stderr directly. Is this normal or
>> there
>> >>> >> >>> is
>> >>> >> >>> still
>> >>> >> >>> problem on my envs? Thanks!
>> >>> >> >>>
>> >>> >> >>> Cheers,
>> >>> >> >>> Dan
>> >>> >> >>>
>> >>> >> >>>
>> >>> >> >>> 2015-01-22 11:33 GMT-06:00 Adam Bordelon <ad...@mesosphere.io>:
>> >>> >> >>>
>> >>> >> >>>> Try the --hostname parameters for master/slave. If you want
>> to be
>> >>> >> >>>> extra
>> >>> >> >>>> explicit about the IP (e.g. publish the public IP instead of
>> the
>> >>> >> >>>> private one
>> >>> >> >>>> in a cloud environment), you can also set the --ip parameter
>> on
>> >>> >> >>>> master/slave.
>> >>> >> >>>>
>> >>> >> >>>> On Thu, Jan 22, 2015 at 8:43 AM, Dan Dong <
>> dongdan39@gmail.com>
>> >>> >> >>>> wrote:
>> >>> >> >>>>>
>> >>> >> >>>>> Thanks Ryan, yes, from the machine where the browser is on
>> slave
>> >>> >> >>>>> hostnames could not be resolved, so that's why failure, but
>> it
>> >>> >> >>>>> can
>> >>> >> >>>>> reach
>> >>> >> >>>>> them by IP address( I don't think sys admin would like to add
>> >>> >> >>>>> those
>> >>> >> >>>>> VMs
>> >>> >> >>>>> entries to /etc/hosts on the server). I tried to change
>> masters
>> >>> >> >>>>> and
>> >>> >> >>>>> slaves
>> >>> >> >>>>> of mesos to IP addresses instead of hostname but UI still
>> points
>> >>> >> >>>>> to
>> >>> >> >>>>> hostnames of slaves. Is threre a way to let mesos only use IP
>> >>> >> >>>>> address of
>> >>> >> >>>>> master and slaves?
>> >>> >> >>>>>
>> >>> >> >>>>> Cheers,
>> >>> >> >>>>> Dan
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>> 2015-01-22 9:48 GMT-06:00 Ryan Thomas <r.n.thomas@gmail.com
>> >:
>> >>> >> >>>>>
>> >>> >> >>>>>> It is a request from your browser session, not from the
>> master
>> >>> >> >>>>>> that
>> >>> >> >>>>>> is
>> >>> >> >>>>>> going to the slaves - so in order to view the sandbox you
>> need
>> >>> >> >>>>>> to
>> >>> >> >>>>>> ensure
>> >>> >> >>>>>> that the machine your browser is on can resolve and route to
>> >>> >> >>>>>> the
>> >>> >> >>>>>> masters
>> >>> >> >>>>>> _and_ the slaves.
>> >>> >> >>>>>>
>> >>> >> >>>>>> The master doesn't proxy the sandbox requests through itself
>> >>> >> >>>>>> (yet)
>> >>> >> >>>>>> -
>> >>> >> >>>>>> they are made directly from your browser instance to the
>> >>> >> >>>>>> slaves.
>> >>> >> >>>>>>
>> >>> >> >>>>>> Make sure you can resolve the slaves from the machine you're
>> >>> >> >>>>>> browsing
>> >>> >> >>>>>> the UI on.
>> >>> >> >>>>>>
>> >>> >> >>>>>> Cheers,
>> >>> >> >>>>>>
>> >>> >> >>>>>> ryan
>> >>> >> >>>>>>
>> >>> >> >>>>>> On 22 January 2015 at 15:42, Dan Dong <do...@gmail.com>
>> >>> >> >>>>>> wrote:
>> >>> >> >>>>>>>
>> >>> >> >>>>>>> Thank you all, the master and slaves can resolve each
>> others'
>> >>> >> >>>>>>> hostname and ssh login without password, firewalls have
>> been
>> >>> >> >>>>>>> switched off on
>> >>> >> >>>>>>> all the machines too.
>> >>> >> >>>>>>> So I'm confused what will block such a pull of info of
>> slaves
>> >>> >> >>>>>>> from
>> >>> >> >>>>>>> UI?
>> >>> >> >>>>>>>
>> >>> >> >>>>>>> Cheers,
>> >>> >> >>>>>>> Dan
>> >>> >> >>>>>>>
>> >>> >> >>>>>>>
>> >>> >> >>>>>>> 2015-01-21 16:35 GMT-06:00 Cody Maloney <
>> cody@mesosphere.io>:
>> >>> >> >>>>>>>
>> >>> >> >>>>>>>> Also see https://issues.apache.org/jira/browse/MESOS-2129
>> if
>> >>> >> >>>>>>>> you
>> >>> >> >>>>>>>> want to track progress on changing this.
>> >>> >> >>>>>>>>
>> >>> >> >>>>>>>> Unfortunately it is on hold for me at the moment to fix.
>> >>> >> >>>>>>>>
>> >>> >> >>>>>>>> Cody
>> >>> >> >>>>>>>>
>> >>> >> >>>>>>>> On Wed, Jan 21, 2015 at 2:07 PM, Ryan Thomas
>> >>> >> >>>>>>>> <r....@gmail.com>
>> >>> >> >>>>>>>> wrote:
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> Hey Dan,
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> The UI will attempt to pull that info directly from the
>> >>> >> >>>>>>>>> slave so
>> >>> >> >>>>>>>>> you need to make sure the host is resolvable and
>> routeable
>> >>> >> >>>>>>>>> from
>> >>> >> >>>>>>>>> your
>> >>> >> >>>>>>>>> browser.
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> Cheers,
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> Ryan
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> From my phone
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> On Wednesday, 21 January 2015, Dan Dong
>> >>> >> >>>>>>>>> <do...@gmail.com>
>> >>> >> >>>>>>>>> wrote:
>> >>> >> >>>>>>>>>>
>> >>> >> >>>>>>>>>> Hi, All,
>> >>> >> >>>>>>>>>> When I try to access sandbox on mesos UI, I see the
>> >>> >> >>>>>>>>>> following
>> >>> >> >>>>>>>>>> info( The
>> >>> >> >>>>>>>>>> same error appears on every slave sandbox.):
>> >>> >> >>>>>>>>>>
>> >>> >> >>>>>>>>>> "Failed to connect to slave
>> >>> >> >>>>>>>>>> '20150115-144719-3205108908-5050-4552-S0'
>> >>> >> >>>>>>>>>> on 'centos-2.local:5051'.
>> >>> >> >>>>>>>>>>
>> >>> >> >>>>>>>>>> Potential reasons:
>> >>> >> >>>>>>>>>> The slave's hostname, 'centos-2.local', is not
>> accessible
>> >>> >> >>>>>>>>>> from
>> >>> >> >>>>>>>>>> your
>> >>> >> >>>>>>>>>> network The slave's port, '5051', is not accessible
>> from
>> >>> >> >>>>>>>>>> your
>> >>> >> >>>>>>>>>> network"
>> >>> >> >>>>>>>>>>
>> >>> >> >>>>>>>>>>
>> >>> >> >>>>>>>>>> I checked that:
>> >>> >> >>>>>>>>>> slave centos-2.local can be login from any machine in
>> the
>> >>> >> >>>>>>>>>> cluster
>> >>> >> >>>>>>>>>> without
>> >>> >> >>>>>>>>>> password by "ssh centos-2.local ";
>> >>> >> >>>>>>>>>>
>> >>> >> >>>>>>>>>> port 5051 on slave centos-2.local could be connected
>> from
>> >>> >> >>>>>>>>>> master
>> >>> >> >>>>>>>>>> by
>> >>> >> >>>>>>>>>> "telnet centos-2.local 5051"
>> >>> >> >>>>>>>>>>
>> >>> >> >>>>>>>>>> The stdout and stderr are there on each slave's
>> >>> >> >>>>>>>>>> /tmp/mesos/...,
>> >>> >> >>>>>>>>>> but seems mesos UI just could not access it.
>> >>> >> >>>>>>>>>> (and Both master and slaves are on the same network IP
>> >>> >> >>>>>>>>>> ranges).
>> >>> >> >>>>>>>>>> Should I open any port on slaves? Any hint what's the
>> >>> >> >>>>>>>>>> problem
>> >>> >> >>>>>>>>>> here?
>> >>> >> >>>>>>>>>>
>> >>> >> >>>>>>>>>> Cheers,
>> >>> >> >>>>>>>>>> Dan
>> >>> >> >>>>>>>>
>> >>> >> >>>>>>>>
>> >>> >> >>>>>>>
>> >>> >> >>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>
>> >>> >> >>>
>> >>> >> >>
>> >>> >> >
>> >>> >
>> >>> >
>> >>
>> >>
>> >
>>
>
>
Re: Unable to follow "Sandbox" links from Mesos UI.
Posted by Dan Dong <do...@gmail.com>.
Hi, All,
Checked again that when I hover cursor on the stdout/stderr, it points to
links of IP address of the master node, so that's why when clicking on it
nothing will show up. While the "Download" button beside it points
correctly to the IP address of slave node, so I can download them without
problem. Seems a config problem somewhere? A bit lost here.
So seems the "host" in the pailer function is resolved to master instead of
slave node:
14 // Invokes the pailer for the specified host and path using the
15 // specified window_title.
16 function pailer(host, path, window_title) {
17 var url = 'http://' + host + '/files/read.json?path=' + path;
18 var pailer =
19 window.open('/static/pailer.html', url, 'width=580px,
height=700px');
20
21 // Need to use window.onload instead of document.ready to make
22 // sure the title doesn't get overwritten.
23 pailer.onload = function() {
24 pailer.document.title = window_title + ' (' + host + ')';
25 };
26 }
27
Cheers,
Dan
2015-01-27 2:51 GMT-06:00 Alex Rukletsov <al...@mesosphere.io>:
> Dan,
>
> the link to the sandbox on a slave is prepared in the JS. As Geoffroy
> suggests, could you please check that the JS code works correctly and
> the url is constructed normally (see controllers.js:16)? If
> everything's fine on your side, could you please file a JIRA for this
> issue?
>
> On Tue, Jan 27, 2015 at 8:21 AM, Geoffroy Jabouley
> <ge...@gmail.com> wrote:
> > Hello
> >
> > just in case, which internet browser are you using?
> >
> > Do you have installed any extensions (NoScript, Ghostery, ...) that could
> > prevent the display /statis/pailer display?
> >
> > I personnaly use NoScript with Firefox, and i have to turn it off on all
> @IP
> > of our cluster to correctly access slave information from Mesos UI.
> >
> > My 2 cents
> > Regards
> >
> > 2015-01-26 21:08 GMT+01:00 Suijian Zhou <su...@ige-project.eu>:
> >>
> >> Hi, Alex,
> >> Yes, I can see the link points to the slave machine when I hover on
> the
> >> "Download" button and stdout/stderr can be downloaded. So do you mean
> it is
> >> expected/designed that clicking on 'stdout/stderr' themselves will not
> show
> >> you anything? Thanks!
> >>
> >> Cheers,
> >> Dan
> >>
> >>
> >> 2015-01-26 7:44 GMT-06:00 Alex Rukletsov <al...@mesosphere.io>:
> >>>
> >>> Dan,
> >>>
> >>> that's correct. The 'static/pailer.html' is a page that lives on the
> >>> master and it gets a url to the actual slave as a parameter. The url
> >>> is computed in 'controllers.js' based on where the associated executor
> >>> lives. You should see this 'actual' url if you hover over the Download
> >>> button. Please check this url for correctness and that you can access
> >>> it from your browser.
> >>>
> >>> On Fri, Jan 23, 2015 at 9:24 PM, Dan Dong <do...@gmail.com> wrote:
> >>> > I see the problem: when I move the cursor onto the link, e.g: stderr,
> >>> > it
> >>> > actually points to the IP address of the master machine, so it trys
> to
> >>> > follow links of Master_IP:/tmp/mesos/slaves/...
> >>> > which is not there. So why the link does not point to the IP address
> >>> > of
> >>> > slaves( config problems somewhere?)?
> >>> >
> >>> > Cheers,
> >>> > Dan
> >>> >
> >>> >
> >>> > 2015-01-23 11:25 GMT-06:00 Dick Davies <di...@hellooperator.net>:
> >>> >
> >>> >> Start with 'inspect element' in the browser and see if that gives
> any
> >>> >> clues.
> >>> >> Sounds like your network is a little strict so it may be something
> >>> >> else needs opening up.
> >>> >>
> >>> >> On 23 January 2015 at 16:56, Dan Dong <do...@gmail.com> wrote:
> >>> >> > Hi, Alex,
> >>> >> > That is what expected, but when I click on it, it pops a new
> blank
> >>> >> > window(pailer.html) without the content of the file(9KB size). Any
> >>> >> > hints?
> >>> >> >
> >>> >> > Cheers,
> >>> >> > Dan
> >>> >> >
> >>> >> >
> >>> >> > 2015-01-23 4:37 GMT-06:00 Alex Rukletsov <al...@mesosphere.io>:
> >>> >> >
> >>> >> >> Dan,
> >>> >> >>
> >>> >> >> you should be able to view file contents just by clicking on the
> >>> >> >> link.
> >>> >> >>
> >>> >> >> On Thu, Jan 22, 2015 at 9:57 PM, Dan Dong <do...@gmail.com>
> >>> >> >> wrote:
> >>> >> >>>
> >>> >> >>> Yes, --hostname solves the problem. Now I can see all files
> there
> >>> >> >>> like
> >>> >> >>> stdout, stderr etc, but when I click on e.g stdout, it pops a
> new
> >>> >> >>> blank
> >>> >> >>> window(pailer.html) without the content of the file(9KB size).
> >>> >> >>> Although it
> >>> >> >>> provides a "Download" link beside, it would be much more
> >>> >> >>> convenient if
> >>> >> >>> one
> >>> >> >>> can view the stdout and stderr directly. Is this normal or there
> >>> >> >>> is
> >>> >> >>> still
> >>> >> >>> problem on my envs? Thanks!
> >>> >> >>>
> >>> >> >>> Cheers,
> >>> >> >>> Dan
> >>> >> >>>
> >>> >> >>>
> >>> >> >>> 2015-01-22 11:33 GMT-06:00 Adam Bordelon <ad...@mesosphere.io>:
> >>> >> >>>
> >>> >> >>>> Try the --hostname parameters for master/slave. If you want to
> be
> >>> >> >>>> extra
> >>> >> >>>> explicit about the IP (e.g. publish the public IP instead of
> the
> >>> >> >>>> private one
> >>> >> >>>> in a cloud environment), you can also set the --ip parameter on
> >>> >> >>>> master/slave.
> >>> >> >>>>
> >>> >> >>>> On Thu, Jan 22, 2015 at 8:43 AM, Dan Dong <dongdan39@gmail.com
> >
> >>> >> >>>> wrote:
> >>> >> >>>>>
> >>> >> >>>>> Thanks Ryan, yes, from the machine where the browser is on
> slave
> >>> >> >>>>> hostnames could not be resolved, so that's why failure, but it
> >>> >> >>>>> can
> >>> >> >>>>> reach
> >>> >> >>>>> them by IP address( I don't think sys admin would like to add
> >>> >> >>>>> those
> >>> >> >>>>> VMs
> >>> >> >>>>> entries to /etc/hosts on the server). I tried to change
> masters
> >>> >> >>>>> and
> >>> >> >>>>> slaves
> >>> >> >>>>> of mesos to IP addresses instead of hostname but UI still
> points
> >>> >> >>>>> to
> >>> >> >>>>> hostnames of slaves. Is threre a way to let mesos only use IP
> >>> >> >>>>> address of
> >>> >> >>>>> master and slaves?
> >>> >> >>>>>
> >>> >> >>>>> Cheers,
> >>> >> >>>>> Dan
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>>> 2015-01-22 9:48 GMT-06:00 Ryan Thomas <r....@gmail.com>:
> >>> >> >>>>>
> >>> >> >>>>>> It is a request from your browser session, not from the
> master
> >>> >> >>>>>> that
> >>> >> >>>>>> is
> >>> >> >>>>>> going to the slaves - so in order to view the sandbox you
> need
> >>> >> >>>>>> to
> >>> >> >>>>>> ensure
> >>> >> >>>>>> that the machine your browser is on can resolve and route to
> >>> >> >>>>>> the
> >>> >> >>>>>> masters
> >>> >> >>>>>> _and_ the slaves.
> >>> >> >>>>>>
> >>> >> >>>>>> The master doesn't proxy the sandbox requests through itself
> >>> >> >>>>>> (yet)
> >>> >> >>>>>> -
> >>> >> >>>>>> they are made directly from your browser instance to the
> >>> >> >>>>>> slaves.
> >>> >> >>>>>>
> >>> >> >>>>>> Make sure you can resolve the slaves from the machine you're
> >>> >> >>>>>> browsing
> >>> >> >>>>>> the UI on.
> >>> >> >>>>>>
> >>> >> >>>>>> Cheers,
> >>> >> >>>>>>
> >>> >> >>>>>> ryan
> >>> >> >>>>>>
> >>> >> >>>>>> On 22 January 2015 at 15:42, Dan Dong <do...@gmail.com>
> >>> >> >>>>>> wrote:
> >>> >> >>>>>>>
> >>> >> >>>>>>> Thank you all, the master and slaves can resolve each
> others'
> >>> >> >>>>>>> hostname and ssh login without password, firewalls have been
> >>> >> >>>>>>> switched off on
> >>> >> >>>>>>> all the machines too.
> >>> >> >>>>>>> So I'm confused what will block such a pull of info of
> slaves
> >>> >> >>>>>>> from
> >>> >> >>>>>>> UI?
> >>> >> >>>>>>>
> >>> >> >>>>>>> Cheers,
> >>> >> >>>>>>> Dan
> >>> >> >>>>>>>
> >>> >> >>>>>>>
> >>> >> >>>>>>> 2015-01-21 16:35 GMT-06:00 Cody Maloney <cody@mesosphere.io
> >:
> >>> >> >>>>>>>
> >>> >> >>>>>>>> Also see https://issues.apache.org/jira/browse/MESOS-2129
> if
> >>> >> >>>>>>>> you
> >>> >> >>>>>>>> want to track progress on changing this.
> >>> >> >>>>>>>>
> >>> >> >>>>>>>> Unfortunately it is on hold for me at the moment to fix.
> >>> >> >>>>>>>>
> >>> >> >>>>>>>> Cody
> >>> >> >>>>>>>>
> >>> >> >>>>>>>> On Wed, Jan 21, 2015 at 2:07 PM, Ryan Thomas
> >>> >> >>>>>>>> <r....@gmail.com>
> >>> >> >>>>>>>> wrote:
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> Hey Dan,
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> The UI will attempt to pull that info directly from the
> >>> >> >>>>>>>>> slave so
> >>> >> >>>>>>>>> you need to make sure the host is resolvable and
> routeable
> >>> >> >>>>>>>>> from
> >>> >> >>>>>>>>> your
> >>> >> >>>>>>>>> browser.
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> Cheers,
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> Ryan
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> From my phone
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> On Wednesday, 21 January 2015, Dan Dong
> >>> >> >>>>>>>>> <do...@gmail.com>
> >>> >> >>>>>>>>> wrote:
> >>> >> >>>>>>>>>>
> >>> >> >>>>>>>>>> Hi, All,
> >>> >> >>>>>>>>>> When I try to access sandbox on mesos UI, I see the
> >>> >> >>>>>>>>>> following
> >>> >> >>>>>>>>>> info( The
> >>> >> >>>>>>>>>> same error appears on every slave sandbox.):
> >>> >> >>>>>>>>>>
> >>> >> >>>>>>>>>> "Failed to connect to slave
> >>> >> >>>>>>>>>> '20150115-144719-3205108908-5050-4552-S0'
> >>> >> >>>>>>>>>> on 'centos-2.local:5051'.
> >>> >> >>>>>>>>>>
> >>> >> >>>>>>>>>> Potential reasons:
> >>> >> >>>>>>>>>> The slave's hostname, 'centos-2.local', is not
> accessible
> >>> >> >>>>>>>>>> from
> >>> >> >>>>>>>>>> your
> >>> >> >>>>>>>>>> network The slave's port, '5051', is not accessible from
> >>> >> >>>>>>>>>> your
> >>> >> >>>>>>>>>> network"
> >>> >> >>>>>>>>>>
> >>> >> >>>>>>>>>>
> >>> >> >>>>>>>>>> I checked that:
> >>> >> >>>>>>>>>> slave centos-2.local can be login from any machine in
> the
> >>> >> >>>>>>>>>> cluster
> >>> >> >>>>>>>>>> without
> >>> >> >>>>>>>>>> password by "ssh centos-2.local ";
> >>> >> >>>>>>>>>>
> >>> >> >>>>>>>>>> port 5051 on slave centos-2.local could be connected
> from
> >>> >> >>>>>>>>>> master
> >>> >> >>>>>>>>>> by
> >>> >> >>>>>>>>>> "telnet centos-2.local 5051"
> >>> >> >>>>>>>>>>
> >>> >> >>>>>>>>>> The stdout and stderr are there on each slave's
> >>> >> >>>>>>>>>> /tmp/mesos/...,
> >>> >> >>>>>>>>>> but seems mesos UI just could not access it.
> >>> >> >>>>>>>>>> (and Both master and slaves are on the same network IP
> >>> >> >>>>>>>>>> ranges).
> >>> >> >>>>>>>>>> Should I open any port on slaves? Any hint what's the
> >>> >> >>>>>>>>>> problem
> >>> >> >>>>>>>>>> here?
> >>> >> >>>>>>>>>>
> >>> >> >>>>>>>>>> Cheers,
> >>> >> >>>>>>>>>> Dan
> >>> >> >>>>>>>>
> >>> >> >>>>>>>>
> >>> >> >>>>>>>
> >>> >> >>>>>>
> >>> >> >>>>>
> >>> >> >>>>
> >>> >> >>>
> >>> >> >>
> >>> >> >
> >>> >
> >>> >
> >>
> >>
> >
>
Re: Unable to follow "Sandbox" links from Mesos UI.
Posted by Alex Rukletsov <al...@mesosphere.io>.
Dan,
the link to the sandbox on a slave is prepared in the JS. As Geoffroy
suggests, could you please check that the JS code works correctly and
the url is constructed normally (see controllers.js:16)? If
everything's fine on your side, could you please file a JIRA for this
issue?
On Tue, Jan 27, 2015 at 8:21 AM, Geoffroy Jabouley
<ge...@gmail.com> wrote:
> Hello
>
> just in case, which internet browser are you using?
>
> Do you have installed any extensions (NoScript, Ghostery, ...) that could
> prevent the display /statis/pailer display?
>
> I personnaly use NoScript with Firefox, and i have to turn it off on all @IP
> of our cluster to correctly access slave information from Mesos UI.
>
> My 2 cents
> Regards
>
> 2015-01-26 21:08 GMT+01:00 Suijian Zhou <su...@ige-project.eu>:
>>
>> Hi, Alex,
>> Yes, I can see the link points to the slave machine when I hover on the
>> "Download" button and stdout/stderr can be downloaded. So do you mean it is
>> expected/designed that clicking on 'stdout/stderr' themselves will not show
>> you anything? Thanks!
>>
>> Cheers,
>> Dan
>>
>>
>> 2015-01-26 7:44 GMT-06:00 Alex Rukletsov <al...@mesosphere.io>:
>>>
>>> Dan,
>>>
>>> that's correct. The 'static/pailer.html' is a page that lives on the
>>> master and it gets a url to the actual slave as a parameter. The url
>>> is computed in 'controllers.js' based on where the associated executor
>>> lives. You should see this 'actual' url if you hover over the Download
>>> button. Please check this url for correctness and that you can access
>>> it from your browser.
>>>
>>> On Fri, Jan 23, 2015 at 9:24 PM, Dan Dong <do...@gmail.com> wrote:
>>> > I see the problem: when I move the cursor onto the link, e.g: stderr,
>>> > it
>>> > actually points to the IP address of the master machine, so it trys to
>>> > follow links of Master_IP:/tmp/mesos/slaves/...
>>> > which is not there. So why the link does not point to the IP address
>>> > of
>>> > slaves( config problems somewhere?)?
>>> >
>>> > Cheers,
>>> > Dan
>>> >
>>> >
>>> > 2015-01-23 11:25 GMT-06:00 Dick Davies <di...@hellooperator.net>:
>>> >
>>> >> Start with 'inspect element' in the browser and see if that gives any
>>> >> clues.
>>> >> Sounds like your network is a little strict so it may be something
>>> >> else needs opening up.
>>> >>
>>> >> On 23 January 2015 at 16:56, Dan Dong <do...@gmail.com> wrote:
>>> >> > Hi, Alex,
>>> >> > That is what expected, but when I click on it, it pops a new blank
>>> >> > window(pailer.html) without the content of the file(9KB size). Any
>>> >> > hints?
>>> >> >
>>> >> > Cheers,
>>> >> > Dan
>>> >> >
>>> >> >
>>> >> > 2015-01-23 4:37 GMT-06:00 Alex Rukletsov <al...@mesosphere.io>:
>>> >> >
>>> >> >> Dan,
>>> >> >>
>>> >> >> you should be able to view file contents just by clicking on the
>>> >> >> link.
>>> >> >>
>>> >> >> On Thu, Jan 22, 2015 at 9:57 PM, Dan Dong <do...@gmail.com>
>>> >> >> wrote:
>>> >> >>>
>>> >> >>> Yes, --hostname solves the problem. Now I can see all files there
>>> >> >>> like
>>> >> >>> stdout, stderr etc, but when I click on e.g stdout, it pops a new
>>> >> >>> blank
>>> >> >>> window(pailer.html) without the content of the file(9KB size).
>>> >> >>> Although it
>>> >> >>> provides a "Download" link beside, it would be much more
>>> >> >>> convenient if
>>> >> >>> one
>>> >> >>> can view the stdout and stderr directly. Is this normal or there
>>> >> >>> is
>>> >> >>> still
>>> >> >>> problem on my envs? Thanks!
>>> >> >>>
>>> >> >>> Cheers,
>>> >> >>> Dan
>>> >> >>>
>>> >> >>>
>>> >> >>> 2015-01-22 11:33 GMT-06:00 Adam Bordelon <ad...@mesosphere.io>:
>>> >> >>>
>>> >> >>>> Try the --hostname parameters for master/slave. If you want to be
>>> >> >>>> extra
>>> >> >>>> explicit about the IP (e.g. publish the public IP instead of the
>>> >> >>>> private one
>>> >> >>>> in a cloud environment), you can also set the --ip parameter on
>>> >> >>>> master/slave.
>>> >> >>>>
>>> >> >>>> On Thu, Jan 22, 2015 at 8:43 AM, Dan Dong <do...@gmail.com>
>>> >> >>>> wrote:
>>> >> >>>>>
>>> >> >>>>> Thanks Ryan, yes, from the machine where the browser is on slave
>>> >> >>>>> hostnames could not be resolved, so that's why failure, but it
>>> >> >>>>> can
>>> >> >>>>> reach
>>> >> >>>>> them by IP address( I don't think sys admin would like to add
>>> >> >>>>> those
>>> >> >>>>> VMs
>>> >> >>>>> entries to /etc/hosts on the server). I tried to change masters
>>> >> >>>>> and
>>> >> >>>>> slaves
>>> >> >>>>> of mesos to IP addresses instead of hostname but UI still points
>>> >> >>>>> to
>>> >> >>>>> hostnames of slaves. Is threre a way to let mesos only use IP
>>> >> >>>>> address of
>>> >> >>>>> master and slaves?
>>> >> >>>>>
>>> >> >>>>> Cheers,
>>> >> >>>>> Dan
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>> 2015-01-22 9:48 GMT-06:00 Ryan Thomas <r....@gmail.com>:
>>> >> >>>>>
>>> >> >>>>>> It is a request from your browser session, not from the master
>>> >> >>>>>> that
>>> >> >>>>>> is
>>> >> >>>>>> going to the slaves - so in order to view the sandbox you need
>>> >> >>>>>> to
>>> >> >>>>>> ensure
>>> >> >>>>>> that the machine your browser is on can resolve and route to
>>> >> >>>>>> the
>>> >> >>>>>> masters
>>> >> >>>>>> _and_ the slaves.
>>> >> >>>>>>
>>> >> >>>>>> The master doesn't proxy the sandbox requests through itself
>>> >> >>>>>> (yet)
>>> >> >>>>>> -
>>> >> >>>>>> they are made directly from your browser instance to the
>>> >> >>>>>> slaves.
>>> >> >>>>>>
>>> >> >>>>>> Make sure you can resolve the slaves from the machine you're
>>> >> >>>>>> browsing
>>> >> >>>>>> the UI on.
>>> >> >>>>>>
>>> >> >>>>>> Cheers,
>>> >> >>>>>>
>>> >> >>>>>> ryan
>>> >> >>>>>>
>>> >> >>>>>> On 22 January 2015 at 15:42, Dan Dong <do...@gmail.com>
>>> >> >>>>>> wrote:
>>> >> >>>>>>>
>>> >> >>>>>>> Thank you all, the master and slaves can resolve each others'
>>> >> >>>>>>> hostname and ssh login without password, firewalls have been
>>> >> >>>>>>> switched off on
>>> >> >>>>>>> all the machines too.
>>> >> >>>>>>> So I'm confused what will block such a pull of info of slaves
>>> >> >>>>>>> from
>>> >> >>>>>>> UI?
>>> >> >>>>>>>
>>> >> >>>>>>> Cheers,
>>> >> >>>>>>> Dan
>>> >> >>>>>>>
>>> >> >>>>>>>
>>> >> >>>>>>> 2015-01-21 16:35 GMT-06:00 Cody Maloney <co...@mesosphere.io>:
>>> >> >>>>>>>
>>> >> >>>>>>>> Also see https://issues.apache.org/jira/browse/MESOS-2129 if
>>> >> >>>>>>>> you
>>> >> >>>>>>>> want to track progress on changing this.
>>> >> >>>>>>>>
>>> >> >>>>>>>> Unfortunately it is on hold for me at the moment to fix.
>>> >> >>>>>>>>
>>> >> >>>>>>>> Cody
>>> >> >>>>>>>>
>>> >> >>>>>>>> On Wed, Jan 21, 2015 at 2:07 PM, Ryan Thomas
>>> >> >>>>>>>> <r....@gmail.com>
>>> >> >>>>>>>> wrote:
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> Hey Dan,
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> The UI will attempt to pull that info directly from the
>>> >> >>>>>>>>> slave so
>>> >> >>>>>>>>> you need to make sure the host is resolvable and routeable
>>> >> >>>>>>>>> from
>>> >> >>>>>>>>> your
>>> >> >>>>>>>>> browser.
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> Cheers,
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> Ryan
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> From my phone
>>> >> >>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> On Wednesday, 21 January 2015, Dan Dong
>>> >> >>>>>>>>> <do...@gmail.com>
>>> >> >>>>>>>>> wrote:
>>> >> >>>>>>>>>>
>>> >> >>>>>>>>>> Hi, All,
>>> >> >>>>>>>>>> When I try to access sandbox on mesos UI, I see the
>>> >> >>>>>>>>>> following
>>> >> >>>>>>>>>> info( The
>>> >> >>>>>>>>>> same error appears on every slave sandbox.):
>>> >> >>>>>>>>>>
>>> >> >>>>>>>>>> "Failed to connect to slave
>>> >> >>>>>>>>>> '20150115-144719-3205108908-5050-4552-S0'
>>> >> >>>>>>>>>> on 'centos-2.local:5051'.
>>> >> >>>>>>>>>>
>>> >> >>>>>>>>>> Potential reasons:
>>> >> >>>>>>>>>> The slave's hostname, 'centos-2.local', is not accessible
>>> >> >>>>>>>>>> from
>>> >> >>>>>>>>>> your
>>> >> >>>>>>>>>> network The slave's port, '5051', is not accessible from
>>> >> >>>>>>>>>> your
>>> >> >>>>>>>>>> network"
>>> >> >>>>>>>>>>
>>> >> >>>>>>>>>>
>>> >> >>>>>>>>>> I checked that:
>>> >> >>>>>>>>>> slave centos-2.local can be login from any machine in the
>>> >> >>>>>>>>>> cluster
>>> >> >>>>>>>>>> without
>>> >> >>>>>>>>>> password by "ssh centos-2.local ";
>>> >> >>>>>>>>>>
>>> >> >>>>>>>>>> port 5051 on slave centos-2.local could be connected from
>>> >> >>>>>>>>>> master
>>> >> >>>>>>>>>> by
>>> >> >>>>>>>>>> "telnet centos-2.local 5051"
>>> >> >>>>>>>>>>
>>> >> >>>>>>>>>> The stdout and stderr are there on each slave's
>>> >> >>>>>>>>>> /tmp/mesos/...,
>>> >> >>>>>>>>>> but seems mesos UI just could not access it.
>>> >> >>>>>>>>>> (and Both master and slaves are on the same network IP
>>> >> >>>>>>>>>> ranges).
>>> >> >>>>>>>>>> Should I open any port on slaves? Any hint what's the
>>> >> >>>>>>>>>> problem
>>> >> >>>>>>>>>> here?
>>> >> >>>>>>>>>>
>>> >> >>>>>>>>>> Cheers,
>>> >> >>>>>>>>>> Dan
>>> >> >>>>>>>>
>>> >> >>>>>>>>
>>> >> >>>>>>>
>>> >> >>>>>>
>>> >> >>>>>
>>> >> >>>>
>>> >> >>>
>>> >> >>
>>> >> >
>>> >
>>> >
>>
>>
>
Re: Unable to follow "Sandbox" links from Mesos UI.
Posted by Geoffroy Jabouley <ge...@gmail.com>.
Hello
just in case, which internet browser are you using?
Do you have installed any extensions (NoScript, Ghostery, ...) that could
prevent the display /statis/pailer display?
I personnaly use NoScript with Firefox, and i have to turn it off on all
@IP of our cluster to correctly access slave information from Mesos UI.
My 2 cents
Regards
2015-01-26 21:08 GMT+01:00 Suijian Zhou <su...@ige-project.eu>:
> Hi, Alex,
> Yes, I can see the link points to the slave machine when I hover on the
> "Download" button and stdout/stderr can be downloaded. So do you mean it is
> expected/designed that clicking on 'stdout/stderr' themselves will not show
> you anything? Thanks!
>
> Cheers,
> Dan
>
>
> 2015-01-26 7:44 GMT-06:00 Alex Rukletsov <al...@mesosphere.io>:
>
>> Dan,
>>
>> that's correct. The 'static/pailer.html' is a page that lives on the
>> master and it gets a url to the actual slave as a parameter. The url
>> is computed in 'controllers.js' based on where the associated executor
>> lives. You should see this 'actual' url if you hover over the Download
>> button. Please check this url for correctness and that you can access
>> it from your browser.
>>
>> On Fri, Jan 23, 2015 at 9:24 PM, Dan Dong <do...@gmail.com> wrote:
>> > I see the problem: when I move the cursor onto the link, e.g: stderr, it
>> > actually points to the IP address of the master machine, so it trys to
>> > follow links of Master_IP:/tmp/mesos/slaves/...
>> > which is not there. So why the link does not point to the IP address of
>> > slaves( config problems somewhere?)?
>> >
>> > Cheers,
>> > Dan
>> >
>> >
>> > 2015-01-23 11:25 GMT-06:00 Dick Davies <di...@hellooperator.net>:
>> >
>> >> Start with 'inspect element' in the browser and see if that gives any
>> >> clues.
>> >> Sounds like your network is a little strict so it may be something
>> >> else needs opening up.
>> >>
>> >> On 23 January 2015 at 16:56, Dan Dong <do...@gmail.com> wrote:
>> >> > Hi, Alex,
>> >> > That is what expected, but when I click on it, it pops a new blank
>> >> > window(pailer.html) without the content of the file(9KB size). Any
>> >> > hints?
>> >> >
>> >> > Cheers,
>> >> > Dan
>> >> >
>> >> >
>> >> > 2015-01-23 4:37 GMT-06:00 Alex Rukletsov <al...@mesosphere.io>:
>> >> >
>> >> >> Dan,
>> >> >>
>> >> >> you should be able to view file contents just by clicking on the
>> link.
>> >> >>
>> >> >> On Thu, Jan 22, 2015 at 9:57 PM, Dan Dong <do...@gmail.com>
>> wrote:
>> >> >>>
>> >> >>> Yes, --hostname solves the problem. Now I can see all files there
>> like
>> >> >>> stdout, stderr etc, but when I click on e.g stdout, it pops a new
>> >> >>> blank
>> >> >>> window(pailer.html) without the content of the file(9KB size).
>> >> >>> Although it
>> >> >>> provides a "Download" link beside, it would be much more
>> convenient if
>> >> >>> one
>> >> >>> can view the stdout and stderr directly. Is this normal or there is
>> >> >>> still
>> >> >>> problem on my envs? Thanks!
>> >> >>>
>> >> >>> Cheers,
>> >> >>> Dan
>> >> >>>
>> >> >>>
>> >> >>> 2015-01-22 11:33 GMT-06:00 Adam Bordelon <ad...@mesosphere.io>:
>> >> >>>
>> >> >>>> Try the --hostname parameters for master/slave. If you want to be
>> >> >>>> extra
>> >> >>>> explicit about the IP (e.g. publish the public IP instead of the
>> >> >>>> private one
>> >> >>>> in a cloud environment), you can also set the --ip parameter on
>> >> >>>> master/slave.
>> >> >>>>
>> >> >>>> On Thu, Jan 22, 2015 at 8:43 AM, Dan Dong <do...@gmail.com>
>> >> >>>> wrote:
>> >> >>>>>
>> >> >>>>> Thanks Ryan, yes, from the machine where the browser is on slave
>> >> >>>>> hostnames could not be resolved, so that's why failure, but it
>> can
>> >> >>>>> reach
>> >> >>>>> them by IP address( I don't think sys admin would like to add
>> those
>> >> >>>>> VMs
>> >> >>>>> entries to /etc/hosts on the server). I tried to change masters
>> and
>> >> >>>>> slaves
>> >> >>>>> of mesos to IP addresses instead of hostname but UI still points
>> to
>> >> >>>>> hostnames of slaves. Is threre a way to let mesos only use IP
>> >> >>>>> address of
>> >> >>>>> master and slaves?
>> >> >>>>>
>> >> >>>>> Cheers,
>> >> >>>>> Dan
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> 2015-01-22 9:48 GMT-06:00 Ryan Thomas <r....@gmail.com>:
>> >> >>>>>
>> >> >>>>>> It is a request from your browser session, not from the master
>> that
>> >> >>>>>> is
>> >> >>>>>> going to the slaves - so in order to view the sandbox you need
>> to
>> >> >>>>>> ensure
>> >> >>>>>> that the machine your browser is on can resolve and route to the
>> >> >>>>>> masters
>> >> >>>>>> _and_ the slaves.
>> >> >>>>>>
>> >> >>>>>> The master doesn't proxy the sandbox requests through itself
>> (yet)
>> >> >>>>>> -
>> >> >>>>>> they are made directly from your browser instance to the slaves.
>> >> >>>>>>
>> >> >>>>>> Make sure you can resolve the slaves from the machine you're
>> >> >>>>>> browsing
>> >> >>>>>> the UI on.
>> >> >>>>>>
>> >> >>>>>> Cheers,
>> >> >>>>>>
>> >> >>>>>> ryan
>> >> >>>>>>
>> >> >>>>>> On 22 January 2015 at 15:42, Dan Dong <do...@gmail.com>
>> wrote:
>> >> >>>>>>>
>> >> >>>>>>> Thank you all, the master and slaves can resolve each others'
>> >> >>>>>>> hostname and ssh login without password, firewalls have been
>> >> >>>>>>> switched off on
>> >> >>>>>>> all the machines too.
>> >> >>>>>>> So I'm confused what will block such a pull of info of slaves
>> from
>> >> >>>>>>> UI?
>> >> >>>>>>>
>> >> >>>>>>> Cheers,
>> >> >>>>>>> Dan
>> >> >>>>>>>
>> >> >>>>>>>
>> >> >>>>>>> 2015-01-21 16:35 GMT-06:00 Cody Maloney <co...@mesosphere.io>:
>> >> >>>>>>>
>> >> >>>>>>>> Also see https://issues.apache.org/jira/browse/MESOS-2129 if
>> you
>> >> >>>>>>>> want to track progress on changing this.
>> >> >>>>>>>>
>> >> >>>>>>>> Unfortunately it is on hold for me at the moment to fix.
>> >> >>>>>>>>
>> >> >>>>>>>> Cody
>> >> >>>>>>>>
>> >> >>>>>>>> On Wed, Jan 21, 2015 at 2:07 PM, Ryan Thomas
>> >> >>>>>>>> <r....@gmail.com>
>> >> >>>>>>>> wrote:
>> >> >>>>>>>>>
>> >> >>>>>>>>> Hey Dan,
>> >> >>>>>>>>>
>> >> >>>>>>>>> The UI will attempt to pull that info directly from the
>> slave so
>> >> >>>>>>>>> you need to make sure the host is resolvable and routeable
>> from
>> >> >>>>>>>>> your
>> >> >>>>>>>>> browser.
>> >> >>>>>>>>>
>> >> >>>>>>>>> Cheers,
>> >> >>>>>>>>>
>> >> >>>>>>>>> Ryan
>> >> >>>>>>>>>
>> >> >>>>>>>>> From my phone
>> >> >>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>>>>> On Wednesday, 21 January 2015, Dan Dong <dongdan39@gmail.com
>> >
>> >> >>>>>>>>> wrote:
>> >> >>>>>>>>>>
>> >> >>>>>>>>>> Hi, All,
>> >> >>>>>>>>>> When I try to access sandbox on mesos UI, I see the
>> following
>> >> >>>>>>>>>> info( The
>> >> >>>>>>>>>> same error appears on every slave sandbox.):
>> >> >>>>>>>>>>
>> >> >>>>>>>>>> "Failed to connect to slave
>> >> >>>>>>>>>> '20150115-144719-3205108908-5050-4552-S0'
>> >> >>>>>>>>>> on 'centos-2.local:5051'.
>> >> >>>>>>>>>>
>> >> >>>>>>>>>> Potential reasons:
>> >> >>>>>>>>>> The slave's hostname, 'centos-2.local', is not accessible
>> from
>> >> >>>>>>>>>> your
>> >> >>>>>>>>>> network The slave's port, '5051', is not accessible from
>> your
>> >> >>>>>>>>>> network"
>> >> >>>>>>>>>>
>> >> >>>>>>>>>>
>> >> >>>>>>>>>> I checked that:
>> >> >>>>>>>>>> slave centos-2.local can be login from any machine in the
>> >> >>>>>>>>>> cluster
>> >> >>>>>>>>>> without
>> >> >>>>>>>>>> password by "ssh centos-2.local ";
>> >> >>>>>>>>>>
>> >> >>>>>>>>>> port 5051 on slave centos-2.local could be connected from
>> >> >>>>>>>>>> master
>> >> >>>>>>>>>> by
>> >> >>>>>>>>>> "telnet centos-2.local 5051"
>> >> >>>>>>>>>>
>> >> >>>>>>>>>> The stdout and stderr are there on each slave's
>> /tmp/mesos/...,
>> >> >>>>>>>>>> but seems mesos UI just could not access it.
>> >> >>>>>>>>>> (and Both master and slaves are on the same network IP
>> ranges).
>> >> >>>>>>>>>> Should I open any port on slaves? Any hint what's the
>> problem
>> >> >>>>>>>>>> here?
>> >> >>>>>>>>>>
>> >> >>>>>>>>>> Cheers,
>> >> >>>>>>>>>> Dan
>> >> >>>>>>>>
>> >> >>>>>>>>
>> >> >>>>>>>
>> >> >>>>>>
>> >> >>>>>
>> >> >>>>
>> >> >>>
>> >> >>
>> >> >
>> >
>> >
>>
>
>
Re: Unable to follow "Sandbox" links from Mesos UI.
Posted by Suijian Zhou <su...@ige-project.eu>.
Hi, Alex,
Yes, I can see the link points to the slave machine when I hover on the
"Download" button and stdout/stderr can be downloaded. So do you mean it is
expected/designed that clicking on 'stdout/stderr' themselves will not show
you anything? Thanks!
Cheers,
Dan
2015-01-26 7:44 GMT-06:00 Alex Rukletsov <al...@mesosphere.io>:
> Dan,
>
> that's correct. The 'static/pailer.html' is a page that lives on the
> master and it gets a url to the actual slave as a parameter. The url
> is computed in 'controllers.js' based on where the associated executor
> lives. You should see this 'actual' url if you hover over the Download
> button. Please check this url for correctness and that you can access
> it from your browser.
>
> On Fri, Jan 23, 2015 at 9:24 PM, Dan Dong <do...@gmail.com> wrote:
> > I see the problem: when I move the cursor onto the link, e.g: stderr, it
> > actually points to the IP address of the master machine, so it trys to
> > follow links of Master_IP:/tmp/mesos/slaves/...
> > which is not there. So why the link does not point to the IP address of
> > slaves( config problems somewhere?)?
> >
> > Cheers,
> > Dan
> >
> >
> > 2015-01-23 11:25 GMT-06:00 Dick Davies <di...@hellooperator.net>:
> >
> >> Start with 'inspect element' in the browser and see if that gives any
> >> clues.
> >> Sounds like your network is a little strict so it may be something
> >> else needs opening up.
> >>
> >> On 23 January 2015 at 16:56, Dan Dong <do...@gmail.com> wrote:
> >> > Hi, Alex,
> >> > That is what expected, but when I click on it, it pops a new blank
> >> > window(pailer.html) without the content of the file(9KB size). Any
> >> > hints?
> >> >
> >> > Cheers,
> >> > Dan
> >> >
> >> >
> >> > 2015-01-23 4:37 GMT-06:00 Alex Rukletsov <al...@mesosphere.io>:
> >> >
> >> >> Dan,
> >> >>
> >> >> you should be able to view file contents just by clicking on the
> link.
> >> >>
> >> >> On Thu, Jan 22, 2015 at 9:57 PM, Dan Dong <do...@gmail.com>
> wrote:
> >> >>>
> >> >>> Yes, --hostname solves the problem. Now I can see all files there
> like
> >> >>> stdout, stderr etc, but when I click on e.g stdout, it pops a new
> >> >>> blank
> >> >>> window(pailer.html) without the content of the file(9KB size).
> >> >>> Although it
> >> >>> provides a "Download" link beside, it would be much more convenient
> if
> >> >>> one
> >> >>> can view the stdout and stderr directly. Is this normal or there is
> >> >>> still
> >> >>> problem on my envs? Thanks!
> >> >>>
> >> >>> Cheers,
> >> >>> Dan
> >> >>>
> >> >>>
> >> >>> 2015-01-22 11:33 GMT-06:00 Adam Bordelon <ad...@mesosphere.io>:
> >> >>>
> >> >>>> Try the --hostname parameters for master/slave. If you want to be
> >> >>>> extra
> >> >>>> explicit about the IP (e.g. publish the public IP instead of the
> >> >>>> private one
> >> >>>> in a cloud environment), you can also set the --ip parameter on
> >> >>>> master/slave.
> >> >>>>
> >> >>>> On Thu, Jan 22, 2015 at 8:43 AM, Dan Dong <do...@gmail.com>
> >> >>>> wrote:
> >> >>>>>
> >> >>>>> Thanks Ryan, yes, from the machine where the browser is on slave
> >> >>>>> hostnames could not be resolved, so that's why failure, but it can
> >> >>>>> reach
> >> >>>>> them by IP address( I don't think sys admin would like to add
> those
> >> >>>>> VMs
> >> >>>>> entries to /etc/hosts on the server). I tried to change masters
> and
> >> >>>>> slaves
> >> >>>>> of mesos to IP addresses instead of hostname but UI still points
> to
> >> >>>>> hostnames of slaves. Is threre a way to let mesos only use IP
> >> >>>>> address of
> >> >>>>> master and slaves?
> >> >>>>>
> >> >>>>> Cheers,
> >> >>>>> Dan
> >> >>>>>
> >> >>>>>
> >> >>>>> 2015-01-22 9:48 GMT-06:00 Ryan Thomas <r....@gmail.com>:
> >> >>>>>
> >> >>>>>> It is a request from your browser session, not from the master
> that
> >> >>>>>> is
> >> >>>>>> going to the slaves - so in order to view the sandbox you need to
> >> >>>>>> ensure
> >> >>>>>> that the machine your browser is on can resolve and route to the
> >> >>>>>> masters
> >> >>>>>> _and_ the slaves.
> >> >>>>>>
> >> >>>>>> The master doesn't proxy the sandbox requests through itself
> (yet)
> >> >>>>>> -
> >> >>>>>> they are made directly from your browser instance to the slaves.
> >> >>>>>>
> >> >>>>>> Make sure you can resolve the slaves from the machine you're
> >> >>>>>> browsing
> >> >>>>>> the UI on.
> >> >>>>>>
> >> >>>>>> Cheers,
> >> >>>>>>
> >> >>>>>> ryan
> >> >>>>>>
> >> >>>>>> On 22 January 2015 at 15:42, Dan Dong <do...@gmail.com>
> wrote:
> >> >>>>>>>
> >> >>>>>>> Thank you all, the master and slaves can resolve each others'
> >> >>>>>>> hostname and ssh login without password, firewalls have been
> >> >>>>>>> switched off on
> >> >>>>>>> all the machines too.
> >> >>>>>>> So I'm confused what will block such a pull of info of slaves
> from
> >> >>>>>>> UI?
> >> >>>>>>>
> >> >>>>>>> Cheers,
> >> >>>>>>> Dan
> >> >>>>>>>
> >> >>>>>>>
> >> >>>>>>> 2015-01-21 16:35 GMT-06:00 Cody Maloney <co...@mesosphere.io>:
> >> >>>>>>>
> >> >>>>>>>> Also see https://issues.apache.org/jira/browse/MESOS-2129 if
> you
> >> >>>>>>>> want to track progress on changing this.
> >> >>>>>>>>
> >> >>>>>>>> Unfortunately it is on hold for me at the moment to fix.
> >> >>>>>>>>
> >> >>>>>>>> Cody
> >> >>>>>>>>
> >> >>>>>>>> On Wed, Jan 21, 2015 at 2:07 PM, Ryan Thomas
> >> >>>>>>>> <r....@gmail.com>
> >> >>>>>>>> wrote:
> >> >>>>>>>>>
> >> >>>>>>>>> Hey Dan,
> >> >>>>>>>>>
> >> >>>>>>>>> The UI will attempt to pull that info directly from the slave
> so
> >> >>>>>>>>> you need to make sure the host is resolvable and routeable
> from
> >> >>>>>>>>> your
> >> >>>>>>>>> browser.
> >> >>>>>>>>>
> >> >>>>>>>>> Cheers,
> >> >>>>>>>>>
> >> >>>>>>>>> Ryan
> >> >>>>>>>>>
> >> >>>>>>>>> From my phone
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>> On Wednesday, 21 January 2015, Dan Dong <do...@gmail.com>
> >> >>>>>>>>> wrote:
> >> >>>>>>>>>>
> >> >>>>>>>>>> Hi, All,
> >> >>>>>>>>>> When I try to access sandbox on mesos UI, I see the
> following
> >> >>>>>>>>>> info( The
> >> >>>>>>>>>> same error appears on every slave sandbox.):
> >> >>>>>>>>>>
> >> >>>>>>>>>> "Failed to connect to slave
> >> >>>>>>>>>> '20150115-144719-3205108908-5050-4552-S0'
> >> >>>>>>>>>> on 'centos-2.local:5051'.
> >> >>>>>>>>>>
> >> >>>>>>>>>> Potential reasons:
> >> >>>>>>>>>> The slave's hostname, 'centos-2.local', is not accessible
> from
> >> >>>>>>>>>> your
> >> >>>>>>>>>> network The slave's port, '5051', is not accessible from
> your
> >> >>>>>>>>>> network"
> >> >>>>>>>>>>
> >> >>>>>>>>>>
> >> >>>>>>>>>> I checked that:
> >> >>>>>>>>>> slave centos-2.local can be login from any machine in the
> >> >>>>>>>>>> cluster
> >> >>>>>>>>>> without
> >> >>>>>>>>>> password by "ssh centos-2.local ";
> >> >>>>>>>>>>
> >> >>>>>>>>>> port 5051 on slave centos-2.local could be connected from
> >> >>>>>>>>>> master
> >> >>>>>>>>>> by
> >> >>>>>>>>>> "telnet centos-2.local 5051"
> >> >>>>>>>>>>
> >> >>>>>>>>>> The stdout and stderr are there on each slave's
> /tmp/mesos/...,
> >> >>>>>>>>>> but seems mesos UI just could not access it.
> >> >>>>>>>>>> (and Both master and slaves are on the same network IP
> ranges).
> >> >>>>>>>>>> Should I open any port on slaves? Any hint what's the problem
> >> >>>>>>>>>> here?
> >> >>>>>>>>>>
> >> >>>>>>>>>> Cheers,
> >> >>>>>>>>>> Dan
> >> >>>>>>>>
> >> >>>>>>>>
> >> >>>>>>>
> >> >>>>>>
> >> >>>>>
> >> >>>>
> >> >>>
> >> >>
> >> >
> >
> >
>
Re: Unable to follow "Sandbox" links from Mesos UI.
Posted by Alex Rukletsov <al...@mesosphere.io>.
Dan,
that's correct. The 'static/pailer.html' is a page that lives on the
master and it gets a url to the actual slave as a parameter. The url
is computed in 'controllers.js' based on where the associated executor
lives. You should see this 'actual' url if you hover over the Download
button. Please check this url for correctness and that you can access
it from your browser.
On Fri, Jan 23, 2015 at 9:24 PM, Dan Dong <do...@gmail.com> wrote:
> I see the problem: when I move the cursor onto the link, e.g: stderr, it
> actually points to the IP address of the master machine, so it trys to
> follow links of Master_IP:/tmp/mesos/slaves/...
> which is not there. So why the link does not point to the IP address of
> slaves( config problems somewhere?)?
>
> Cheers,
> Dan
>
>
> 2015-01-23 11:25 GMT-06:00 Dick Davies <di...@hellooperator.net>:
>
>> Start with 'inspect element' in the browser and see if that gives any
>> clues.
>> Sounds like your network is a little strict so it may be something
>> else needs opening up.
>>
>> On 23 January 2015 at 16:56, Dan Dong <do...@gmail.com> wrote:
>> > Hi, Alex,
>> > That is what expected, but when I click on it, it pops a new blank
>> > window(pailer.html) without the content of the file(9KB size). Any
>> > hints?
>> >
>> > Cheers,
>> > Dan
>> >
>> >
>> > 2015-01-23 4:37 GMT-06:00 Alex Rukletsov <al...@mesosphere.io>:
>> >
>> >> Dan,
>> >>
>> >> you should be able to view file contents just by clicking on the link.
>> >>
>> >> On Thu, Jan 22, 2015 at 9:57 PM, Dan Dong <do...@gmail.com> wrote:
>> >>>
>> >>> Yes, --hostname solves the problem. Now I can see all files there like
>> >>> stdout, stderr etc, but when I click on e.g stdout, it pops a new
>> >>> blank
>> >>> window(pailer.html) without the content of the file(9KB size).
>> >>> Although it
>> >>> provides a "Download" link beside, it would be much more convenient if
>> >>> one
>> >>> can view the stdout and stderr directly. Is this normal or there is
>> >>> still
>> >>> problem on my envs? Thanks!
>> >>>
>> >>> Cheers,
>> >>> Dan
>> >>>
>> >>>
>> >>> 2015-01-22 11:33 GMT-06:00 Adam Bordelon <ad...@mesosphere.io>:
>> >>>
>> >>>> Try the --hostname parameters for master/slave. If you want to be
>> >>>> extra
>> >>>> explicit about the IP (e.g. publish the public IP instead of the
>> >>>> private one
>> >>>> in a cloud environment), you can also set the --ip parameter on
>> >>>> master/slave.
>> >>>>
>> >>>> On Thu, Jan 22, 2015 at 8:43 AM, Dan Dong <do...@gmail.com>
>> >>>> wrote:
>> >>>>>
>> >>>>> Thanks Ryan, yes, from the machine where the browser is on slave
>> >>>>> hostnames could not be resolved, so that's why failure, but it can
>> >>>>> reach
>> >>>>> them by IP address( I don't think sys admin would like to add those
>> >>>>> VMs
>> >>>>> entries to /etc/hosts on the server). I tried to change masters and
>> >>>>> slaves
>> >>>>> of mesos to IP addresses instead of hostname but UI still points to
>> >>>>> hostnames of slaves. Is threre a way to let mesos only use IP
>> >>>>> address of
>> >>>>> master and slaves?
>> >>>>>
>> >>>>> Cheers,
>> >>>>> Dan
>> >>>>>
>> >>>>>
>> >>>>> 2015-01-22 9:48 GMT-06:00 Ryan Thomas <r....@gmail.com>:
>> >>>>>
>> >>>>>> It is a request from your browser session, not from the master that
>> >>>>>> is
>> >>>>>> going to the slaves - so in order to view the sandbox you need to
>> >>>>>> ensure
>> >>>>>> that the machine your browser is on can resolve and route to the
>> >>>>>> masters
>> >>>>>> _and_ the slaves.
>> >>>>>>
>> >>>>>> The master doesn't proxy the sandbox requests through itself (yet)
>> >>>>>> -
>> >>>>>> they are made directly from your browser instance to the slaves.
>> >>>>>>
>> >>>>>> Make sure you can resolve the slaves from the machine you're
>> >>>>>> browsing
>> >>>>>> the UI on.
>> >>>>>>
>> >>>>>> Cheers,
>> >>>>>>
>> >>>>>> ryan
>> >>>>>>
>> >>>>>> On 22 January 2015 at 15:42, Dan Dong <do...@gmail.com> wrote:
>> >>>>>>>
>> >>>>>>> Thank you all, the master and slaves can resolve each others'
>> >>>>>>> hostname and ssh login without password, firewalls have been
>> >>>>>>> switched off on
>> >>>>>>> all the machines too.
>> >>>>>>> So I'm confused what will block such a pull of info of slaves from
>> >>>>>>> UI?
>> >>>>>>>
>> >>>>>>> Cheers,
>> >>>>>>> Dan
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> 2015-01-21 16:35 GMT-06:00 Cody Maloney <co...@mesosphere.io>:
>> >>>>>>>
>> >>>>>>>> Also see https://issues.apache.org/jira/browse/MESOS-2129 if you
>> >>>>>>>> want to track progress on changing this.
>> >>>>>>>>
>> >>>>>>>> Unfortunately it is on hold for me at the moment to fix.
>> >>>>>>>>
>> >>>>>>>> Cody
>> >>>>>>>>
>> >>>>>>>> On Wed, Jan 21, 2015 at 2:07 PM, Ryan Thomas
>> >>>>>>>> <r....@gmail.com>
>> >>>>>>>> wrote:
>> >>>>>>>>>
>> >>>>>>>>> Hey Dan,
>> >>>>>>>>>
>> >>>>>>>>> The UI will attempt to pull that info directly from the slave so
>> >>>>>>>>> you need to make sure the host is resolvable and routeable from
>> >>>>>>>>> your
>> >>>>>>>>> browser.
>> >>>>>>>>>
>> >>>>>>>>> Cheers,
>> >>>>>>>>>
>> >>>>>>>>> Ryan
>> >>>>>>>>>
>> >>>>>>>>> From my phone
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> On Wednesday, 21 January 2015, Dan Dong <do...@gmail.com>
>> >>>>>>>>> wrote:
>> >>>>>>>>>>
>> >>>>>>>>>> Hi, All,
>> >>>>>>>>>> When I try to access sandbox on mesos UI, I see the following
>> >>>>>>>>>> info( The
>> >>>>>>>>>> same error appears on every slave sandbox.):
>> >>>>>>>>>>
>> >>>>>>>>>> "Failed to connect to slave
>> >>>>>>>>>> '20150115-144719-3205108908-5050-4552-S0'
>> >>>>>>>>>> on 'centos-2.local:5051'.
>> >>>>>>>>>>
>> >>>>>>>>>> Potential reasons:
>> >>>>>>>>>> The slave's hostname, 'centos-2.local', is not accessible from
>> >>>>>>>>>> your
>> >>>>>>>>>> network The slave's port, '5051', is not accessible from your
>> >>>>>>>>>> network"
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>> I checked that:
>> >>>>>>>>>> slave centos-2.local can be login from any machine in the
>> >>>>>>>>>> cluster
>> >>>>>>>>>> without
>> >>>>>>>>>> password by "ssh centos-2.local ";
>> >>>>>>>>>>
>> >>>>>>>>>> port 5051 on slave centos-2.local could be connected from
>> >>>>>>>>>> master
>> >>>>>>>>>> by
>> >>>>>>>>>> "telnet centos-2.local 5051"
>> >>>>>>>>>>
>> >>>>>>>>>> The stdout and stderr are there on each slave's /tmp/mesos/...,
>> >>>>>>>>>> but seems mesos UI just could not access it.
>> >>>>>>>>>> (and Both master and slaves are on the same network IP ranges).
>> >>>>>>>>>> Should I open any port on slaves? Any hint what's the problem
>> >>>>>>>>>> here?
>> >>>>>>>>>>
>> >>>>>>>>>> Cheers,
>> >>>>>>>>>> Dan
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>
>> >>>>
>> >>>
>> >>
>> >
>
>
Re: Unable to follow "Sandbox" links from Mesos UI.
Posted by Dan Dong <do...@gmail.com>.
I see the problem: when I move the cursor onto the link, e.g: stderr, it
actually points to the IP address of the master machine, so it trys to
follow links of Master_IP:/tmp/mesos/slaves/...
which is not there. So why the link does not point to the IP address of
slaves( config problems somewhere?)?
Cheers,
Dan
2015-01-23 11:25 GMT-06:00 Dick Davies <di...@hellooperator.net>:
> Start with 'inspect element' in the browser and see if that gives any
> clues.
> Sounds like your network is a little strict so it may be something
> else needs opening up.
>
> On 23 January 2015 at 16:56, Dan Dong <do...@gmail.com> wrote:
> > Hi, Alex,
> > That is what expected, but when I click on it, it pops a new blank
> > window(pailer.html) without the content of the file(9KB size). Any hints?
> >
> > Cheers,
> > Dan
> >
> >
> > 2015-01-23 4:37 GMT-06:00 Alex Rukletsov <al...@mesosphere.io>:
> >
> >> Dan,
> >>
> >> you should be able to view file contents just by clicking on the link.
> >>
> >> On Thu, Jan 22, 2015 at 9:57 PM, Dan Dong <do...@gmail.com> wrote:
> >>>
> >>> Yes, --hostname solves the problem. Now I can see all files there like
> >>> stdout, stderr etc, but when I click on e.g stdout, it pops a new blank
> >>> window(pailer.html) without the content of the file(9KB size).
> Although it
> >>> provides a "Download" link beside, it would be much more convenient if
> one
> >>> can view the stdout and stderr directly. Is this normal or there is
> still
> >>> problem on my envs? Thanks!
> >>>
> >>> Cheers,
> >>> Dan
> >>>
> >>>
> >>> 2015-01-22 11:33 GMT-06:00 Adam Bordelon <ad...@mesosphere.io>:
> >>>
> >>>> Try the --hostname parameters for master/slave. If you want to be
> extra
> >>>> explicit about the IP (e.g. publish the public IP instead of the
> private one
> >>>> in a cloud environment), you can also set the --ip parameter on
> >>>> master/slave.
> >>>>
> >>>> On Thu, Jan 22, 2015 at 8:43 AM, Dan Dong <do...@gmail.com>
> wrote:
> >>>>>
> >>>>> Thanks Ryan, yes, from the machine where the browser is on slave
> >>>>> hostnames could not be resolved, so that's why failure, but it can
> reach
> >>>>> them by IP address( I don't think sys admin would like to add those
> VMs
> >>>>> entries to /etc/hosts on the server). I tried to change masters and
> slaves
> >>>>> of mesos to IP addresses instead of hostname but UI still points to
> >>>>> hostnames of slaves. Is threre a way to let mesos only use IP
> address of
> >>>>> master and slaves?
> >>>>>
> >>>>> Cheers,
> >>>>> Dan
> >>>>>
> >>>>>
> >>>>> 2015-01-22 9:48 GMT-06:00 Ryan Thomas <r....@gmail.com>:
> >>>>>
> >>>>>> It is a request from your browser session, not from the master that
> is
> >>>>>> going to the slaves - so in order to view the sandbox you need to
> ensure
> >>>>>> that the machine your browser is on can resolve and route to the
> masters
> >>>>>> _and_ the slaves.
> >>>>>>
> >>>>>> The master doesn't proxy the sandbox requests through itself (yet) -
> >>>>>> they are made directly from your browser instance to the slaves.
> >>>>>>
> >>>>>> Make sure you can resolve the slaves from the machine you're
> browsing
> >>>>>> the UI on.
> >>>>>>
> >>>>>> Cheers,
> >>>>>>
> >>>>>> ryan
> >>>>>>
> >>>>>> On 22 January 2015 at 15:42, Dan Dong <do...@gmail.com> wrote:
> >>>>>>>
> >>>>>>> Thank you all, the master and slaves can resolve each others'
> >>>>>>> hostname and ssh login without password, firewalls have been
> switched off on
> >>>>>>> all the machines too.
> >>>>>>> So I'm confused what will block such a pull of info of slaves from
> >>>>>>> UI?
> >>>>>>>
> >>>>>>> Cheers,
> >>>>>>> Dan
> >>>>>>>
> >>>>>>>
> >>>>>>> 2015-01-21 16:35 GMT-06:00 Cody Maloney <co...@mesosphere.io>:
> >>>>>>>
> >>>>>>>> Also see https://issues.apache.org/jira/browse/MESOS-2129 if you
> >>>>>>>> want to track progress on changing this.
> >>>>>>>>
> >>>>>>>> Unfortunately it is on hold for me at the moment to fix.
> >>>>>>>>
> >>>>>>>> Cody
> >>>>>>>>
> >>>>>>>> On Wed, Jan 21, 2015 at 2:07 PM, Ryan Thomas <
> r.n.thomas@gmail.com>
> >>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>> Hey Dan,
> >>>>>>>>>
> >>>>>>>>> The UI will attempt to pull that info directly from the slave so
> >>>>>>>>> you need to make sure the host is resolvable and routeable from
> your
> >>>>>>>>> browser.
> >>>>>>>>>
> >>>>>>>>> Cheers,
> >>>>>>>>>
> >>>>>>>>> Ryan
> >>>>>>>>>
> >>>>>>>>> From my phone
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On Wednesday, 21 January 2015, Dan Dong <do...@gmail.com>
> >>>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>> Hi, All,
> >>>>>>>>>> When I try to access sandbox on mesos UI, I see the following
> >>>>>>>>>> info( The
> >>>>>>>>>> same error appears on every slave sandbox.):
> >>>>>>>>>>
> >>>>>>>>>> "Failed to connect to slave
> >>>>>>>>>> '20150115-144719-3205108908-5050-4552-S0'
> >>>>>>>>>> on 'centos-2.local:5051'.
> >>>>>>>>>>
> >>>>>>>>>> Potential reasons:
> >>>>>>>>>> The slave's hostname, 'centos-2.local', is not accessible from
> >>>>>>>>>> your
> >>>>>>>>>> network The slave's port, '5051', is not accessible from your
> >>>>>>>>>> network"
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> I checked that:
> >>>>>>>>>> slave centos-2.local can be login from any machine in the
> cluster
> >>>>>>>>>> without
> >>>>>>>>>> password by "ssh centos-2.local ";
> >>>>>>>>>>
> >>>>>>>>>> port 5051 on slave centos-2.local could be connected from
> master
> >>>>>>>>>> by
> >>>>>>>>>> "telnet centos-2.local 5051"
> >>>>>>>>>>
> >>>>>>>>>> The stdout and stderr are there on each slave's /tmp/mesos/...,
> >>>>>>>>>> but seems mesos UI just could not access it.
> >>>>>>>>>> (and Both master and slaves are on the same network IP ranges).
> >>>>>>>>>> Should I open any port on slaves? Any hint what's the problem
> here?
> >>>>>>>>>>
> >>>>>>>>>> Cheers,
> >>>>>>>>>> Dan
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >
>
Re: Unable to follow "Sandbox" links from Mesos UI.
Posted by Dick Davies <di...@hellooperator.net>.
Start with 'inspect element' in the browser and see if that gives any clues.
Sounds like your network is a little strict so it may be something
else needs opening up.
On 23 January 2015 at 16:56, Dan Dong <do...@gmail.com> wrote:
> Hi, Alex,
> That is what expected, but when I click on it, it pops a new blank
> window(pailer.html) without the content of the file(9KB size). Any hints?
>
> Cheers,
> Dan
>
>
> 2015-01-23 4:37 GMT-06:00 Alex Rukletsov <al...@mesosphere.io>:
>
>> Dan,
>>
>> you should be able to view file contents just by clicking on the link.
>>
>> On Thu, Jan 22, 2015 at 9:57 PM, Dan Dong <do...@gmail.com> wrote:
>>>
>>> Yes, --hostname solves the problem. Now I can see all files there like
>>> stdout, stderr etc, but when I click on e.g stdout, it pops a new blank
>>> window(pailer.html) without the content of the file(9KB size). Although it
>>> provides a "Download" link beside, it would be much more convenient if one
>>> can view the stdout and stderr directly. Is this normal or there is still
>>> problem on my envs? Thanks!
>>>
>>> Cheers,
>>> Dan
>>>
>>>
>>> 2015-01-22 11:33 GMT-06:00 Adam Bordelon <ad...@mesosphere.io>:
>>>
>>>> Try the --hostname parameters for master/slave. If you want to be extra
>>>> explicit about the IP (e.g. publish the public IP instead of the private one
>>>> in a cloud environment), you can also set the --ip parameter on
>>>> master/slave.
>>>>
>>>> On Thu, Jan 22, 2015 at 8:43 AM, Dan Dong <do...@gmail.com> wrote:
>>>>>
>>>>> Thanks Ryan, yes, from the machine where the browser is on slave
>>>>> hostnames could not be resolved, so that's why failure, but it can reach
>>>>> them by IP address( I don't think sys admin would like to add those VMs
>>>>> entries to /etc/hosts on the server). I tried to change masters and slaves
>>>>> of mesos to IP addresses instead of hostname but UI still points to
>>>>> hostnames of slaves. Is threre a way to let mesos only use IP address of
>>>>> master and slaves?
>>>>>
>>>>> Cheers,
>>>>> Dan
>>>>>
>>>>>
>>>>> 2015-01-22 9:48 GMT-06:00 Ryan Thomas <r....@gmail.com>:
>>>>>
>>>>>> It is a request from your browser session, not from the master that is
>>>>>> going to the slaves - so in order to view the sandbox you need to ensure
>>>>>> that the machine your browser is on can resolve and route to the masters
>>>>>> _and_ the slaves.
>>>>>>
>>>>>> The master doesn't proxy the sandbox requests through itself (yet) -
>>>>>> they are made directly from your browser instance to the slaves.
>>>>>>
>>>>>> Make sure you can resolve the slaves from the machine you're browsing
>>>>>> the UI on.
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> ryan
>>>>>>
>>>>>> On 22 January 2015 at 15:42, Dan Dong <do...@gmail.com> wrote:
>>>>>>>
>>>>>>> Thank you all, the master and slaves can resolve each others'
>>>>>>> hostname and ssh login without password, firewalls have been switched off on
>>>>>>> all the machines too.
>>>>>>> So I'm confused what will block such a pull of info of slaves from
>>>>>>> UI?
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Dan
>>>>>>>
>>>>>>>
>>>>>>> 2015-01-21 16:35 GMT-06:00 Cody Maloney <co...@mesosphere.io>:
>>>>>>>
>>>>>>>> Also see https://issues.apache.org/jira/browse/MESOS-2129 if you
>>>>>>>> want to track progress on changing this.
>>>>>>>>
>>>>>>>> Unfortunately it is on hold for me at the moment to fix.
>>>>>>>>
>>>>>>>> Cody
>>>>>>>>
>>>>>>>> On Wed, Jan 21, 2015 at 2:07 PM, Ryan Thomas <r....@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Hey Dan,
>>>>>>>>>
>>>>>>>>> The UI will attempt to pull that info directly from the slave so
>>>>>>>>> you need to make sure the host is resolvable and routeable from your
>>>>>>>>> browser.
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>>
>>>>>>>>> Ryan
>>>>>>>>>
>>>>>>>>> From my phone
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wednesday, 21 January 2015, Dan Dong <do...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi, All,
>>>>>>>>>> When I try to access sandbox on mesos UI, I see the following
>>>>>>>>>> info( The
>>>>>>>>>> same error appears on every slave sandbox.):
>>>>>>>>>>
>>>>>>>>>> "Failed to connect to slave
>>>>>>>>>> '20150115-144719-3205108908-5050-4552-S0'
>>>>>>>>>> on 'centos-2.local:5051'.
>>>>>>>>>>
>>>>>>>>>> Potential reasons:
>>>>>>>>>> The slave's hostname, 'centos-2.local', is not accessible from
>>>>>>>>>> your
>>>>>>>>>> network The slave's port, '5051', is not accessible from your
>>>>>>>>>> network"
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I checked that:
>>>>>>>>>> slave centos-2.local can be login from any machine in the cluster
>>>>>>>>>> without
>>>>>>>>>> password by "ssh centos-2.local ";
>>>>>>>>>>
>>>>>>>>>> port 5051 on slave centos-2.local could be connected from master
>>>>>>>>>> by
>>>>>>>>>> "telnet centos-2.local 5051"
>>>>>>>>>>
>>>>>>>>>> The stdout and stderr are there on each slave's /tmp/mesos/...,
>>>>>>>>>> but seems mesos UI just could not access it.
>>>>>>>>>> (and Both master and slaves are on the same network IP ranges).
>>>>>>>>>> Should I open any port on slaves? Any hint what's the problem here?
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>> Dan
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Unable to follow "Sandbox" links from Mesos UI.
Posted by Dan Dong <do...@gmail.com>.
Hi, Alex,
That is what expected, but when I click on it, it pops a new blank
window(pailer.html) without the content of the file(9KB size). Any hints?
Cheers,
Dan
2015-01-23 4:37 GMT-06:00 Alex Rukletsov <al...@mesosphere.io>:
> Dan,
>
> you should be able to view file contents just by clicking on the link.
>
> On Thu, Jan 22, 2015 at 9:57 PM, Dan Dong <do...@gmail.com> wrote:
>
>> Yes, --hostname solves the problem. Now I can see all files there like
>> stdout, stderr etc, but when I click on e.g stdout, it pops a new blank
>> window(pailer.html) without the content of the file(9KB size). Although it
>> provides a "Download" link beside, it would be much more convenient if one
>> can view the stdout and stderr directly. Is this normal or there is still
>> problem on my envs? Thanks!
>>
>> Cheers,
>> Dan
>>
>>
>> 2015-01-22 11:33 GMT-06:00 Adam Bordelon <ad...@mesosphere.io>:
>>
>> Try the --hostname parameters for master/slave. If you want to be extra
>>> explicit about the IP (e.g. publish the public IP instead of the private
>>> one in a cloud environment), you can also set the --ip parameter on
>>> master/slave.
>>>
>>> On Thu, Jan 22, 2015 at 8:43 AM, Dan Dong <do...@gmail.com> wrote:
>>>
>>>> Thanks Ryan, yes, from the machine where the browser is on slave
>>>> hostnames could not be resolved, so that's why failure, but it can reach
>>>> them by IP address( I don't think sys admin would like to add those VMs
>>>> entries to /etc/hosts on the server). I tried to change masters and slaves
>>>> of mesos to IP addresses instead of hostname but UI still points to
>>>> hostnames of slaves. Is threre a way to let mesos only use IP address of
>>>> master and slaves?
>>>>
>>>> Cheers,
>>>> Dan
>>>>
>>>>
>>>> 2015-01-22 9:48 GMT-06:00 Ryan Thomas <r....@gmail.com>:
>>>>
>>>> It is a request from your browser session, not from the master that is
>>>>> going to the slaves - so in order to view the sandbox you need to ensure
>>>>> that the machine your browser is on can resolve and route to the masters
>>>>> _and_ the slaves.
>>>>>
>>>>> The master doesn't proxy the sandbox requests through itself (yet) -
>>>>> they are made directly from your browser instance to the slaves.
>>>>>
>>>>> Make sure you can resolve the slaves from the machine you're browsing
>>>>> the UI on.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> ryan
>>>>>
>>>>> On 22 January 2015 at 15:42, Dan Dong <do...@gmail.com> wrote:
>>>>>
>>>>>> Thank you all, the master and slaves can resolve each others'
>>>>>> hostname and ssh login without password, firewalls have been switched off
>>>>>> on all the machines too.
>>>>>> So I'm confused what will block such a pull of info of slaves from
>>>>>> UI?
>>>>>>
>>>>>> Cheers,
>>>>>> Dan
>>>>>>
>>>>>>
>>>>>> 2015-01-21 16:35 GMT-06:00 Cody Maloney <co...@mesosphere.io>:
>>>>>>
>>>>>> Also see https://issues.apache.org/jira/browse/MESOS-2129 if you
>>>>>>> want to track progress on changing this.
>>>>>>>
>>>>>>> Unfortunately it is on hold for me at the moment to fix.
>>>>>>>
>>>>>>> Cody
>>>>>>>
>>>>>>> On Wed, Jan 21, 2015 at 2:07 PM, Ryan Thomas <r....@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hey Dan,
>>>>>>>>
>>>>>>>> The UI will attempt to pull that info directly from the slave so
>>>>>>>> you need to make sure the host is resolvable and routeable from your
>>>>>>>> browser.
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>>
>>>>>>>> Ryan
>>>>>>>>
>>>>>>>> From my phone
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wednesday, 21 January 2015, Dan Dong <do...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi, All,
>>>>>>>>> When I try to access sandbox on mesos UI, I see the following info( The
>>>>>>>>> same error appears on every slave sandbox.):
>>>>>>>>>
>>>>>>>>> "Failed to connect to slave '20150115-144719-3205108908-5050-4552-S0'
>>>>>>>>> on 'centos-2.local:5051'.
>>>>>>>>>
>>>>>>>>> Potential reasons:
>>>>>>>>> The slave's hostname, 'centos-2.local', is not accessible from your
>>>>>>>>> network The slave's port, '5051', is not accessible from your network"
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I checked that:
>>>>>>>>> slave centos-2.local can be login from any machine in the cluster without
>>>>>>>>> password by "ssh centos-2.local ";
>>>>>>>>>
>>>>>>>>> port 5051 on slave centos-2.local could be connected from master by
>>>>>>>>> "telnet centos-2.local 5051"
>>>>>>>>> The stdout and stderr are there on each slave's /tmp/mesos/..., but seems mesos UI just could not access it.
>>>>>>>>> (and Both master and slaves are on the same network IP ranges). Should I open any port on slaves? Any hint what's the problem here?
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> Dan
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Unable to follow "Sandbox" links from Mesos UI.
Posted by Alex Rukletsov <al...@mesosphere.io>.
Dan,
you should be able to view file contents just by clicking on the link.
On Thu, Jan 22, 2015 at 9:57 PM, Dan Dong <do...@gmail.com> wrote:
> Yes, --hostname solves the problem. Now I can see all files there like
> stdout, stderr etc, but when I click on e.g stdout, it pops a new blank
> window(pailer.html) without the content of the file(9KB size). Although it
> provides a "Download" link beside, it would be much more convenient if one
> can view the stdout and stderr directly. Is this normal or there is still
> problem on my envs? Thanks!
>
> Cheers,
> Dan
>
>
> 2015-01-22 11:33 GMT-06:00 Adam Bordelon <ad...@mesosphere.io>:
>
> Try the --hostname parameters for master/slave. If you want to be extra
>> explicit about the IP (e.g. publish the public IP instead of the private
>> one in a cloud environment), you can also set the --ip parameter on
>> master/slave.
>>
>> On Thu, Jan 22, 2015 at 8:43 AM, Dan Dong <do...@gmail.com> wrote:
>>
>>> Thanks Ryan, yes, from the machine where the browser is on slave
>>> hostnames could not be resolved, so that's why failure, but it can reach
>>> them by IP address( I don't think sys admin would like to add those VMs
>>> entries to /etc/hosts on the server). I tried to change masters and slaves
>>> of mesos to IP addresses instead of hostname but UI still points to
>>> hostnames of slaves. Is threre a way to let mesos only use IP address of
>>> master and slaves?
>>>
>>> Cheers,
>>> Dan
>>>
>>>
>>> 2015-01-22 9:48 GMT-06:00 Ryan Thomas <r....@gmail.com>:
>>>
>>> It is a request from your browser session, not from the master that is
>>>> going to the slaves - so in order to view the sandbox you need to ensure
>>>> that the machine your browser is on can resolve and route to the masters
>>>> _and_ the slaves.
>>>>
>>>> The master doesn't proxy the sandbox requests through itself (yet) -
>>>> they are made directly from your browser instance to the slaves.
>>>>
>>>> Make sure you can resolve the slaves from the machine you're browsing
>>>> the UI on.
>>>>
>>>> Cheers,
>>>>
>>>> ryan
>>>>
>>>> On 22 January 2015 at 15:42, Dan Dong <do...@gmail.com> wrote:
>>>>
>>>>> Thank you all, the master and slaves can resolve each others' hostname
>>>>> and ssh login without password, firewalls have been switched off on all the
>>>>> machines too.
>>>>> So I'm confused what will block such a pull of info of slaves from UI?
>>>>>
>>>>> Cheers,
>>>>> Dan
>>>>>
>>>>>
>>>>> 2015-01-21 16:35 GMT-06:00 Cody Maloney <co...@mesosphere.io>:
>>>>>
>>>>> Also see https://issues.apache.org/jira/browse/MESOS-2129 if you want
>>>>>> to track progress on changing this.
>>>>>>
>>>>>> Unfortunately it is on hold for me at the moment to fix.
>>>>>>
>>>>>> Cody
>>>>>>
>>>>>> On Wed, Jan 21, 2015 at 2:07 PM, Ryan Thomas <r....@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hey Dan,
>>>>>>>
>>>>>>> The UI will attempt to pull that info directly from the slave so you
>>>>>>> need to make sure the host is resolvable and routeable from your browser.
>>>>>>>
>>>>>>> Cheers,
>>>>>>>
>>>>>>> Ryan
>>>>>>>
>>>>>>> From my phone
>>>>>>>
>>>>>>>
>>>>>>> On Wednesday, 21 January 2015, Dan Dong <do...@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hi, All,
>>>>>>>> When I try to access sandbox on mesos UI, I see the following info( The
>>>>>>>> same error appears on every slave sandbox.):
>>>>>>>>
>>>>>>>> "Failed to connect to slave '20150115-144719-3205108908-5050-4552-S0'
>>>>>>>> on 'centos-2.local:5051'.
>>>>>>>>
>>>>>>>> Potential reasons:
>>>>>>>> The slave's hostname, 'centos-2.local', is not accessible from your
>>>>>>>> network The slave's port, '5051', is not accessible from your network"
>>>>>>>>
>>>>>>>>
>>>>>>>> I checked that:
>>>>>>>> slave centos-2.local can be login from any machine in the cluster without
>>>>>>>> password by "ssh centos-2.local ";
>>>>>>>>
>>>>>>>> port 5051 on slave centos-2.local could be connected from master by
>>>>>>>> "telnet centos-2.local 5051"
>>>>>>>> The stdout and stderr are there on each slave's /tmp/mesos/..., but seems mesos UI just could not access it.
>>>>>>>> (and Both master and slaves are on the same network IP ranges). Should I open any port on slaves? Any hint what's the problem here?
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Dan
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Unable to follow "Sandbox" links from Mesos UI.
Posted by Dan Dong <do...@gmail.com>.
Yes, --hostname solves the problem. Now I can see all files there like
stdout, stderr etc, but when I click on e.g stdout, it pops a new blank
window(pailer.html) without the content of the file(9KB size). Although it
provides a "Download" link beside, it would be much more convenient if one
can view the stdout and stderr directly. Is this normal or there is still
problem on my envs? Thanks!
Cheers,
Dan
2015-01-22 11:33 GMT-06:00 Adam Bordelon <ad...@mesosphere.io>:
> Try the --hostname parameters for master/slave. If you want to be extra
> explicit about the IP (e.g. publish the public IP instead of the private
> one in a cloud environment), you can also set the --ip parameter on
> master/slave.
>
> On Thu, Jan 22, 2015 at 8:43 AM, Dan Dong <do...@gmail.com> wrote:
>
>> Thanks Ryan, yes, from the machine where the browser is on slave
>> hostnames could not be resolved, so that's why failure, but it can reach
>> them by IP address( I don't think sys admin would like to add those VMs
>> entries to /etc/hosts on the server). I tried to change masters and slaves
>> of mesos to IP addresses instead of hostname but UI still points to
>> hostnames of slaves. Is threre a way to let mesos only use IP address of
>> master and slaves?
>>
>> Cheers,
>> Dan
>>
>>
>> 2015-01-22 9:48 GMT-06:00 Ryan Thomas <r....@gmail.com>:
>>
>> It is a request from your browser session, not from the master that is
>>> going to the slaves - so in order to view the sandbox you need to ensure
>>> that the machine your browser is on can resolve and route to the masters
>>> _and_ the slaves.
>>>
>>> The master doesn't proxy the sandbox requests through itself (yet) -
>>> they are made directly from your browser instance to the slaves.
>>>
>>> Make sure you can resolve the slaves from the machine you're browsing
>>> the UI on.
>>>
>>> Cheers,
>>>
>>> ryan
>>>
>>> On 22 January 2015 at 15:42, Dan Dong <do...@gmail.com> wrote:
>>>
>>>> Thank you all, the master and slaves can resolve each others' hostname
>>>> and ssh login without password, firewalls have been switched off on all the
>>>> machines too.
>>>> So I'm confused what will block such a pull of info of slaves from UI?
>>>>
>>>> Cheers,
>>>> Dan
>>>>
>>>>
>>>> 2015-01-21 16:35 GMT-06:00 Cody Maloney <co...@mesosphere.io>:
>>>>
>>>> Also see https://issues.apache.org/jira/browse/MESOS-2129 if you want
>>>>> to track progress on changing this.
>>>>>
>>>>> Unfortunately it is on hold for me at the moment to fix.
>>>>>
>>>>> Cody
>>>>>
>>>>> On Wed, Jan 21, 2015 at 2:07 PM, Ryan Thomas <r....@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hey Dan,
>>>>>>
>>>>>> The UI will attempt to pull that info directly from the slave so you
>>>>>> need to make sure the host is resolvable and routeable from your browser.
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Ryan
>>>>>>
>>>>>> From my phone
>>>>>>
>>>>>>
>>>>>> On Wednesday, 21 January 2015, Dan Dong <do...@gmail.com> wrote:
>>>>>>
>>>>>>> Hi, All,
>>>>>>> When I try to access sandbox on mesos UI, I see the following info( The
>>>>>>> same error appears on every slave sandbox.):
>>>>>>>
>>>>>>> "Failed to connect to slave '20150115-144719-3205108908-5050-4552-S0'
>>>>>>> on 'centos-2.local:5051'.
>>>>>>>
>>>>>>> Potential reasons:
>>>>>>> The slave's hostname, 'centos-2.local', is not accessible from your
>>>>>>> network The slave's port, '5051', is not accessible from your network"
>>>>>>>
>>>>>>>
>>>>>>> I checked that:
>>>>>>> slave centos-2.local can be login from any machine in the cluster without
>>>>>>> password by "ssh centos-2.local ";
>>>>>>>
>>>>>>> port 5051 on slave centos-2.local could be connected from master by
>>>>>>> "telnet centos-2.local 5051"
>>>>>>> The stdout and stderr are there on each slave's /tmp/mesos/..., but seems mesos UI just could not access it.
>>>>>>> (and Both master and slaves are on the same network IP ranges). Should I open any port on slaves? Any hint what's the problem here?
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Dan
>>>>>>>
>>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Unable to follow "Sandbox" links from Mesos UI.
Posted by Adam Bordelon <ad...@mesosphere.io>.
Try the --hostname parameters for master/slave. If you want to be extra
explicit about the IP (e.g. publish the public IP instead of the private
one in a cloud environment), you can also set the --ip parameter on
master/slave.
On Thu, Jan 22, 2015 at 8:43 AM, Dan Dong <do...@gmail.com> wrote:
> Thanks Ryan, yes, from the machine where the browser is on slave hostnames
> could not be resolved, so that's why failure, but it can reach them by IP
> address( I don't think sys admin would like to add those VMs entries to
> /etc/hosts on the server). I tried to change masters and slaves of mesos
> to IP addresses instead of hostname but UI still points to hostnames of
> slaves. Is threre a way to let mesos only use IP address of master and
> slaves?
>
> Cheers,
> Dan
>
>
> 2015-01-22 9:48 GMT-06:00 Ryan Thomas <r....@gmail.com>:
>
> It is a request from your browser session, not from the master that is
>> going to the slaves - so in order to view the sandbox you need to ensure
>> that the machine your browser is on can resolve and route to the masters
>> _and_ the slaves.
>>
>> The master doesn't proxy the sandbox requests through itself (yet) - they
>> are made directly from your browser instance to the slaves.
>>
>> Make sure you can resolve the slaves from the machine you're browsing the
>> UI on.
>>
>> Cheers,
>>
>> ryan
>>
>> On 22 January 2015 at 15:42, Dan Dong <do...@gmail.com> wrote:
>>
>>> Thank you all, the master and slaves can resolve each others' hostname
>>> and ssh login without password, firewalls have been switched off on all the
>>> machines too.
>>> So I'm confused what will block such a pull of info of slaves from UI?
>>>
>>> Cheers,
>>> Dan
>>>
>>>
>>> 2015-01-21 16:35 GMT-06:00 Cody Maloney <co...@mesosphere.io>:
>>>
>>> Also see https://issues.apache.org/jira/browse/MESOS-2129 if you want
>>>> to track progress on changing this.
>>>>
>>>> Unfortunately it is on hold for me at the moment to fix.
>>>>
>>>> Cody
>>>>
>>>> On Wed, Jan 21, 2015 at 2:07 PM, Ryan Thomas <r....@gmail.com>
>>>> wrote:
>>>>
>>>>> Hey Dan,
>>>>>
>>>>> The UI will attempt to pull that info directly from the slave so you
>>>>> need to make sure the host is resolvable and routeable from your browser.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Ryan
>>>>>
>>>>> From my phone
>>>>>
>>>>>
>>>>> On Wednesday, 21 January 2015, Dan Dong <do...@gmail.com> wrote:
>>>>>
>>>>>> Hi, All,
>>>>>> When I try to access sandbox on mesos UI, I see the following info( The
>>>>>> same error appears on every slave sandbox.):
>>>>>>
>>>>>> "Failed to connect to slave '20150115-144719-3205108908-5050-4552-S0'
>>>>>> on 'centos-2.local:5051'.
>>>>>>
>>>>>> Potential reasons:
>>>>>> The slave's hostname, 'centos-2.local', is not accessible from your
>>>>>> network The slave's port, '5051', is not accessible from your network"
>>>>>>
>>>>>>
>>>>>> I checked that:
>>>>>> slave centos-2.local can be login from any machine in the cluster without
>>>>>> password by "ssh centos-2.local ";
>>>>>>
>>>>>> port 5051 on slave centos-2.local could be connected from master by
>>>>>> "telnet centos-2.local 5051"
>>>>>> The stdout and stderr are there on each slave's /tmp/mesos/..., but seems mesos UI just could not access it.
>>>>>> (and Both master and slaves are on the same network IP ranges). Should I open any port on slaves? Any hint what's the problem here?
>>>>>>
>>>>>> Cheers,
>>>>>> Dan
>>>>>>
>>>>>>
>>>>
>>>
>>
>
Re: Unable to follow "Sandbox" links from Mesos UI.
Posted by Dan Dong <do...@gmail.com>.
Thanks Ryan, yes, from the machine where the browser is on slave hostnames
could not be resolved, so that's why failure, but it can reach them by IP
address( I don't think sys admin would like to add those VMs entries to
/etc/hosts on the server). I tried to change masters and slaves of mesos
to IP addresses instead of hostname but UI still points to hostnames of
slaves. Is threre a way to let mesos only use IP address of master and
slaves?
Cheers,
Dan
2015-01-22 9:48 GMT-06:00 Ryan Thomas <r....@gmail.com>:
> It is a request from your browser session, not from the master that is
> going to the slaves - so in order to view the sandbox you need to ensure
> that the machine your browser is on can resolve and route to the masters
> _and_ the slaves.
>
> The master doesn't proxy the sandbox requests through itself (yet) - they
> are made directly from your browser instance to the slaves.
>
> Make sure you can resolve the slaves from the machine you're browsing the
> UI on.
>
> Cheers,
>
> ryan
>
> On 22 January 2015 at 15:42, Dan Dong <do...@gmail.com> wrote:
>
>> Thank you all, the master and slaves can resolve each others' hostname
>> and ssh login without password, firewalls have been switched off on all the
>> machines too.
>> So I'm confused what will block such a pull of info of slaves from UI?
>>
>> Cheers,
>> Dan
>>
>>
>> 2015-01-21 16:35 GMT-06:00 Cody Maloney <co...@mesosphere.io>:
>>
>> Also see https://issues.apache.org/jira/browse/MESOS-2129 if you want to
>>> track progress on changing this.
>>>
>>> Unfortunately it is on hold for me at the moment to fix.
>>>
>>> Cody
>>>
>>> On Wed, Jan 21, 2015 at 2:07 PM, Ryan Thomas <r....@gmail.com>
>>> wrote:
>>>
>>>> Hey Dan,
>>>>
>>>> The UI will attempt to pull that info directly from the slave so you
>>>> need to make sure the host is resolvable and routeable from your browser.
>>>>
>>>> Cheers,
>>>>
>>>> Ryan
>>>>
>>>> From my phone
>>>>
>>>>
>>>> On Wednesday, 21 January 2015, Dan Dong <do...@gmail.com> wrote:
>>>>
>>>>> Hi, All,
>>>>> When I try to access sandbox on mesos UI, I see the following info( The
>>>>> same error appears on every slave sandbox.):
>>>>>
>>>>> "Failed to connect to slave '20150115-144719-3205108908-5050-4552-S0'
>>>>> on 'centos-2.local:5051'.
>>>>>
>>>>> Potential reasons:
>>>>> The slave's hostname, 'centos-2.local', is not accessible from your
>>>>> network The slave's port, '5051', is not accessible from your network"
>>>>>
>>>>>
>>>>> I checked that:
>>>>> slave centos-2.local can be login from any machine in the cluster without
>>>>> password by "ssh centos-2.local ";
>>>>>
>>>>> port 5051 on slave centos-2.local could be connected from master by
>>>>> "telnet centos-2.local 5051"
>>>>> The stdout and stderr are there on each slave's /tmp/mesos/..., but seems mesos UI just could not access it.
>>>>> (and Both master and slaves are on the same network IP ranges). Should I open any port on slaves? Any hint what's the problem here?
>>>>>
>>>>> Cheers,
>>>>> Dan
>>>>>
>>>>>
>>>
>>
>
Re: Unable to follow "Sandbox" links from Mesos UI.
Posted by Ryan Thomas <r....@gmail.com>.
It is a request from your browser session, not from the master that is
going to the slaves - so in order to view the sandbox you need to ensure
that the machine your browser is on can resolve and route to the masters
_and_ the slaves.
The master doesn't proxy the sandbox requests through itself (yet) - they
are made directly from your browser instance to the slaves.
Make sure you can resolve the slaves from the machine you're browsing the
UI on.
Cheers,
ryan
On 22 January 2015 at 15:42, Dan Dong <do...@gmail.com> wrote:
> Thank you all, the master and slaves can resolve each others' hostname and
> ssh login without password, firewalls have been switched off on all the
> machines too.
> So I'm confused what will block such a pull of info of slaves from UI?
>
> Cheers,
> Dan
>
>
> 2015-01-21 16:35 GMT-06:00 Cody Maloney <co...@mesosphere.io>:
>
> Also see https://issues.apache.org/jira/browse/MESOS-2129 if you want to
>> track progress on changing this.
>>
>> Unfortunately it is on hold for me at the moment to fix.
>>
>> Cody
>>
>> On Wed, Jan 21, 2015 at 2:07 PM, Ryan Thomas <r....@gmail.com>
>> wrote:
>>
>>> Hey Dan,
>>>
>>> The UI will attempt to pull that info directly from the slave so you
>>> need to make sure the host is resolvable and routeable from your browser.
>>>
>>> Cheers,
>>>
>>> Ryan
>>>
>>> From my phone
>>>
>>>
>>> On Wednesday, 21 January 2015, Dan Dong <do...@gmail.com> wrote:
>>>
>>>> Hi, All,
>>>> When I try to access sandbox on mesos UI, I see the following info( The
>>>> same error appears on every slave sandbox.):
>>>>
>>>> "Failed to connect to slave '20150115-144719-3205108908-5050-4552-S0'
>>>> on 'centos-2.local:5051'.
>>>>
>>>> Potential reasons:
>>>> The slave's hostname, 'centos-2.local', is not accessible from your
>>>> network The slave's port, '5051', is not accessible from your network"
>>>>
>>>>
>>>> I checked that:
>>>> slave centos-2.local can be login from any machine in the cluster without
>>>> password by "ssh centos-2.local ";
>>>>
>>>> port 5051 on slave centos-2.local could be connected from master by
>>>> "telnet centos-2.local 5051"
>>>> The stdout and stderr are there on each slave's /tmp/mesos/..., but seems mesos UI just could not access it.
>>>> (and Both master and slaves are on the same network IP ranges). Should I open any port on slaves? Any hint what's the problem here?
>>>>
>>>> Cheers,
>>>> Dan
>>>>
>>>>
>>
>
Re: Unable to follow "Sandbox" links from Mesos UI.
Posted by Dan Dong <do...@gmail.com>.
Thank you all, the master and slaves can resolve each others' hostname and
ssh login without password, firewalls have been switched off on all the
machines too.
So I'm confused what will block such a pull of info of slaves from UI?
Cheers,
Dan
2015-01-21 16:35 GMT-06:00 Cody Maloney <co...@mesosphere.io>:
> Also see https://issues.apache.org/jira/browse/MESOS-2129 if you want to
> track progress on changing this.
>
> Unfortunately it is on hold for me at the moment to fix.
>
> Cody
>
> On Wed, Jan 21, 2015 at 2:07 PM, Ryan Thomas <r....@gmail.com> wrote:
>
>> Hey Dan,
>>
>> The UI will attempt to pull that info directly from the slave so you need
>> to make sure the host is resolvable and routeable from your browser.
>>
>> Cheers,
>>
>> Ryan
>>
>> From my phone
>>
>>
>> On Wednesday, 21 January 2015, Dan Dong <do...@gmail.com> wrote:
>>
>>> Hi, All,
>>> When I try to access sandbox on mesos UI, I see the following info( The
>>> same error appears on every slave sandbox.):
>>>
>>> "Failed to connect to slave '20150115-144719-3205108908-5050-4552-S0'
>>> on 'centos-2.local:5051'.
>>>
>>> Potential reasons:
>>> The slave's hostname, 'centos-2.local', is not accessible from your
>>> network The slave's port, '5051', is not accessible from your network"
>>>
>>>
>>> I checked that:
>>> slave centos-2.local can be login from any machine in the cluster without
>>> password by "ssh centos-2.local ";
>>>
>>> port 5051 on slave centos-2.local could be connected from master by
>>> "telnet centos-2.local 5051"
>>> The stdout and stderr are there on each slave's /tmp/mesos/..., but seems mesos UI just could not access it.
>>> (and Both master and slaves are on the same network IP ranges). Should I open any port on slaves? Any hint what's the problem here?
>>>
>>> Cheers,
>>> Dan
>>>
>>>
>
Re: Unable to follow "Sandbox" links from Mesos UI.
Posted by Cody Maloney <co...@mesosphere.io>.
Also see https://issues.apache.org/jira/browse/MESOS-2129 if you want to
track progress on changing this.
Unfortunately it is on hold for me at the moment to fix.
Cody
On Wed, Jan 21, 2015 at 2:07 PM, Ryan Thomas <r....@gmail.com> wrote:
> Hey Dan,
>
> The UI will attempt to pull that info directly from the slave so you need
> to make sure the host is resolvable and routeable from your browser.
>
> Cheers,
>
> Ryan
>
> From my phone
>
>
> On Wednesday, 21 January 2015, Dan Dong <do...@gmail.com> wrote:
>
>> Hi, All,
>> When I try to access sandbox on mesos UI, I see the following info( The
>> same error appears on every slave sandbox.):
>>
>> "Failed to connect to slave '20150115-144719-3205108908-5050-4552-S0'
>> on 'centos-2.local:5051'.
>>
>> Potential reasons:
>> The slave's hostname, 'centos-2.local', is not accessible from your
>> network The slave's port, '5051', is not accessible from your network"
>>
>>
>> I checked that:
>> slave centos-2.local can be login from any machine in the cluster without
>> password by "ssh centos-2.local ";
>>
>> port 5051 on slave centos-2.local could be connected from master by
>> "telnet centos-2.local 5051"
>> The stdout and stderr are there on each slave's /tmp/mesos/..., but seems mesos UI just could not access it.
>> (and Both master and slaves are on the same network IP ranges). Should I open any port on slaves? Any hint what's the problem here?
>>
>> Cheers,
>> Dan
>>
>>
Re: Unable to follow "Sandbox" links from Mesos UI.
Posted by Ryan Thomas <r....@gmail.com>.
Hey Dan,
The UI will attempt to pull that info directly from the slave so you need
to make sure the host is resolvable and routeable from your browser.
Cheers,
Ryan
>From my phone
On Wednesday, 21 January 2015, Dan Dong <do...@gmail.com> wrote:
> Hi, All,
> When I try to access sandbox on mesos UI, I see the following info( The
> same error appears on every slave sandbox.):
>
> "Failed to connect to slave '20150115-144719-3205108908-5050-4552-S0'
> on 'centos-2.local:5051'.
>
> Potential reasons:
> The slave's hostname, 'centos-2.local', is not accessible from your
> network The slave's port, '5051', is not accessible from your network"
>
>
> I checked that:
> slave centos-2.local can be login from any machine in the cluster without
> password by "ssh centos-2.local ";
>
> port 5051 on slave centos-2.local could be connected from master by
> "telnet centos-2.local 5051"
> The stdout and stderr are there on each slave's /tmp/mesos/..., but seems mesos UI just could not access it.
> (and Both master and slaves are on the same network IP ranges). Should I open any port on slaves? Any hint what's the problem here?
>
> Cheers,
> Dan
>
>