Re: Mesos 0.28.2 does not start

[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 log, that'll normally give
similar information.

TBH it sounds like you've made yourself a difficult setup with this
openstack thing :(

On 13 June 2016 at 13:06, Stefano Bianchi  wrote:
> Hi guys i don't know why but my three masters cannot determine the leader.
> How can i give you a log file do check?
>
> 2016-06-12 10:42 GMT+02:00 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 hostname and ip files is
>> > written
>> > here:https://open.mesosphere.com/getting-started/install/
>> >
>> > It says:
>> > If you're unable to resolve the hostname of the machine directly (e.g.,
>> > if
>> > on a different network or using a VPN), set /etc/mesos-slave/hostname to
>> > a
>> > value that you can resolve, for example, an externally accessible IP
>> > address
>> > or DNS hostname. This will ensure all links from the Mesos console work
>> > correctly.
>> >
>> > The problem, i guess, is that the set of floating iPs 10.250.0.xxx is
>> > not
>> > externally accessible.
>> > In my other deployment i have set the floating IPs in these files and
>> > all is
>> > perfectly working, but in that case i have used externally reachable
>> > IPs.
>> >
>> > 2016-06-11 22:51 GMT+02:00 Erik Weathers :
>> >>
>> >> It depends on your setup.  I would probably not set the hostname and
>> >> instead set the "--no-hostname_lookup" flag.  I'm not sure how you do
>> >> that
>> >> with the file-based configuration style you are using.
>> >>
>> >> % mesos-master --help
>> >> ...
>> >>
>> >>   --hostname=VALUE  The hostname the master should
>> >> advertise
>> >> in ZooKeeper.
>> >> If left unset, the
>> >> hostname is resolved from the IP address
>> >> that the slave binds
>> >> to;
>> >> unless the user explicitly prevents
>> >> that, using
>> >> `--no-hostname_lookup`, in which case the IP itself
>> >> is used.
>> >>
>> >> On Sat, Jun 11, 2016 at 1:27 PM, Stefano Bianchi 
>> >> wrote:
>> >>>
>> >>> So Erik do you suggest to use the 192.* IP in both
>> >>> /etc/mesos-master/hostname nad /etc/mesos-master/ip right?
>> >>>
>> >>> Il 11/giu/2016 22:15, "Erik Weathers"  ha
>> >>> scritto:
>> 
>>  Yeah, so there is no 10.x address on the box.  Thus you cannot bind
>>  Mesos to listen to that address.   You need to use one of the 192.*
>>  IPs for
>>  Mesos to bind to.  I'm not sure why you say you need to use the 10.x
>>  addresses for the UI, that sounds like a problem you should tackle
>>  *after*
>>  getting Mesos up.
>> 
>>  - Erik
>> 
>>  P.S., when using gmail in chrome, you can avoid those extraneous
>>  newlines when you paste by holding "Shift" along with the Command-V
>>  (at
>>  least on Mac OS X!).
>> 
>>  On Sat, Jun 11, 2016 at 1:06 PM, Stefano Bianchi
>>  
>>  wrote:
>> >
>> > ifconfig -a
>> >
>> > eth0: flags=4163  mtu 1454
>> >
>> > inet 192.168.100.3  netmask 255.255.255.0  broadcast
>> > 192.168.100.255
>> >
>> > inet6 fe80::f816:3eff:fe1c:a3bf  prefixlen 64  scopeid
>> > 0x20
>> >
>> > ether fa:16:3e:1c:a3:bf  txqueuelen 1000  (Ethernet)
>> >
>> > RX packets 61258  bytes 4686426 (4.4 MiB)
>> >
>> > RX errors 0  dropped 0  overruns 0  frame 0
>> >
>> > TX packets 40537  bytes 3603100 (3.4 MiB)
>> >
>> > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>> >
>> >
>> > lo: flags=73  mtu 65536
>> >
>> > inet 127.0.0.1  netmask 255.0.0.0
>> >
>> > inet6 ::1  prefixlen 128  scopeid 0x10
>> >
>> > loop  txqueuelen 0  (Local Loopback)
>> >
>> > RX packets 28468  bytes 1672684 (1.5 MiB)
>> >
>> > RX errors 0  dropped 0  overruns 0  frame 0
>> >
>> > TX packets 28468  bytes 1672684 (1.5 MiB)
>> >
>> > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>> >
>> >
>> >
>> > ip addr:1: lo:  mtu 65536 

Re: Mesos 0.28.2 does not start

[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 hostname and ip files is written
> here:https://open.mesosphere.com/getting-started/install/
>
> It says:
> If you're unable to resolve the hostname of the machine directly (e.g., if
> on a different network or using a VPN), set /etc/mesos-slave/hostname to a
> value that you can resolve, for example, an externally accessible IP address
> or DNS hostname. This will ensure all links from the Mesos console work
> correctly.
>
> The problem, i guess, is that the set of floating iPs 10.250.0.xxx is not
> externally accessible.
> In my other deployment i have set the floating IPs in these files and all is
> perfectly working, but in that case i have used externally reachable IPs.
>
> 2016-06-11 22:51 GMT+02:00 Erik Weathers :
>>
>> It depends on your setup.  I would probably not set the hostname and
>> instead set the "--no-hostname_lookup" flag.  I'm not sure how you do that
>> with the file-based configuration style you are using.
>>
>> % mesos-master --help
>> ...
>>
>>   --hostname=VALUE  The hostname the master should advertise
>> in ZooKeeper.
>> If left unset, the
>> hostname is resolved from the IP address
>> that the slave binds to;
>> unless the user explicitly prevents
>> that, using
>> `--no-hostname_lookup`, in which case the IP itself
>> is used.
>>
>> On Sat, Jun 11, 2016 at 1:27 PM, Stefano Bianchi 
>> wrote:
>>>
>>> So Erik do you suggest to use the 192.* IP in both
>>> /etc/mesos-master/hostname nad /etc/mesos-master/ip right?
>>>
>>> Il 11/giu/2016 22:15, "Erik Weathers"  ha scritto:

 Yeah, so there is no 10.x address on the box.  Thus you cannot bind
 Mesos to listen to that address.   You need to use one of the 192.* IPs for
 Mesos to bind to.  I'm not sure why you say you need to use the 10.x
 addresses for the UI, that sounds like a problem you should tackle *after*
 getting Mesos up.

 - Erik

 P.S., when using gmail in chrome, you can avoid those extraneous
 newlines when you paste by holding "Shift" along with the Command-V (at
 least on Mac OS X!).

 On Sat, Jun 11, 2016 at 1:06 PM, Stefano Bianchi 
 wrote:
>
> ifconfig -a
>
> eth0: flags=4163  mtu 1454
>
> inet 192.168.100.3  netmask 255.255.255.0  broadcast
> 192.168.100.255
>
> inet6 fe80::f816:3eff:fe1c:a3bf  prefixlen 64  scopeid
> 0x20
>
> ether fa:16:3e:1c:a3:bf  txqueuelen 1000  (Ethernet)
>
> RX packets 61258  bytes 4686426 (4.4 MiB)
>
> RX errors 0  dropped 0  overruns 0  frame 0
>
> TX packets 40537  bytes 3603100 (3.4 MiB)
>
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
>
> lo: flags=73  mtu 65536
>
> inet 127.0.0.1  netmask 255.0.0.0
>
> inet6 ::1  prefixlen 128  scopeid 0x10
>
> loop  txqueuelen 0  (Local Loopback)
>
> RX packets 28468  bytes 1672684 (1.5 MiB)
>
> RX errors 0  dropped 0  overruns 0  frame 0
>
> TX packets 28468  bytes 1672684 (1.5 MiB)
>
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
>
>
> ip addr:1: lo:  mtu 65536 qdisc noqueue state
> UNKNOWN
>
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>
> inet 127.0.0.1/8 scope host lo
>
>valid_lft forever preferred_lft forever
>
> inet6 ::1/128 scope host
>
>valid_lft forever preferred_lft forever
>
> 2: eth0:  mtu 1454 qdisc pfifo_fast
> state UP qlen 1000
>
> link/ether fa:16:3e:1c:a3:bf brd ff:ff:ff:ff:ff:ff
>
> inet 192.168.100.3/24 brd 192.168.100.255 scope global dynamic eth0
>
>valid_lft 77537sec preferred_lft 77537sec
>
> inet6 fe80::f816:3eff:fe1c:a3bf/64 scope link
>
>valid_lft forever preferred_lft forever
>
>
> 2016-06-11 20:05 GMT+02:00 haosdent :
>>
>> As @Erik said, what is your `ifconfig` or `ip addr` command output?
>>
>> On Sun, Jun 12, 2016 at 2:00 AM, Stefano Bianchi
>>  wrote:
>>>
>>> the result of your command give this:
>>>
>>> [root@master ~]# nc 

Re: Mesos 0.28.2 does not start

[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., 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 Bianchi 
> wrote:
>
>> the problem is presented also on 0.27.2 i tried to perform a yum
>> downgrade mesos-0.27.2 and i still have this problem. i don't understand
>> why. i followed the common procedure as for my previous work.
>>
>> 2016-06-11 19:30 GMT+02:00 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

 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 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
>>  and 10.250.0.126
>> 
>>
>> 2016-06-11 19:13 GMT+02:00 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 GMT+02:00 haosdent :
>>>
 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 :
>
>> 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
>>> 

Re: Mesos 0.28.2 does not start

[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 Bianchi 
wrote:

> the problem is presented also on 0.27.2 i tried to perform a yum downgrade
> mesos-0.27.2 and i still have this problem. i don't understand why. i
> followed the common procedure as for my previous work.
>
> 2016-06-11 19:30 GMT+02:00 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
>>>
>>> 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 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
>  and 10.250.0.126 
>
> 2016-06-11 19:13 GMT+02:00 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 GMT+02:00 haosdent :
>>
>>> 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 :

> 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 

Re: Mesos 0.28.2 does not start

[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
>
> 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 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
>>>  and 10.250.0.126 
>>>
>>> 2016-06-11 19:13 GMT+02:00 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 GMT+02:00 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
>>
>> 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 :
>>
>>> 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 

Re: Mesos 0.28.2 does not start

[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 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
>>  and 10.250.0.126 
>>
>> 2016-06-11 19:13 GMT+02:00 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 GMT+02:00 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
>
> 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 :
>
>> 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*
>>>
>>> 

Re: Mesos 0.28.2 does not start

[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
>  and 10.250.0.126 
>
> 2016-06-11 19:13 GMT+02:00 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 GMT+02:00 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

 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 :

> 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 

Re: Mesos 0.28.2 does not start

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

Re: Mesos 0.28.2 does not start

[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 GMT+02:00 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
>>
>> 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 :
>>
>>> 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 
>>> 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 

Re: Mesos 0.28.2 does not start

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

Re: Mesos 0.28.2 does not start

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

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

Re: Mesos 0.28.2 does not start

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

Re: Mesos 0.28.2 does not start

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

Re: Mesos 0.28.2 does not start

[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 service, use: journalctl -u
mesos-master


On Fri, Jun 10, 2016 at 9:45 AM, Stefano Bianchi 
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 :
>
>> 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, 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.
>>
>>
>

Re: Mesos 0.28.2 does not start

[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!
>
> 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, 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.
>
>

Re: Mesos 0.28.2 does not start

[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 AM, Jie Yu  wrote:

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

Re: Mesos 0.28.2 does not start

[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, 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.

Mesos 0.28.2 does not start

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