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