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 <jazzist...@gmail.com>: > 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 <haosd...@gmail.com>: > >> 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 <jazzist...@gmail.com> >> wrote: >> >>> i dont' have 10.250.0.12 <http://10.250.0.12:5050/> floating IP, i have >>> 10.250.0.124 <http://10.250.0.12:5050/> 10.250.0.125 >>> <http://10.250.0.12:5050/> and 10.250.0.126 <http://10.250.0.12:5050/> >>> >>> 2016-06-11 19:13 GMT+02:00 Stefano Bianchi <jazzist...@gmail.com>: >>> >>>> 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 GMT+02:00 haosdent <haosd...@gmail.com>: >>>> >>>>> If 10.250.0.12:5050 used by any other processes? >>>>> >>>>> On Sat, Jun 11, 2016 at 9:18 PM, Stefano Bianchi <jazzist...@gmail.com >>>>> > 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 >>>>>> >>>>>> 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 master: nano /etc/zookeeper/conf/zoo.cfg >>>>>> the last three lines are: >>>>>> server.1=192.168.100.54:2888:3888 >>>>>> server.2=192.168.100.55:2888:3888 >>>>>> server.3=192.168.10.16:2888:3888 >>>>>> >>>>>> where 2888 and 3888 are both open on openstack security group. >>>>>> >>>>>> 3)nano /etc/mesos/zk >>>>>> >>>>>> zk://192.168.100.3:2181,192.168.100.4:2181,192.168.10.3:2181/mesos >>>>>> >>>>>> 4) Set the quorum to 2with >>>>>> nano /etc/mesos-master/quorum and i have written 2 >>>>>> >>>>>> 5)then in /etc/mesos-master/ i created hostname and ip files, within >>>>>> which i have written the public IPs of the masters such that i can use >>>>>> sandbox on web ui. >>>>>> the same in /etc/marathon/conf/ just creating hostname file. >>>>>> >>>>>> let me say that the openstack cluster on which i'm now working on >>>>>> isnot on the public internet but under a private network of the >>>>>> university >>>>>> lab. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> 2016-06-10 22:21 GMT+02:00 Joseph Wu <jos...@mesosphere.io>: >>>>>> >>>>>>> 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 < >>>>>>> jazzist...@gmail.com> wrote: >>>>>>> >>>>>>>> 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 UTC, end at ven 2016-06-10 >>>>>>>> 18:02:23 UTC. -- >>>>>>>> >>>>>>>> giu 09 23:24:35 master.novalocal systemd[1]: Started Mesos Master. >>>>>>>> >>>>>>>> giu 09 23:24:35 master.novalocal systemd[1]: Starting Mesos >>>>>>>> Master... >>>>>>>> >>>>>>>> giu 09 23:24:51 master.novalocal mesos-master[808]: *WARNING: >>>>>>>> Logging before InitGoogleLogging() is written to STDERR* >>>>>>>> >>>>>>>> giu 09 23:24:51 master.novalocal mesos-master[808]: *F0609 >>>>>>>> 23:24:51.739418 718 process.cpp:892] Failed to initialize: Failed to >>>>>>>> bind >>>>>>>> on 10.250.0.124* >>>>>>>> >>>>>>>> giu 09 23:24:52 master.novalocal mesos-master[808]: **** Check >>>>>>>> failure stack trace: **** >>>>>>>> >>>>>>>> giu 09 23:24:52 master.novalocal systemd[1]: *mesos-master.service: >>>>>>>> main process exited, code=killed, status=6/ABRT* >>>>>>>> >>>>>>>> giu 09 23:24:52 master.novalocal systemd[1]: *Unit >>>>>>>> mesos-master.service entered failed state.* >>>>>>>> >>>>>>>> giu 09 23:24:52 master.novalocal systemd[1]: *mesos-master.service >>>>>>>> failed.* >>>>>>>> >>>>>>>> giu 09 23:25:14 master.novalocal systemd[1]: mesos-master.service >>>>>>>> holdoff time over, scheduling restart. >>>>>>>> >>>>>>>> giu 09 23:25:14 master.novalocal systemd[1]: Started Mesos Master. >>>>>>>> >>>>>>>> giu 09 23:25:14 master.novalocal systemd[1]: Starting Mesos >>>>>>>> Master... >>>>>>>> >>>>>>>> giu 09 23:25:15 master.novalocal mesos-master[1091]: *WARNING: >>>>>>>> Logging before InitGoogleLogging() is written to STDERR* >>>>>>>> >>>>>>>> giu 09 23:25:15 master.novalocal mesos-master[1091]: *F0609 >>>>>>>> 23:25:15.071262 1075 process.cpp:892] Failed to initialize: Failed to >>>>>>>> bind >>>>>>>> on 10.250.0.12* >>>>>>>> >>>>>>>> giu 09 23:25:15 master.novalocal mesos-master[1091]: **** Check >>>>>>>> failure stack trace: **** >>>>>>>> >>>>>>>> giu 09 23:25:15 master.novalocal systemd[1]: *mesos-master.service: >>>>>>>> main process exited, code=killed, status=6/ABRT* >>>>>>>> >>>>>>>> giu 09 23:25:15 master.novalocal systemd[1]: *Unit >>>>>>>> mesos-master.service entered failed state.* >>>>>>>> >>>>>>>> giu 09 23:25:15 master.novalocal systemd[1]: *mesos-master.service >>>>>>>> failed.* >>>>>>>> >>>>>>>> giu 09 23:25:35 master.novalocal systemd[1]: mesos-master.service >>>>>>>> holdoff time over, scheduling restart. >>>>>>>> >>>>>>>> giu 09 23:25:35 master.novalocal systemd[1]: Started Mesos Master. >>>>>>>> >>>>>>>> giu 09 23:25:35 master.novalocal systemd[1]: Starting Mesos >>>>>>>> Master... >>>>>>>> >>>>>>>> giu 09 23:25:35 master.novalocal mesos-master[1156]: *WARNING: >>>>>>>> Logging before InitGoogleLogging() is written to STDERR* >>>>>>>> >>>>>>>> giu 09 23:25:35 master.novalocal mesos-master[1156]: *F0609 >>>>>>>> 23:25:35.288352 1141 process.cpp:892] Failed to initialize: Failed to >>>>>>>> bind >>>>>>>> on 10.250.0.12* >>>>>>>> >>>>>>>> giu 09 23:25:35 master.novalocal mesos-master[1156]: **** Check >>>>>>>> failure stack trace: **** >>>>>>>> >>>>>>>> giu 09 23:25:35 master.novalocal systemd[1]: *mesos-master.service: >>>>>>>> main process exited, code=killed, status=6/ABRT* >>>>>>>> >>>>>>>> giu 09 23:25:35 master.novalocal systemd[1]: *Unit >>>>>>>> mesos-master.service entered failed state.* >>>>>>>> >>>>>>>> giu 09 23:25:35 master.novalocal systemd[1]: *mesos-master.service >>>>>>>> failed.* >>>>>>>> >>>>>>>> giu 09 23:25:55 master.novalocal systemd[1]: mesos-master.service >>>>>>>> holdoff time over, scheduling restart. >>>>>>>> >>>>>>>> giu 09 23:25:55 master.novalocal systemd[1]: Started Mesos Master. >>>>>>>> >>>>>>>> giu 09 23:25:55 master.novalocal systemd[1]: Starting Mesos >>>>>>>> Master... >>>>>>>> >>>>>>>> giu 09 23:25:55 master.novalocal mesos-master[1241]: *WARNING: >>>>>>>> Logging before InitGoogleLogging() is written to STDERR* >>>>>>>> >>>>>>>> giu 09 23:25:55 master.novalocal mesos-master[1241]: *F0609 >>>>>>>> 23:25:55.562469 1225 process.cpp:892] Failed to initialize: Failed to >>>>>>>> bind >>>>>>>> on 10.250.0.12* >>>>>>>> >>>>>>>> giu 09 23:25:55 master.novalocal mesos-master[1241]: **** Check >>>>>>>> failure stack trace: **** >>>>>>>> >>>>>>>> giu 09 23:25:55 master.novalocal systemd[1]: *mesos-master.service: >>>>>>>> main process exited, code=killed, status=6/ABRT* >>>>>>>> >>>>>>>> giu 09 23:25:55 master.novalocal systemd[1]: *Unit >>>>>>>> mesos-master.service entered failed state.* >>>>>>>> >>>>>>>> giu 09 23:25:55 master.novalocal systemd[1]: *mesos-master.service >>>>>>>> failed.* >>>>>>>> >>>>>>>> giu 09 23:26:15 master.novalocal systemd[1]: mesos-master.service >>>>>>>> holdoff time over, scheduling restart. >>>>>>>> >>>>>>>> giu 09 23:26:15 master.novalocal systemd[1]: Started Mesos Master. >>>>>>>> >>>>>>>> giu 09 23:26:15 master.novalocal systemd[1]: Starting Mesos >>>>>>>> Master... >>>>>>>> >>>>>>>> giu 09 23:26:15 master.novalocal mesos-master[1300]: *WARNING: >>>>>>>> Logging before InitGoogleLogging() is written to STDERR* >>>>>>>> >>>>>>>> giu 09 23:26:15 master.novalocal mesos-master[1300]: *F0609 >>>>>>>> 23:26:15.898391 1285 process.cpp:892] Failed to initialize: Failed to >>>>>>>> bind >>>>>>>> on 10.250.0.12* >>>>>>>> >>>>>>>> giu 09 23:26:15 master.novalocal mesos-master[1300]: **** Check >>>>>>>> failure stack trace: **** >>>>>>>> >>>>>>>> giu 09 23:26:15 master.novalocal systemd[1]: *mesos-master.service: >>>>>>>> main process exited, code=killed, status=6/ABRT* >>>>>>>> >>>>>>>> giu 09 23:26:15 master.novalocal systemd[1]: *Unit >>>>>>>> mesos-master.service entered failed state.* >>>>>>>> >>>>>>>> giu 09 23:26:15 master.novalocal systemd[1]: *mesos-master.service >>>>>>>> failed.* >>>>>>>> >>>>>>>> giu 09 23:26:35 master.novalocal systemd[1]: mesos-master.service >>>>>>>> holdoff time over, scheduling restart. >>>>>>>> >>>>>>>> giu 09 23:26:35 master.novalocal systemd[1]: Started Mesos Master. >>>>>>>> >>>>>>>> giu 09 23:26:35 master.novalocal systemd[1]: Starting Mesos >>>>>>>> Master... >>>>>>>> >>>>>>>> 2016-06-10 18:51 GMT+02:00 Joseph Wu <jos...@mesosphere.io>: >>>>>>>> >>>>>>>>> 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 service, use: journalctl >>>>>>>>> -u mesos-master >>>>>>>>> >>>>>>>>> On Fri, Jun 10, 2016 at 9:45 AM, Stefano Bianchi < >>>>>>>>> jazzist...@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> 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 <yujie....@gmail.com>: >>>>>>>>>> >>>>>>>>>>> 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 < >>>>>>>>>>> jazzist...@gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>> 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 seems to start but if i check the status with: service >>>>>>>>>>> mesos-master status >>>>>>>>>>> i obtain the following: >>>>>>>>>>> >>>>>>>>>>> [root@master ~]# service mesos-master status >>>>>>>>>>> >>>>>>>>>>> Redirecting to /bin/systemctl status mesos-master.service >>>>>>>>>>> >>>>>>>>>>> ● mesos-master.service - Mesos Master >>>>>>>>>>> >>>>>>>>>>> Loaded: loaded (/usr/lib/systemd/system/mesos-master.service; >>>>>>>>>>> enabled; vendor preset: disabled) >>>>>>>>>>> >>>>>>>>>>> Active: activating (auto-restart) (Result: signal) since ven >>>>>>>>>>> 2016-06-10 15:39:36 UTC; 3s ago >>>>>>>>>>> >>>>>>>>>>> Process: 12163 ExecStart=/usr/bin/mesos-init-wrapper master >>>>>>>>>>> *(code=killed, >>>>>>>>>>> signal=ABRT)* >>>>>>>>>>> >>>>>>>>>>> Main PID: 12163 (code=killed, signal=ABRT) >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Any one knows why i have this issue? >>>>>>>>>>> >>>>>>>>>>> Thanks in advance. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Best Regards, >>>>> Haosdent Huang >>>>> >>>> >>>> >>> >> >> >> -- >> Best Regards, >> Haosdent Huang >> > >
