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 >>> >>> >
