The public (floating) IP in OpenStack was generated by some NAT or iptables rules, and this will not be shown via `ifconfig`. I think that you can try private IP for your whole cluster.
Thanks, Guangya On Thu, May 26, 2016 at 10:12 AM, haosdent <[email protected]> wrote: > Hi, @Omar > May you change both /etc/mesos/mesos-slave/ip and > /etc/mesos/mesos-slave/hostname to private ip as well (192.168.100.xx)? > Because if you public ip could not be shown via ifconfig, you need to use > LIBPROCESS_ADVERTISE_IP to export public ip. > > And could you show the log under /var/log/mesos/ ? I think the log you > show above is upstart log not mesos log. > > On Thu, May 26, 2016 at 4:07 AM, 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 >>> >> >> > > > -- > Best Regards, > Haosdent Huang >
