Re: Mesos 0.28.2 does not start

2016-06-13 Thread Dick Davies
My guess would be your networking is still wonky. Each master is putting their IP into zookeeper, and the other masters use that to find each other for elections. you can poke around in zookeeper with zkCli.sh, that should give you an idea which IP is ending up there - or just check each masters

Re: Mesos 0.28.2 does not start

2016-06-12 Thread Dick Davies
Try putting the IP you're binding to (the actual IP on the master) in /etc/mesos-*/ip , and the externally accessible IP in /etc/mesos-*/hostname. On 12 June 2016 at 00:57, Stefano Bianchi wrote: > ok i guess i figured out. > The reason for which i put floating IP on

Re: Mesos 0.28.2 does not start

2016-06-11 Thread Stefano Bianchi
Wait, i saw now that on openstack security group pots 5050 8080 and 4400 are not open... 2016-06-11 19:35 GMT+02:00 Erik Weathers : > I'm not 100% sure what is implied by "public" and "floating" IPs here. > Are the IPs of 10.20.250.x the *actual* IPs on the hosts? i.e.,

Re: Mesos 0.28.2 does not start

2016-06-11 Thread Erik Weathers
I'm not 100% sure what is implied by "public" and "floating" IPs here. Are the IPs of 10.20.250.x the *actual* IPs on the hosts? i.e., if you run "ifconfig -a" or "ip a" do those IPs appear? If not then you cannot bind to them on the host. - Erik On Sat, Jun 11, 2016 at 10:32 AM, Stefano

Re: Mesos 0.28.2 does not start

2016-06-11 Thread Stefano Bianchi
The floating IPs are correclty set both on /etc/mesos-master/ip and /etc/mesos-master/hostname 2016-06-11 19:27 GMT+02:00 Stefano Bianchi : > i checked now, and i have correctly set 10.250.0.124, 10.250.0.125, > 10.250.0.126 > according to the masters floating IPs > >

Re: Mesos 0.28.2 does not start

2016-06-11 Thread Stefano Bianchi
i checked now, and i have correctly set 10.250.0.124, 10.250.0.125, 10.250.0.126 according to the masters floating IPs 2016-06-11 19:18 GMT+02:00 haosdent : > Oh, according to the log. It looks like your set /etc/mesos-master/ip > to 10.250.0.12? > > On Sun, Jun 12, 2016 at

Re: Mesos 0.28.2 does not start

2016-06-11 Thread haosdent
Oh, according to the log. It looks like your set /etc/mesos-master/ip to 10.250.0.12? On Sun, Jun 12, 2016 at 1:15 AM, Stefano Bianchi wrote: > i dont' have 10.250.0.12 floating IP, i have > 10.250.0.124 10.250.0.125 >

Re: Mesos 0.28.2 does not start

2016-06-11 Thread Stefano Bianchi
i dont' have 10.250.0.12 floating IP, i have 10.250.0.124 10.250.0.125 and 10.250.0.126 2016-06-11 19:13 GMT+02:00 Stefano Bianchi : > sorry i have made a mistakee in

Re: Mesos 0.28.2 does not start

2016-06-11 Thread Stefano Bianchi
sorry i have made a mistakee in my previous message, On each master: nano /etc/zookeeper/conf/zoo.cfg the last three lines are: server.1=192.168.100.3:2888:3888 server.2=192.168.100.4:2888:3888 server.3=192.168.10.3:2888:3888 these are the correct IPs i have set in this file. 2016-06-11 15:36

Re: Mesos 0.28.2 does not start

2016-06-11 Thread haosdent
If 10.250.0.12:5050 used by any other processes? On Sat, Jun 11, 2016 at 9:18 PM, Stefano Bianchi wrote: > I have set: > > 1) > On master1: > sudo -u zookeeper zookeeper-server-initialize --myid=1 > > On Master2: > sudo -u zookeeper zookeeper-server-initialize --myid=2 > >

Re: Mesos 0.28.2 does not start

2016-06-11 Thread Stefano Bianchi
I have set: 1) On master1: sudo -u zookeeper zookeeper-server-initialize --myid=1 On Master2: sudo -u zookeeper zookeeper-server-initialize --myid=2 On Master3: sudo -u zookeeper zookeeper-server-initialize --myid=3 i checked /var/lib/zookeeper/myid and i get correctly 1, 2 and 3 2) On each

Re: Mesos 0.28.2 does not start

2016-06-10 Thread Joseph Wu
Looks like the master can't bind to the IP you have specified (or, if you did not specify, the master resolved it from the computer's hostname). Either specify the --ip master flag or investigate the problem with your network. On Fri, Jun 10, 2016 at 11:03 AM, Stefano Bianchi

Re: Mesos 0.28.2 does not start

2016-06-10 Thread Stefano Bianchi
this is what i get with your command: giu 10 18:02:23 master.novalocal systemd[1]: *Unit mesos-master.service entered failed state.* giu 10 18:02:23 master.novalocal systemd[1]: *mesos-master.service failed.* [root@master ~]# journalctl -u mesos-master -- Logs begin at gio 2016-06-09 23:24:02

Re: Mesos 0.28.2 does not start

2016-06-10 Thread Joseph Wu
The log directory is based on your configuration. See the master config section here: http://mesos.apache.org/documentation/latest/configuration/ If you've set the --log_dir flag, you'll find your logs there. Otherwise, the logs will be in stderr. If you launched the master via a systemd

Re: Mesos 0.28.2 does not start

2016-06-10 Thread Stefano Bianchi
Actually i don't have the access to the Mesos UI so i need to find the log within CentOS VM. Please can you tell me where can i find the master log file ? 2016-06-10 17:50 GMT+02:00 Jie Yu : > Can u create a jira ticket and paste the master log? Thanks for reporting! > >

Re: Mesos 0.28.2 does not start

2016-06-10 Thread Joseph Wu
I'm guessing you mis-configured a master flag/environment-variable somewhere. Since it looks like you're using systemd, can you run this command, "journalctl -xe", right after you try to start the service? That should show you more info on why your master aborted. On Fri, Jun 10, 2016 at 8:50

Re: Mesos 0.28.2 does not start

2016-06-10 Thread Jie Yu
Can u create a jira ticket and paste the master log? Thanks for reporting! Sent from my iPhone > On Jun 10, 2016, at 8:44 AM, Stefano Bianchi wrote: > > Hi all > i'm re installing my platform on another openstack tenant. > I downloaded all the needed softwares,

Mesos 0.28.2 does not start

2016-06-10 Thread Stefano Bianchi
Hi all i'm re installing my platform on another openstack tenant. I downloaded all the needed softwares, zookeeper-server, mesos 0.28.2 marathon 1.1.1 and chronos 2.4.0. i have configured all correctly the i started zookeeper-server and it works fine. when i type: service mesos-master start it