Omar, For mesos, master and agents need to be able to reach zookeeper (2181 by default). Agents need 5050 avaialble on the master and master needs 5051 on the agent.
Are you trying to bind mesos to an IP address which is not assigned to the interface? This will not work, right? – Best regards, Radek Gruchalski [email protected] de.linkedin.com/in/radgruchalski Confidentiality: This communication is intended for the above-named person and may be confidential and/or legally privileged. If it has come to you in error you must take no action based on it, nor must you copy or show it to anyone; please delete/destroy and inform the sender immediately. On May 25, 2016 at 10:25:08 PM, Omar Sobh ([email protected]) wrote: In my /etc/hosts I have the IP mapped to the VM's private IP address: 192.168.100.38 dev01.org and it's public IP (allocated floating IP) would be something like 140.141.210.220. within the VM itself if i type ifconfig it only shows eth0 being the 192 address. in the /etc/mesos/mesos-slave/ip I have: 140.141.210.220 when I start mesos slave I get: [89726.105700] init: mesos-slave main process ended, respawning [89726.221619] init: mesos-slave main process (5868) killed by ABRT signal [89726.221627] init: mesos-slave main process ended, respawning [89726.332208] init: mesos-slave main process (5897) killed by ABRT signal [89726.332216] init: mesos-slave main process ended, respawning [89726.443081] init: mesos-slave main process (5926) killed by ABRT signal [89726.443089] init: mesos-slave respawning too fast, stopped not sure what's the issue with the mappings...all ports are open on the firewall..but just to be sure what ports are needed by the master and slave to communicate? -O On 5/25/2016 12:11 PM, Stefano Bianchi wrote: > uld also edit the hosts file where you associate the hostnames of e
