Re: Master pailer failure 0.28.2

[Benjamin Mahler]

Hard to interpret the error message, it looks like it's pointing to our
$scope variables 'offered_cpus' and 'idle_cpus'.

Is the error consistent? When you say you get this error with the pailer,
what does that mean? You see this in the pailer window? In your browser
console after you click on the pailer? Something else?

On Tue, Aug 9, 2016 at 11:19 AM, haosdent <haosd...@gmail.com> wrote:

> Hi, @Charles Allen I use 1.0.0 and it looks fine in my master. Does it
> happen after you refresh?
>
> On Wed, Aug 10, 2016 at 1:31 AM, Charles Allen <
> charles.al...@metamarkets.com> wrote:
>
>> Slave pailer is working fine
>>
>> On Tue, Aug 9, 2016 at 10:29 AM Charles Allen <
>> charles.al...@metamarkets.com> wrote:
>>
>>> For some reason I started getting the following failure on 0.28.2 with
>>> the pailer when trying to view master logs from the master console
>>> (REDACTED is the ip address):
>>>
>>>
>>> angular-1.2.3.min.js:84 Error: [$interpolate:interr]
>>> http://errors.angularjs.org/1.2.3/$interpolate/interr?p0=%7B
>>> %7Boffered_cpus…7D=TypeError%3A%20Cannot%20read%20propert
>>> y%20'toFixed'%20of%20undefined
>>> at Error (native)
>>> at http://REDACTED:5050/static/js/angular-1.2.3.min.js:6:449
>>> at Object.s (http://REDACTED:5050/static/j
>>> s/angular-1.2.3.min.js:73:495)
>>> at f.$digest (http://REDACTED:5050/static/j
>>> s/angular-1.2.3.min.js:99:14)
>>> at f.$apply (http://REDACTED:5050/static/j
>>> s/angular-1.2.3.min.js:101:369)
>>> at f (http://REDACTED:5050/static/js/angular-1.2.3.min.js:67:175)
>>> at Q (http://REDACTED:5050/static/js/angular-1.2.3.min.js:71:99)
>>> at XMLHttpRequest.y.onreadystatechange (
>>> http://REDACTED:5050/static/js/angular-1.2.3.min.js:72:130)(anonymous
>>> function) @ angular-1.2.3.min.js:84(anonymous function) @
>>> angular-1.2.3.min.js:62s @ angular-1.2.3.min.js:74$digest @
>>> angular-1.2.3.min.js:99$apply @ angular-1.2.3.min.js:101f @
>>> angular-1.2.3.min.js:67Q @ angular-1.2.3.min.js:71y.onreadystatechange
>>> @ angular-1.2.3.min.js:72
>>> angular-1.2.3.min.js:84 Error: [$interpolate:interr]
>>> http://errors.angularjs.org/1.2.3/$interpolate/interr?p0=%7B
>>> %7Bidle_cpus%20…7D=TypeError%3A%20Cannot%20read%20propert
>>> y%20'toFixed'%20of%20undefined
>>> at Error (native)
>>> at http://REDACTED:5050/static/js/angular-1.2.3.min.js:6:449
>>> at Object.s (http://REDACTED:5050/static/j
>>> s/angular-1.2.3.min.js:73:495)
>>> at f.$digest (http://REDACTED:5050/static/j
>>> s/angular-1.2.3.min.js:99:14)
>>> at f.$apply (http://REDACTED:5050/static/j
>>> s/angular-1.2.3.min.js:101:369)
>>> at f (http://REDACTED:5050/static/js/angular-1.2.3.min.js:67:175)
>>> at Q (http://REDACTED:5050/static/js/angular-1.2.3.min.js:71:99)
>>> at XMLHttpRequest.y.onreadystatechange (
>>> http://REDACTED:5050/static/js/angular-1.2.3.min.js:72:130)(anonymous
>>> function) @ angular-1.2.3.min.js:84(anonymous function) @
>>> angular-1.2.3.min.js:62s @ angular-1.2.3.min.js:74$digest @
>>> angular-1.2.3.min.js:99$apply @ angular-1.2.3.min.js:101f @
>>> angular-1.2.3.min.js:67Q @ angular-1.2.3.min.js:71y.onreadystatechange
>>> @ angular-1.2.3.min.js:72
>>>
>>>
>>> Has anyone seen this before?
>>>
>>
>
>
> --
> Best Regards,
> Haosdent Huang
>

Re: Master pailer failure 0.28.2

[haosdent]

Hi, @Charles Allen I use 1.0.0 and it looks fine in my master. Does it
happen after you refresh?

On Wed, Aug 10, 2016 at 1:31 AM, Charles Allen <
charles.al...@metamarkets.com> wrote:

> Slave pailer is working fine
>
> On Tue, Aug 9, 2016 at 10:29 AM Charles Allen <
> charles.al...@metamarkets.com> wrote:
>
>> For some reason I started getting the following failure on 0.28.2 with
>> the pailer when trying to view master logs from the master console
>> (REDACTED is the ip address):
>>
>>
>> angular-1.2.3.min.js:84 Error: [$interpolate:interr]
>> http://errors.angularjs.org/1.2.3/$interpolate/interr?p0=%
>> 7B%7Boffered_cpus…7D=TypeError%3A%20Cannot%20read%
>> 20property%20'toFixed'%20of%20undefined
>> at Error (native)
>> at http://REDACTED:5050/static/js/angular-1.2.3.min.js:6:449
>> at Object.s (http://REDACTED:5050/static/
>> js/angular-1.2.3.min.js:73:495)
>> at f.$digest (http://REDACTED:5050/static/
>> js/angular-1.2.3.min.js:99:14)
>> at f.$apply (http://REDACTED:5050/static/js/angular-1.2.3.min.js:101:
>> 369)
>> at f (http://REDACTED:5050/static/js/angular-1.2.3.min.js:67:175)
>> at Q (http://REDACTED:5050/static/js/angular-1.2.3.min.js:71:99)
>> at XMLHttpRequest.y.onreadystatechange (http://REDACTED:5050/static/
>> js/angular-1.2.3.min.js:72:130)(anonymous function) @
>> angular-1.2.3.min.js:84(anonymous function) @ angular-1.2.3.min.js:62s @
>> angular-1.2.3.min.js:74$digest @ angular-1.2.3.min.js:99$apply @
>> angular-1.2.3.min.js:101f @ angular-1.2.3.min.js:67Q @
>> angular-1.2.3.min.js:71y.onreadystatechange @ angular-1.2.3.min.js:72
>> angular-1.2.3.min.js:84 Error: [$interpolate:interr]
>> http://errors.angularjs.org/1.2.3/$interpolate/interr?p0=%
>> 7B%7Bidle_cpus%20…7D=TypeError%3A%20Cannot%20read%
>> 20property%20'toFixed'%20of%20undefined
>> at Error (native)
>> at http://REDACTED:5050/static/js/angular-1.2.3.min.js:6:449
>> at Object.s (http://REDACTED:5050/static/
>> js/angular-1.2.3.min.js:73:495)
>> at f.$digest (http://REDACTED:5050/static/
>> js/angular-1.2.3.min.js:99:14)
>> at f.$apply (http://REDACTED:5050/static/js/angular-1.2.3.min.js:101:
>> 369)
>> at f (http://REDACTED:5050/static/js/angular-1.2.3.min.js:67:175)
>> at Q (http://REDACTED:5050/static/js/angular-1.2.3.min.js:71:99)
>> at XMLHttpRequest.y.onreadystatechange (http://REDACTED:5050/static/
>> js/angular-1.2.3.min.js:72:130)(anonymous function) @
>> angular-1.2.3.min.js:84(anonymous function) @ angular-1.2.3.min.js:62s @
>> angular-1.2.3.min.js:74$digest @ angular-1.2.3.min.js:99$apply @
>> angular-1.2.3.min.js:101f @ angular-1.2.3.min.js:67Q @
>> angular-1.2.3.min.js:71y.onreadystatechange @ angular-1.2.3.min.js:72
>>
>>
>> Has anyone seen this before?
>>
>


-- 
Best Regards,
Haosdent Huang

Re: Master pailer failure 0.28.2

[Charles Allen]

Slave pailer is working fine

On Tue, Aug 9, 2016 at 10:29 AM Charles Allen <charles.al...@metamarkets.com>
wrote:

> For some reason I started getting the following failure on 0.28.2 with the
> pailer when trying to view master logs from the master console (REDACTED is
> the ip address):
>
>
> angular-1.2.3.min.js:84 Error: [$interpolate:interr]
> http://errors.angularjs.org/1.2.3/$interpolate/interr?p0=%7B%7Boffered_cpus
> …7D=TypeError%3A%20Cannot%20read%20property%20'toFixed'%20of%20undefined
> at Error (native)
> at http://REDACTED:5050/static/js/angular-1.2.3.min.js:6:449
> at Object.s (
> http://REDACTED:5050/static/js/angular-1.2.3.min.js:73:495)
> at f.$digest (
> http://REDACTED:5050/static/js/angular-1.2.3.min.js:99:14)
> at f.$apply (
> http://REDACTED:5050/static/js/angular-1.2.3.min.js:101:369)
> at f (http://REDACTED:5050/static/js/angular-1.2.3.min.js:67:175)
> at Q (http://REDACTED:5050/static/js/angular-1.2.3.min.js:71:99)
> at XMLHttpRequest.y.onreadystatechange (
> http://REDACTED:5050/static/js/angular-1.2.3.min.js:72:130)(anonymous
> function) @ angular-1.2.3.min.js:84(anonymous function) @
> angular-1.2.3.min.js:62s @ angular-1.2.3.min.js:74$digest @
> angular-1.2.3.min.js:99$apply @ angular-1.2.3.min.js:101f @
> angular-1.2.3.min.js:67Q @ angular-1.2.3.min.js:71y.onreadystatechange @
> angular-1.2.3.min.js:72
> angular-1.2.3.min.js:84 Error: [$interpolate:interr]
> http://errors.angularjs.org/1.2.3/$interpolate/interr?p0=%7B%7Bidle_cpus%20
> …7D=TypeError%3A%20Cannot%20read%20property%20'toFixed'%20of%20undefined
> at Error (native)
> at http://REDACTED:5050/static/js/angular-1.2.3.min.js:6:449
> at Object.s (
> http://REDACTED:5050/static/js/angular-1.2.3.min.js:73:495)
> at f.$digest (
> http://REDACTED:5050/static/js/angular-1.2.3.min.js:99:14)
> at f.$apply (
> http://REDACTED:5050/static/js/angular-1.2.3.min.js:101:369)
> at f (http://REDACTED:5050/static/js/angular-1.2.3.min.js:67:175)
> at Q (http://REDACTED:5050/static/js/angular-1.2.3.min.js:71:99)
> at XMLHttpRequest.y.onreadystatechange (
> http://REDACTED:5050/static/js/angular-1.2.3.min.js:72:130)(anonymous
> function) @ angular-1.2.3.min.js:84(anonymous function) @
> angular-1.2.3.min.js:62s @ angular-1.2.3.min.js:74$digest @
> angular-1.2.3.min.js:99$apply @ angular-1.2.3.min.js:101f @
> angular-1.2.3.min.js:67Q @ angular-1.2.3.min.js:71y.onreadystatechange @
> angular-1.2.3.min.js:72
>
>
> Has anyone seen this before?
>

Master pailer failure 0.28.2

[Charles Allen]

For some reason I started getting the following failure on 0.28.2 with the
pailer when trying to view master logs from the master console (REDACTED is
the ip address):


angular-1.2.3.min.js:84 Error: [$interpolate:interr]
http://errors.angularjs.org/1.2.3/$interpolate/interr?p0=%7B%7Boffered_cpus
…7D=TypeError%3A%20Cannot%20read%20property%20'toFixed'%20of%20undefined
at Error (native)
at http://REDACTED:5050/static/js/angular-1.2.3.min.js:6:449
at Object.s (http://REDACTED:5050/static/js/angular-1.2.3.min.js:73:495)
at f.$digest (http://REDACTED:5050/static/js/angular-1.2.3.min.js:99:14)
at f.$apply (http://REDACTED:5050/static/js/angular-1.2.3.min.js:101:369
)
at f (http://REDACTED:5050/static/js/angular-1.2.3.min.js:67:175)
at Q (http://REDACTED:5050/static/js/angular-1.2.3.min.js:71:99)
at XMLHttpRequest.y.onreadystatechange (
http://REDACTED:5050/static/js/angular-1.2.3.min.js:72:130)(anonymous
function) @ angular-1.2.3.min.js:84(anonymous function) @
angular-1.2.3.min.js:62s @ angular-1.2.3.min.js:74$digest @
angular-1.2.3.min.js:99$apply @ angular-1.2.3.min.js:101f @
angular-1.2.3.min.js:67Q @ angular-1.2.3.min.js:71y.onreadystatechange @
angular-1.2.3.min.js:72
angular-1.2.3.min.js:84 Error: [$interpolate:interr]
http://errors.angularjs.org/1.2.3/$interpolate/interr?p0=%7B%7Bidle_cpus%20
…7D=TypeError%3A%20Cannot%20read%20property%20'toFixed'%20of%20undefined
at Error (native)
at http://REDACTED:5050/static/js/angular-1.2.3.min.js:6:449
at Object.s (http://REDACTED:5050/static/js/angular-1.2.3.min.js:73:495)
at f.$digest (http://REDACTED:5050/static/js/angular-1.2.3.min.js:99:14)
at f.$apply (http://REDACTED:5050/static/js/angular-1.2.3.min.js:101:369
)
at f (http://REDACTED:5050/static/js/angular-1.2.3.min.js:67:175)
at Q (http://REDACTED:5050/static/js/angular-1.2.3.min.js:71:99)
at XMLHttpRequest.y.onreadystatechange (
http://REDACTED:5050/static/js/angular-1.2.3.min.js:72:130)(anonymous
function) @ angular-1.2.3.min.js:84(anonymous function) @
angular-1.2.3.min.js:62s @ angular-1.2.3.min.js:74$digest @
angular-1.2.3.min.js:99$apply @ angular-1.2.3.min.js:101f @
angular-1.2.3.min.js:67Q @ angular-1.2.3.min.js:71y.onreadystatechange @
angular-1.2.3.min.js:72


Has anyone seen this before?

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]

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

Re: Mesos 0.28.2 does not start

[Erik Weathers]

gt; 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
>>>>
>>>
>>>
>>
>

Re: Mesos 0.28.2 does not start

[Stefano Bianchi]

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

Re: Mesos 0.28.2 does not start

[Stefano Bianchi]

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

Re: Mesos 0.28.2 does not start

[haosdent]

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

Re: Mesos 0.28.2 does not start

[Stefano Bianchi]

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

Re: Mesos 0.28.2 does not start

[Stefano Bianchi]

ster[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>:
&g

Re: Mesos 0.28.2 does not start

[haosdent]

 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

Re: Mesos 0.28.2 does not start

[Stefano Bianchi]

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

Re: Mesos 0.28.2 does not start

[Joseph Wu]

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

Re: Mesos 0.28.2 does not start

[Stefano Bianchi]

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

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

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

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 <yujie@gmail.com> 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 <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.
>
>

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

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.

Re: 0.28.2 has been released

[Kapil Arya]

Hi All,

The 0.28.2 rpm/deb packages can be found here:
http://open.mesosphere.com/downloads/mesos/#apache-mesos-0.28.2

Best,
Kapil

On Mon, Jun 6, 2016 at 5:21 PM, Kapil Arya <ka...@mesosphere.io> wrote:

> Hi Craig,
>
> I should be sending out a link to the RPM packages in a couple of days.
> (Our packaging scripts had some issues and I am working on fixing them).
>
> Kapil
>
> On Mon, Jun 6, 2016 at 6:15 AM, craig w <codecr...@gmail.com> wrote:
>
>> Jie,
>>
>> Thanks for the updates. When will the packages be available (in
>> particular RPM)?
>>
>> -craig
>>
>> On Sun, Jun 5, 2016 at 2:31 PM, Jie Yu <yujie@gmail.com> wrote:
>>
>>> Hi folks,
>>>
>>> I just released Mesos 0.28.2 and updated the website.
>>>
>>> It includes some important bug fixes. The change log can be found here:
>>>
>>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.28.2
>>>
>>> If you are considering using 0.28, please use 0.28.2!
>>>
>>> Thanks!
>>> - Jie
>>>
>>
>>
>>
>> --
>>
>> https://github.com/mindscratch
>> https://www.google.com/+CraigWickesser
>> https://twitter.com/mind_scratch
>> https://twitter.com/craig_links
>>
>>
>

Re: 0.28.2 has been released

[Kapil Arya]

Hi Craig,

I should be sending out a link to the RPM packages in a couple of days.
(Our packaging scripts had some issues and I am working on fixing them).

Kapil

On Mon, Jun 6, 2016 at 6:15 AM, craig w <codecr...@gmail.com> wrote:

> Jie,
>
> Thanks for the updates. When will the packages be available (in particular
> RPM)?
>
> -craig
>
> On Sun, Jun 5, 2016 at 2:31 PM, Jie Yu <yujie@gmail.com> wrote:
>
>> Hi folks,
>>
>> I just released Mesos 0.28.2 and updated the website.
>>
>> It includes some important bug fixes. The change log can be found here:
>>
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.28.2
>>
>> If you are considering using 0.28, please use 0.28.2!
>>
>> Thanks!
>> - Jie
>>
>
>
>
> --
>
> https://github.com/mindscratch
> https://www.google.com/+CraigWickesser
> https://twitter.com/mind_scratch
> https://twitter.com/craig_links
>
>

Re: 0.28.2 - mesos-docker-executor - libmesos not found

[haosdent]

I encounter this problem before, because some distribution of Linux didn't
add /usr/local/lib in default library search path.
And I try edit /etc/ld.so.conf and to include `/usr/local/lib` then
execute ldconfig in Agent. It works for me.

On Mon, Jun 6, 2016 at 8:47 PM, Kamil Wokitajtis <wokitaj...@gmail.com>
wrote:

> I have solved this issue by adding env variable to marathon app deployment
> json:
>
> "env": {
>   "LD_LIBRARY_PATH" : "/usr/local/lib"
> }
>
> Maybe someone could shed light, why 0.28.2 is unable to locate libmesos
> without exporting LD_LIBRARY_PATH?
>
>
>
> 2016-06-06 14:21 GMT+02:00 Kamil Wokitajtis <wokitaj...@gmail.com>:
>
>> For 0.28.1:
>> root@pltr-app-pl01:~# ldd /usr/local/libexec/mesos/mesos-docker-executor
>> | grep libmesos
>> libmesos-0.28.1.so => /usr/local/lib/libmesos-0.28.1.so
>>  (0x7fbf522b6000)
>>
>> For 0.28.2, as expected, library not found:
>> root@pltr-app-pl02:~# ldd /usr/local/libexec/mesos/mesos-docker-executor
>> | grep libmesos
>> libmesos-0.28.2.so => not found
>>
>> After exporting LD_LIBRARY_PATH, libmesos is found as expected:
>> root@pltr-app-pl02:~# export LD_LIBRARY_PATH=/usr/local/lib
>> root@pltr-app-pl02:~# ldd /usr/local/libexec/mesos/mesos-docker-executor
>> | grep mesos
>> libmesos-0.28.2.so => /usr/local/lib/libmesos-0.28.2.so
>>  (0x7f219a8c1000)
>>
>> Looks like exporting LD_LIBRARY_PATH should help. But exporting this
>> variable in mesos startup scripts doesn't seem to solve issue.
>>
>>
>> 2016-06-06 13:50 GMT+02:00 Guangya Liu <gyliu...@gmail.com>:
>>
>>> You can check what is the output of `ldd mesos-docker-executor` to see
>>> if the libmesos-xxx is in the right location.
>>>
>>> [root@dcos001 mesosphere]# ldd
>>> ./packages/mesos--0335ca0d3700ea88ad8b808f3b1b84d747ed07f0/libexec/mesos/mesos-docker-executor
>>> | grep libmesos
>>> libmesos-0.28.1.so =>
>>> /opt/mesosphere/packages/mesos--0335ca0d3700ea88ad8b808f3b1b84d747ed07f0/lib/
>>> libmesos-0.28.1.so (0x7f5cf1cb1000)
>>>
>>> Thanks,
>>>
>>> Guangya
>>>
>>> On Mon, Jun 6, 2016 at 6:38 PM, Kamil Wokitajtis <wokitaj...@gmail.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I have upgraded my mesos env from 0.28.1 to 0.28.2.
>>>> On 0.28.1 everything worked just fine.
>>>> Now agents are unable to start docker images, mesos throws:
>>>>
>>>> mesos-docker-executor: error while loading shared libraries:
>>>> libmesos-0.28.2.so: cannot open shared object file: No such  file or
>>>> directory
>>>>
>>>> Just like for Mesos 0.28.1 where it works, libmesos-0.28.2 is in
>>>> /usr/local/lib
>>>> There is also symlink libmesos.so -> libmesos-0.28.2.
>>>> /etc/ld.so.conf.d/libc.conf contains /usr/local/lib entry.
>>>> I have also tried exporting LD_LIBRARY_PATH in startup scripts, no luck.
>>>>
>>>> Thanks,
>>>> Kamil
>>>>
>>>>
>>>
>>
>


-- 
Best Regards,
Haosdent Huang

Re: 0.28.2 - mesos-docker-executor - libmesos not found

[Kamil Wokitajtis]

Thanks, that was the case. I wonder why I didn't have to run ldconfig in
the first place after 0.28.1 install.
Anyway, another lesson learnt.

2016-06-06 14:51 GMT+02:00 Stephen Gran <stephen.g...@piksel.com>:

> Hi,
>
> Run ldconfig after install?
>
> Cheers,
>
> On 06/06/16 13:21, Kamil Wokitajtis wrote:
> > For 0.28.1:
> > root@pltr-app-pl01:~# ldd /usr/local/libexec/mesos/mesos-docker-executor
> > | grep libmesos
> > libmesos-0.28.1.so <http://libmesos-0.28.1.so/> =>
> > /usr/local/lib/libmesos-0.28.1.so
> > <http://libmesos-0.28.1.so/> (0x7fbf522b6000)
> >
> > For 0.28.2, as expected, library not found:
> > root@pltr-app-pl02:~# ldd /usr/local/libexec/mesos/mesos-docker-executor
> > | grep libmesos
> > libmesos-0.28.2.so <http://libmesos-0.28.2.so/> => not found
> >
> > After exporting LD_LIBRARY_PATH, libmesos is found as expected:
> > root@pltr-app-pl02:~#export LD_LIBRARY_PATH=/usr/local/lib
> > root@pltr-app-pl02:~# ldd /usr/local/libexec/mesos/mesos-docker-executor
> > | grep mesos
> > libmesos-0.28.2.so <http://libmesos-0.28.2.so/> =>
> > /usr/local/lib/libmesos-0.28.2.so
> > <http://libmesos-0.28.2.so/> (0x7f219a8c1000)
> >
> > Looks like exporting LD_LIBRARY_PATH should help. But exporting this
> > variable in mesos startup scripts doesn't seem to solve issue.
> >
> >
> > 2016-06-06 13:50 GMT+02:00 Guangya Liu <gyliu...@gmail.com
> > <mailto:gyliu...@gmail.com>>:
> >
> > You can check what is the output of `ldd mesos-docker-executor` to
> > see if the libmesos-xxx is in the right location.
> >
> > [root@dcos001 mesosphere]# ldd
> >
>  
> ./packages/mesos--0335ca0d3700ea88ad8b808f3b1b84d747ed07f0/libexec/mesos/mesos-docker-executor
> > | grep libmesos
> > libmesos-0.28.1.so <http://libmesos-0.28.1.so> =>
> >
>  /opt/mesosphere/packages/mesos--0335ca0d3700ea88ad8b808f3b1b84d747ed07f0/lib/
> libmesos-0.28.1.so
> > <http://libmesos-0.28.1.so> (0x7f5cf1cb1000)
> >
> > Thanks,
> >
> > Guangya
> >
> > On Mon, Jun 6, 2016 at 6:38 PM, Kamil Wokitajtis
> > <wokitaj...@gmail.com <mailto:wokitaj...@gmail.com>> wrote:
> >
> > Hi,
> >
> > I have upgraded my mesos env from 0.28.1 to 0.28.2.
> > On 0.28.1 everything worked just fine.
> > Now agents are unable to start docker images, mesos throws:
> >
> > mesos-docker-executor: error while loading shared libraries:
> > libmesos-0.28.2.so <http://libmesos-0.28.2.so/>: cannot open
> > shared object file: No such  file or directory
> >
> > Just like for Mesos 0.28.1 where it works, libmesos-0.28.2 is in
> > /usr/local/lib
> > There is also symlink libmesos.so -> libmesos-0.28.2.
> > /etc/ld.so.conf.d/libc.conf contains /usr/local/lib entry.
> > I have also tried exporting LD_LIBRARY_PATH in startup scripts,
> > no luck.
> >
> > Thanks,
> > Kamil
> >
> >
> >
>
> --
> Stephen Gran
> Senior Technical Architect
>
> picture the possibilities | piksel.com
>

Re: 0.28.2 - mesos-docker-executor - libmesos not found

[Stephen Gran]

Hi,

Run ldconfig after install?

Cheers,

On 06/06/16 13:21, Kamil Wokitajtis wrote:
> For 0.28.1:
> root@pltr-app-pl01:~# ldd /usr/local/libexec/mesos/mesos-docker-executor
> | grep libmesos
> libmesos-0.28.1.so <http://libmesos-0.28.1.so/> =>
> /usr/local/lib/libmesos-0.28.1.so
> <http://libmesos-0.28.1.so/> (0x7fbf522b6000)
>
> For 0.28.2, as expected, library not found:
> root@pltr-app-pl02:~# ldd /usr/local/libexec/mesos/mesos-docker-executor
> | grep libmesos
> libmesos-0.28.2.so <http://libmesos-0.28.2.so/> => not found
>
> After exporting LD_LIBRARY_PATH, libmesos is found as expected:
> root@pltr-app-pl02:~#export LD_LIBRARY_PATH=/usr/local/lib
> root@pltr-app-pl02:~# ldd /usr/local/libexec/mesos/mesos-docker-executor
> | grep mesos
> libmesos-0.28.2.so <http://libmesos-0.28.2.so/> =>
> /usr/local/lib/libmesos-0.28.2.so
> <http://libmesos-0.28.2.so/> (0x7f219a8c1000)
>
> Looks like exporting LD_LIBRARY_PATH should help. But exporting this
> variable in mesos startup scripts doesn't seem to solve issue.
>
>
> 2016-06-06 13:50 GMT+02:00 Guangya Liu <gyliu...@gmail.com
> <mailto:gyliu...@gmail.com>>:
>
> You can check what is the output of `ldd mesos-docker-executor` to
> see if the libmesos-xxx is in the right location.
>
> [root@dcos001 mesosphere]# ldd
> 
> ./packages/mesos--0335ca0d3700ea88ad8b808f3b1b84d747ed07f0/libexec/mesos/mesos-docker-executor
> | grep libmesos
> libmesos-0.28.1.so <http://libmesos-0.28.1.so> =>
> 
> /opt/mesosphere/packages/mesos--0335ca0d3700ea88ad8b808f3b1b84d747ed07f0/lib/libmesos-0.28.1.so
> <http://libmesos-0.28.1.so> (0x7f5cf1cb1000)
>
> Thanks,
>
> Guangya
>
> On Mon, Jun 6, 2016 at 6:38 PM, Kamil Wokitajtis
> <wokitaj...@gmail.com <mailto:wokitaj...@gmail.com>> wrote:
>
> Hi,
>
> I have upgraded my mesos env from 0.28.1 to 0.28.2.
> On 0.28.1 everything worked just fine.
> Now agents are unable to start docker images, mesos throws:
>
> mesos-docker-executor: error while loading shared libraries:
> libmesos-0.28.2.so <http://libmesos-0.28.2.so/>: cannot open
> shared object file: No such  file or directory
>
> Just like for Mesos 0.28.1 where it works, libmesos-0.28.2 is in
> /usr/local/lib
> There is also symlink libmesos.so -> libmesos-0.28.2.
> /etc/ld.so.conf.d/libc.conf contains /usr/local/lib entry.
> I have also tried exporting LD_LIBRARY_PATH in startup scripts,
> no luck.
>
> Thanks,
> Kamil
>
>
>

-- 
Stephen Gran
Senior Technical Architect

picture the possibilities | piksel.com

Re: 0.28.2 - mesos-docker-executor - libmesos not found

[Kamil Wokitajtis]

I have solved this issue by adding env variable to marathon app deployment
json:

"env": {
  "LD_LIBRARY_PATH" : "/usr/local/lib"
}

Maybe someone could shed light, why 0.28.2 is unable to locate libmesos
without exporting LD_LIBRARY_PATH?



2016-06-06 14:21 GMT+02:00 Kamil Wokitajtis <wokitaj...@gmail.com>:

> For 0.28.1:
> root@pltr-app-pl01:~# ldd /usr/local/libexec/mesos/mesos-docker-executor
> | grep libmesos
> libmesos-0.28.1.so => /usr/local/lib/libmesos-0.28.1.so
>  (0x7fbf522b6000)
>
> For 0.28.2, as expected, library not found:
> root@pltr-app-pl02:~# ldd /usr/local/libexec/mesos/mesos-docker-executor
> | grep libmesos
> libmesos-0.28.2.so => not found
>
> After exporting LD_LIBRARY_PATH, libmesos is found as expected:
> root@pltr-app-pl02:~# export LD_LIBRARY_PATH=/usr/local/lib
> root@pltr-app-pl02:~# ldd /usr/local/libexec/mesos/mesos-docker-executor
> | grep mesos
> libmesos-0.28.2.so => /usr/local/lib/libmesos-0.28.2.so
>  (0x7f219a8c1000)
>
> Looks like exporting LD_LIBRARY_PATH should help. But exporting this
> variable in mesos startup scripts doesn't seem to solve issue.
>
>
> 2016-06-06 13:50 GMT+02:00 Guangya Liu <gyliu...@gmail.com>:
>
>> You can check what is the output of `ldd mesos-docker-executor` to see if
>> the libmesos-xxx is in the right location.
>>
>> [root@dcos001 mesosphere]# ldd
>> ./packages/mesos--0335ca0d3700ea88ad8b808f3b1b84d747ed07f0/libexec/mesos/mesos-docker-executor
>> | grep libmesos
>> libmesos-0.28.1.so =>
>> /opt/mesosphere/packages/mesos--0335ca0d3700ea88ad8b808f3b1b84d747ed07f0/lib/
>> libmesos-0.28.1.so (0x7f5cf1cb1000)
>>
>> Thanks,
>>
>> Guangya
>>
>> On Mon, Jun 6, 2016 at 6:38 PM, Kamil Wokitajtis <wokitaj...@gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I have upgraded my mesos env from 0.28.1 to 0.28.2.
>>> On 0.28.1 everything worked just fine.
>>> Now agents are unable to start docker images, mesos throws:
>>>
>>> mesos-docker-executor: error while loading shared libraries:
>>> libmesos-0.28.2.so: cannot open shared object file: No such  file or
>>> directory
>>>
>>> Just like for Mesos 0.28.1 where it works, libmesos-0.28.2 is in
>>> /usr/local/lib
>>> There is also symlink libmesos.so -> libmesos-0.28.2.
>>> /etc/ld.so.conf.d/libc.conf contains /usr/local/lib entry.
>>> I have also tried exporting LD_LIBRARY_PATH in startup scripts, no luck.
>>>
>>> Thanks,
>>> Kamil
>>>
>>>
>>
>

Re: 0.28.2 - mesos-docker-executor - libmesos not found

[Kamil Wokitajtis]

For 0.28.1:
root@pltr-app-pl01:~# ldd /usr/local/libexec/mesos/mesos-docker-executor |
grep libmesos
libmesos-0.28.1.so => /usr/local/lib/libmesos-0.28.1.so
 (0x7fbf522b6000)

For 0.28.2, as expected, library not found:
root@pltr-app-pl02:~# ldd /usr/local/libexec/mesos/mesos-docker-executor |
grep libmesos
libmesos-0.28.2.so => not found

After exporting LD_LIBRARY_PATH, libmesos is found as expected:
root@pltr-app-pl02:~# export LD_LIBRARY_PATH=/usr/local/lib
root@pltr-app-pl02:~# ldd /usr/local/libexec/mesos/mesos-docker-executor |
grep mesos
libmesos-0.28.2.so => /usr/local/lib/libmesos-0.28.2.so
 (0x7f219a8c1000)

Looks like exporting LD_LIBRARY_PATH should help. But exporting this
variable in mesos startup scripts doesn't seem to solve issue.


2016-06-06 13:50 GMT+02:00 Guangya Liu <gyliu...@gmail.com>:

> You can check what is the output of `ldd mesos-docker-executor` to see if
> the libmesos-xxx is in the right location.
>
> [root@dcos001 mesosphere]# ldd
> ./packages/mesos--0335ca0d3700ea88ad8b808f3b1b84d747ed07f0/libexec/mesos/mesos-docker-executor
> | grep libmesos
> libmesos-0.28.1.so =>
> /opt/mesosphere/packages/mesos--0335ca0d3700ea88ad8b808f3b1b84d747ed07f0/lib/
> libmesos-0.28.1.so (0x7f5cf1cb1000)
>
> Thanks,
>
> Guangya
>
> On Mon, Jun 6, 2016 at 6:38 PM, Kamil Wokitajtis <wokitaj...@gmail.com>
> wrote:
>
>> Hi,
>>
>> I have upgraded my mesos env from 0.28.1 to 0.28.2.
>> On 0.28.1 everything worked just fine.
>> Now agents are unable to start docker images, mesos throws:
>>
>> mesos-docker-executor: error while loading shared libraries:
>> libmesos-0.28.2.so: cannot open shared object file: No such  file or
>> directory
>>
>> Just like for Mesos 0.28.1 where it works, libmesos-0.28.2 is in
>> /usr/local/lib
>> There is also symlink libmesos.so -> libmesos-0.28.2.
>> /etc/ld.so.conf.d/libc.conf contains /usr/local/lib entry.
>> I have also tried exporting LD_LIBRARY_PATH in startup scripts, no luck.
>>
>> Thanks,
>> Kamil
>>
>>
>

0.28.2 - mesos-docker-executor - libmesos not found

[Kamil Wokitajtis]

Hi,

I have upgraded my mesos env from 0.28.1 to 0.28.2.
On 0.28.1 everything worked just fine.
Now agents are unable to start docker images, mesos throws:

mesos-docker-executor: error while loading shared libraries:
libmesos-0.28.2.so: cannot open shared object file: No such  file or
directory

Just like for Mesos 0.28.1 where it works, libmesos-0.28.2 is in
/usr/local/lib
There is also symlink libmesos.so -> libmesos-0.28.2.
/etc/ld.so.conf.d/libc.conf contains /usr/local/lib entry.
I have also tried exporting LD_LIBRARY_PATH in startup scripts, no luck.

Thanks,
Kamil

Re: 0.28.2 has been released

[craig w]

Jie,

Thanks for the updates. When will the packages be available (in particular
RPM)?

-craig

On Sun, Jun 5, 2016 at 2:31 PM, Jie Yu <yujie@gmail.com> wrote:

> Hi folks,
>
> I just released Mesos 0.28.2 and updated the website.
>
> It includes some important bug fixes. The change log can be found here:
>
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.28.2
>
> If you are considering using 0.28, please use 0.28.2!
>
> Thanks!
> - Jie
>



-- 

https://github.com/mindscratch
https://www.google.com/+CraigWickesser
https://twitter.com/mind_scratch
https://twitter.com/craig_links

0.28.2 has been released

[Jie Yu]

Hi folks,

I just released Mesos 0.28.2 and updated the website.

It includes some important bug fixes. The change log can be found here:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.28.2

If you are considering using 0.28, please use 0.28.2!

Thanks!
- Jie

[RESULT][VOTE] Release Apache Mesos 0.28.2 (rc1)

[Jie Yu]

Hi all,

The vote for Mesos 0.28.2 (rc1) has passed with the
following votes.

+1 (Binding)
--
Vinod Kone
Till Toenshoff
Kapil Arya

+1 (Non-binding)
--
Guangya Liu
haosdent

There were no 0 or -1 votes.

Please find the release at:
https://dist.apache.org/repos/dist/release/mesos/0.28.2

It is recommended to use a mirror to download the release:
http://www.apache.org/dyn/closer.cgi

The CHANGELOG for the release is available at:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.28.2

The mesos-0.28.2.jar has been released to:
https://repository.apache.org

The website (http://mesos.apache.org) will be updated shortly to reflect
this release.

Thanks,
- Jie

Re: 0.28.2

[June Taylor]

I'm glad to know it will be in 1.0, this would really help us out.


Thanks,
June Taylor
System Administrator, Minnesota Population Center
University of Minnesota

On Sun, May 29, 2016 at 7:44 PM, Guangya Liu <gyliu...@gmail.com> wrote:

> +1 to Jie for this. mesos-execute is hot recently, deferring this to 1.0
> sounds more reasonable.
>
> On Mon, May 30, 2016 at 6:43 AM, Jie Yu <yujie@gmail.com> wrote:
>
>> June, per Vinod's response, we typically only backport bug fixes. This is
>> more like a feature to me as well.
>>
>> However, I did try to backport this patch to 0.28.2, but the patch does
>> not apply cleanly. So I would prefer leaving it. Since we'll be cutting 1.0
>> soon, maybe consider upgrading to 1.0? Thanks!
>>
>> - Jie
>>
>> On Wed, May 25, 2016 at 5:52 AM, June Taylor <j...@umn.edu> wrote:
>>
>>> We recently upgraded to 0.28.1 and were looking for the feature where a
>>> role can be specified to mesos-execute. This didn't seem to make it in. Can
>>> you get that into 0.28.2?
>>>
>>>
>>> Thanks,
>>> June Taylor
>>> System Administrator, Minnesota Population Center
>>> University of Minnesota
>>>
>>> On Tue, May 24, 2016 at 11:04 AM, Jie Yu <yujie@gmail.com> wrote:
>>>
>>>> Hi folks,
>>>>
>>>> According to our release schedule, we should be cutting point release
>>>> for 0.28.x. I volunteer to be the release manager. Vinod and Ben already
>>>> started a branch (0.28.x) in the repo, so it's just a matter of cutting it.
>>>> If you have any patch that you want to backport into 0.28.2, please let me
>>>> know asap. I plan to cut it this Thursday.
>>>>
>>>> Thanks,
>>>> - Jie
>>>>
>>>
>>>
>>
>

Re: [VOTE] Release Apache Mesos 0.28.2 (rc1)

[haosdent]

+1 (no-binding)

Tested on CentOS 7.2 via (make check) except known flaky test cases.

On Tue, May 31, 2016 at 9:30 AM, Kapil Arya <ka...@mesosphere.io> wrote:

> +1 (binding)
>
> Distro package building for Ubuntu, Debian and CentOS. Here is the link to
> the RC downloads page:
>   http://open.mesosphere.com/downloads/mesos-rc/
>
> Best,
> Kapil
>
>
>
> On Mon, May 30, 2016 at 3:17 PM, Till Toenshoff <toensh...@me.com> wrote:
>
> > +1
> >
> > Tested on OSX and various distros via private CI.
> >
> > OSX 10.11.5 (15F34), clang version 3.7.0 (trunk 235831) (llvm/trunk
> > 235813):
> >
> >
> 
> > [--] Global test environment tear-down
> > [==] 1009 tests from 132 test cases ran. (299208 ms total)
> > [  PASSED  ] 1003 tests.
> > [  FAILED  ] 6 tests, listed below:
> > [  FAILED  ] ExamplesTest.TestFramework
> > [  FAILED  ] ExamplesTest.NoExecutorFramework
> > [  FAILED  ] ExamplesTest.JavaFramework
> > [  FAILED  ] ExamplesTest.PythonFramework
> > [  FAILED  ] FetcherCacheTest.LocalUncachedExtract
> > [  FAILED  ] FetcherCacheHttpTest.HttpMixed
> >
> >
> > Debian 8
> >
> >
> ---
> > [19:05:20][Step 10/10] [  PASSED  ] 1126 tests.
> >
> > Debian 8 - SSL
> >
> >
> ---
> > [19:03:47][Step 10/10] [  PASSED  ] 1126 tests.
> >
> >
> > Ubuntu 12
> >
> >
> ---
> > [19:00:36][Step 10/10] [  PASSED  ] 1127 tests.
> >
> > Ubuntu 12 - SSL
> >
> >
> ---
> > [19:01:53][Step 10/10] [  PASSED  ] 1127 tests.
> >
> > Ubuntu 14
> >
> >
> ---
> > [19:01:19][Step 10/10] [  PASSED  ] 1125 tests.
> >
> > Ubuntu 14 - SSL
> >
> >
> ---
> > [19:00:20][Step 10/10] [  PASSED  ] 1125 tests.
> >
> > Ubuntu 15
> >
> >
> ---
> > [19:05:28][Step 10/10] [  PASSED  ] 1128 tests.
> >
> > Ubuntu 15 - SSL
> >
> >
> ---
> > [19:05:58][Step 10/10] [  PASSED  ] 1128 tests.
> >
> >
> > Centos 6
> >
> >
> ---
> > [19:07:27][Step 10/10] [  PASSED  ] 1127 tests.
> > [19:07:27][Step 10/10] [  FAILED  ] 1 test, listed below:
> > [19:07:27][Step 10/10] [  FAILED  ]
> > MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
> >
> > Centos 6 - SSL
> >
> >
> ---
> > [19:07:29][Step 10/10] [  PASSED  ] 1127 tests.
> > [19:07:29][Step 10/10] [  FAILED  ] 1 test, listed below:
> > [19:07:29][Step 10/10] [  FAILED  ]
> > MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
> >
> > Centos 7
> >
> >
> ---
> > [19:05:43][Step 10/10] [  PASSED  ] 1129 tests.
> > [19:05:43][Step 10/10] [  FAILED  ] 1 test, listed below:
> > [19:05:43][Step 10/10] [  FAILED  ]
> > LinuxFilesystemIsolatorTest.ROOT_MultipleContainers
> >
> > Centos 7 - SSL
> >
> >
> ---
> > [19:04:53][Step 10/10] [  PASSED  ] 1129 tests.
> > [19:04:53][Step 10/10] [  FAILED  ] 1 test, listed below:
> > [19:04:53][Step 10/10] [  FAILED  ]
> > LinuxFilesystemIsolatorTest.ROOT_MultipleContainers
> >
> >
> >
> >
> >
> > On May 30, 2016, at 8:23 AM, Vinod Kone <vinodk...@apache.org> wrote:
> >
> > +1 (binding)
> >
> > Tested on ASF CI
> >
> > *Revision*: ceecad69bd9656cf405ca7378ad021c4ad51aaed
>

Re: [VOTE] Release Apache Mesos 0.28.2 (rc1)

[Kapil Arya]

+1 (binding)

Distro package building for Ubuntu, Debian and CentOS. Here is the link to
the RC downloads page:
  http://open.mesosphere.com/downloads/mesos-rc/

Best,
Kapil



On Mon, May 30, 2016 at 3:17 PM, Till Toenshoff <toensh...@me.com> wrote:

> +1
>
> Tested on OSX and various distros via private CI.
>
> OSX 10.11.5 (15F34), clang version 3.7.0 (trunk 235831) (llvm/trunk
> 235813):
>
> 
> [--] Global test environment tear-down
> [==] 1009 tests from 132 test cases ran. (299208 ms total)
> [  PASSED  ] 1003 tests.
> [  FAILED  ] 6 tests, listed below:
> [  FAILED  ] ExamplesTest.TestFramework
> [  FAILED  ] ExamplesTest.NoExecutorFramework
> [  FAILED  ] ExamplesTest.JavaFramework
> [  FAILED  ] ExamplesTest.PythonFramework
> [  FAILED  ] FetcherCacheTest.LocalUncachedExtract
> [  FAILED  ] FetcherCacheHttpTest.HttpMixed
>
>
> Debian 8
>
> ---
> [19:05:20][Step 10/10] [  PASSED  ] 1126 tests.
>
> Debian 8 - SSL
>
> ---
> [19:03:47][Step 10/10] [  PASSED  ] 1126 tests.
>
>
> Ubuntu 12
>
> ---
> [19:00:36][Step 10/10] [  PASSED  ] 1127 tests.
>
> Ubuntu 12 - SSL
>
> ---
> [19:01:53][Step 10/10] [  PASSED  ] 1127 tests.
>
> Ubuntu 14
>
> ---
> [19:01:19][Step 10/10] [  PASSED  ] 1125 tests.
>
> Ubuntu 14 - SSL
>
> ---
> [19:00:20][Step 10/10] [  PASSED  ] 1125 tests.
>
> Ubuntu 15
>
> ---
> [19:05:28][Step 10/10] [  PASSED  ] 1128 tests.
>
> Ubuntu 15 - SSL
>
> ---
> [19:05:58][Step 10/10] [  PASSED  ] 1128 tests.
>
>
> Centos 6
>
> ---
> [19:07:27][Step 10/10] [  PASSED  ] 1127 tests.
> [19:07:27][Step 10/10] [  FAILED  ] 1 test, listed below:
> [19:07:27][Step 10/10] [  FAILED  ]
> MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
>
> Centos 6 - SSL
>
> ---
> [19:07:29][Step 10/10] [  PASSED  ] 1127 tests.
> [19:07:29][Step 10/10] [  FAILED  ] 1 test, listed below:
> [19:07:29][Step 10/10] [  FAILED  ]
> MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
>
> Centos 7
>
> ---
> [19:05:43][Step 10/10] [  PASSED  ] 1129 tests.
> [19:05:43][Step 10/10] [  FAILED  ] 1 test, listed below:
> [19:05:43][Step 10/10] [  FAILED  ]
> LinuxFilesystemIsolatorTest.ROOT_MultipleContainers
>
> Centos 7 - SSL
>
> ---
> [19:04:53][Step 10/10] [  PASSED  ] 1129 tests.
> [19:04:53][Step 10/10] [  FAILED  ] 1 test, listed below:
> [19:04:53][Step 10/10] [  FAILED  ]
> LinuxFilesystemIsolatorTest.ROOT_MultipleContainers
>
>
>
>
>
> On May 30, 2016, at 8:23 AM, Vinod Kone <vinodk...@apache.org> wrote:
>
> +1 (binding)
>
> Tested on ASF CI
>
> *Revision*: ceecad69bd9656cf405ca7378ad021c4ad51aaed
>
>   - refs/tags/0.28.2-rc1
>
> Configuration Matrix gcc clang
> centos:7 --verbose --enable-libevent --enable-ssl
> [image: Success]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/15/COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%3A7,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/
> >
> [image: Not run]
> --verbose
> [image: Success]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/15/COMPILER=gcc,CONFIGURATION=--verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%3A7,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/
> >
> [image: Not run]
> ubuntu:14.04 --verbose --enable-libevent --enable-ssl
> [image: Succes

Re: [VOTE] Release Apache Mesos 0.28.2 (rc1)

[Vinod Kone]

+1 (binding)

Tested on ASF CI

*Revision*: ceecad69bd9656cf405ca7378ad021c4ad51aaed

   - refs/tags/0.28.2-rc1

Configuration Matrix gcc clang
centos:7 --verbose --enable-libevent --enable-ssl
[image: Success]
<https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/15/COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%3A7,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/>
[image: Not run]
--verbose
[image: Success]
<https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/15/COMPILER=gcc,CONFIGURATION=--verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%3A7,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/>
[image: Not run]
ubuntu:14.04 --verbose --enable-libevent --enable-ssl
[image: Success]
<https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/15/COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/>
[image: Success]
<https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/15/COMPILER=clang,CONFIGURATION=--verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/>
--verbose
[image: Success]
<https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/15/COMPILER=gcc,CONFIGURATION=--verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/>
[image: Success]
<https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/15/COMPILER=clang,CONFIGURATION=--verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/>

On Sun, May 29, 2016 at 10:17 PM, Guangya Liu <gyliu...@gmail.com> wrote:

> +1 to this.
>
> Only one minor comment: I saw that there are indeed someone using mesos
> CLI, such as `mesos ps` etc. I did minor enhancement for mesos CLI recently
> to improve debug-ability, it would be great if we can have those in 0.28.2.
>
> The following are the three patches for mesos CLI enhancement:
> https://reviews.apache.org/r/47636/ Fixed some coding error in mesos-ps.
> https://reviews.apache.org/r/47693/ Added more error info for mesos ps.
> https://reviews.apache.org/r/47711/ Added more verbose message when mesos
> command encouter error.
>
> Thanks,
>
> Guangya
>
> On Mon, May 30, 2016 at 7:53 AM, Jie Yu <yujie@gmail.com> wrote:
>
>> Hi all,
>>
>> Please vote on releasing the following candidate as Apache Mesos 0.28.2.
>>
>>
>> 0.28.2 is a bug fix release. It includes the following:
>>
>> 
>> ** Bug
>>   * [MESOS-4705] - Linux 'perf' parsing logic may fail when OS
>> distribution has perf backports.
>>   * [MESOS-5239] - Persistent volume DockerContainerizer support assumes
>> proper mount propagation setup on the host.
>>   * [MESOS-5253] - Isolator cleanup should not be invoked if they are not
>> prepared yet.
>>   * [MESOS-5282] - Destroy container while provisioning volume images may
>> lead to a race.
>>   * [MESOS-5312] - Env `MESOS_SANDBOX` is not set properly for command
>> tasks that changes rootfs.
>>   * [MESOS-4885] - Unzip should force overwrite.
>>   * [MESOS-5449] - Memory leak in SchedulerProcess.declineOffer.
>>   * [MESOS-5380] - Killing a queued task can cause the corresponding
>> command executor to never terminate.
>>
>> ** Improvement
>>   * [MESOS-5307] - Sandbox mounts should not be in the host mount
>> namespace.
>>
>> The CHANGELOG for the release is available at:
>>
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.28.2-rc1
>>
>> 
>>
>> The candidate for Mesos 0.28.2 release is available at:
>>
>> https://dist.apache.org/repos/dist/dev/mesos/0.28.2-rc1/mesos-0.28.2.tar.gz
>>
>> The tag to be voted on is 0.28.2-rc1:
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.28.2-rc1
>>
>> The MD5 checksum of the tarball can be found at:
>>
>> https://dist.apache.org/repos/dist/dev/mesos/0.28.2-rc1/mesos-0.28.2.tar.gz.md5
>>
>> The signature of the tarball can be found at:
>>
>> https://dist.apache.org/repos/dist/dev/mesos/0.28.2-rc1/mesos-0.28.2.tar.gz.asc
>>
>> The PGP key used to sign the release is here:
>> https://dist.apache.org/repos/dist/release/mesos/KEYS
>>
>> The JAR is up in Maven in a staging repository here:
>> https://repository.apache.org/content/repositories/orgapachemesos-1140
>>
>> Please vote on releasing this package as Apache Mesos 0.28.2!
>>
>> The vote is open until Wed Jun  1 16:51:42 PDT 2016 and passes if a
>> majority of at least 3 +1 PMC votes are cast.
>>
>> [ ] +1 Release this package as Apache Mesos 0.28.2
>> [ ] -1 Do not release this package because ...
>>
>> Thanks,
>> - Jie
>>
>
>

Re: [VOTE] Release Apache Mesos 0.28.2 (rc1)

[Guangya Liu]

+1 to this.

Only one minor comment: I saw that there are indeed someone using mesos
CLI, such as `mesos ps` etc. I did minor enhancement for mesos CLI recently
to improve debug-ability, it would be great if we can have those in 0.28.2.

The following are the three patches for mesos CLI enhancement:
https://reviews.apache.org/r/47636/ Fixed some coding error in mesos-ps.
https://reviews.apache.org/r/47693/ Added more error info for mesos ps.
https://reviews.apache.org/r/47711/ Added more verbose message when mesos
command encouter error.

Thanks,

Guangya

On Mon, May 30, 2016 at 7:53 AM, Jie Yu <yujie@gmail.com> wrote:

> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 0.28.2.
>
>
> 0.28.2 is a bug fix release. It includes the following:
>
> 
> ** Bug
>   * [MESOS-4705] - Linux 'perf' parsing logic may fail when OS
> distribution has perf backports.
>   * [MESOS-5239] - Persistent volume DockerContainerizer support assumes
> proper mount propagation setup on the host.
>   * [MESOS-5253] - Isolator cleanup should not be invoked if they are not
> prepared yet.
>   * [MESOS-5282] - Destroy container while provisioning volume images may
> lead to a race.
>   * [MESOS-5312] - Env `MESOS_SANDBOX` is not set properly for command
> tasks that changes rootfs.
>   * [MESOS-4885] - Unzip should force overwrite.
>   * [MESOS-5449] - Memory leak in SchedulerProcess.declineOffer.
>   * [MESOS-5380] - Killing a queued task can cause the corresponding
> command executor to never terminate.
>
> ** Improvement
>   * [MESOS-5307] - Sandbox mounts should not be in the host mount
> namespace.
>
> The CHANGELOG for the release is available at:
>
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.28.2-rc1
>
> ----
>
> The candidate for Mesos 0.28.2 release is available at:
> https://dist.apache.org/repos/dist/dev/mesos/0.28.2-rc1/mesos-0.28.2.tar.gz
>
> The tag to be voted on is 0.28.2-rc1:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.28.2-rc1
>
> The MD5 checksum of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/0.28.2-rc1/mesos-0.28.2.tar.gz.md5
>
> The signature of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/0.28.2-rc1/mesos-0.28.2.tar.gz.asc
>
> The PGP key used to sign the release is here:
> https://dist.apache.org/repos/dist/release/mesos/KEYS
>
> The JAR is up in Maven in a staging repository here:
> https://repository.apache.org/content/repositories/orgapachemesos-1140
>
> Please vote on releasing this package as Apache Mesos 0.28.2!
>
> The vote is open until Wed Jun  1 16:51:42 PDT 2016 and passes if a
> majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Mesos 0.28.2
> [ ] -1 Do not release this package because ...
>
> Thanks,
> - Jie
>

Re: 0.28.2

[Guangya Liu]

+1 to Jie for this. mesos-execute is hot recently, deferring this to 1.0
sounds more reasonable.

On Mon, May 30, 2016 at 6:43 AM, Jie Yu <yujie@gmail.com> wrote:

> June, per Vinod's response, we typically only backport bug fixes. This is
> more like a feature to me as well.
>
> However, I did try to backport this patch to 0.28.2, but the patch does
> not apply cleanly. So I would prefer leaving it. Since we'll be cutting 1.0
> soon, maybe consider upgrading to 1.0? Thanks!
>
> - Jie
>
> On Wed, May 25, 2016 at 5:52 AM, June Taylor <j...@umn.edu> wrote:
>
>> We recently upgraded to 0.28.1 and were looking for the feature where a
>> role can be specified to mesos-execute. This didn't seem to make it in. Can
>> you get that into 0.28.2?
>>
>>
>> Thanks,
>> June Taylor
>> System Administrator, Minnesota Population Center
>> University of Minnesota
>>
>> On Tue, May 24, 2016 at 11:04 AM, Jie Yu <yujie@gmail.com> wrote:
>>
>>> Hi folks,
>>>
>>> According to our release schedule, we should be cutting point release
>>> for 0.28.x. I volunteer to be the release manager. Vinod and Ben already
>>> started a branch (0.28.x) in the repo, so it's just a matter of cutting it.
>>> If you have any patch that you want to backport into 0.28.2, please let me
>>> know asap. I plan to cut it this Thursday.
>>>
>>> Thanks,
>>> - Jie
>>>
>>
>>
>

[VOTE] Release Apache Mesos 0.28.2 (rc1)

[Jie Yu]

Hi all,

Please vote on releasing the following candidate as Apache Mesos 0.28.2.


0.28.2 is a bug fix release. It includes the following:

** Bug
  * [MESOS-4705] - Linux 'perf' parsing logic may fail when OS distribution
has perf backports.
  * [MESOS-5239] - Persistent volume DockerContainerizer support assumes
proper mount propagation setup on the host.
  * [MESOS-5253] - Isolator cleanup should not be invoked if they are not
prepared yet.
  * [MESOS-5282] - Destroy container while provisioning volume images may
lead to a race.
  * [MESOS-5312] - Env `MESOS_SANDBOX` is not set properly for command
tasks that changes rootfs.
  * [MESOS-4885] - Unzip should force overwrite.
  * [MESOS-5449] - Memory leak in SchedulerProcess.declineOffer.
  * [MESOS-5380] - Killing a queued task can cause the corresponding
command executor to never terminate.

** Improvement
  * [MESOS-5307] - Sandbox mounts should not be in the host mount namespace.

The CHANGELOG for the release is available at:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.28.2-rc1


The candidate for Mesos 0.28.2 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/0.28.2-rc1/mesos-0.28.2.tar.gz

The tag to be voted on is 0.28.2-rc1:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.28.2-rc1

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.28.2-rc1/mesos-0.28.2.tar.gz.md5

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.28.2-rc1/mesos-0.28.2.tar.gz.asc

The PGP key used to sign the release is here:
https://dist.apache.org/repos/dist/release/mesos/KEYS

The JAR is up in Maven in a staging repository here:
https://repository.apache.org/content/repositories/orgapachemesos-1140

Please vote on releasing this package as Apache Mesos 0.28.2!

The vote is open until Wed Jun  1 16:51:42 PDT 2016 and passes if a
majority of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 0.28.2
[ ] -1 Do not release this package because ...

Thanks,
- Jie

Re: 0.28.2

[Jie Yu]

June, per Vinod's response, we typically only backport bug fixes. This is
more like a feature to me as well.

However, I did try to backport this patch to 0.28.2, but the patch does not
apply cleanly. So I would prefer leaving it. Since we'll be cutting 1.0
soon, maybe consider upgrading to 1.0? Thanks!

- Jie

On Wed, May 25, 2016 at 5:52 AM, June Taylor <j...@umn.edu> wrote:

> We recently upgraded to 0.28.1 and were looking for the feature where a
> role can be specified to mesos-execute. This didn't seem to make it in. Can
> you get that into 0.28.2?
>
>
> Thanks,
> June Taylor
> System Administrator, Minnesota Population Center
> University of Minnesota
>
> On Tue, May 24, 2016 at 11:04 AM, Jie Yu <yujie@gmail.com> wrote:
>
>> Hi folks,
>>
>> According to our release schedule, we should be cutting point release for
>> 0.28.x. I volunteer to be the release manager. Vinod and Ben already
>> started a branch (0.28.x) in the repo, so it's just a matter of cutting it.
>> If you have any patch that you want to backport into 0.28.2, please let me
>> know asap. I plan to cut it this Thursday.
>>
>> Thanks,
>> - Jie
>>
>
>

Re: 0.28.2

[Jie Yu]

OK, looks like no one volunteer for 0.27.3 and 0.26.2. Therefore, I'll be
the release manager for these two release as well. Will try to cut right
after MesosCon.

- Jie

On Fri, May 27, 2016 at 9:38 AM, Jie Yu <yujie@gmail.com> wrote:

> Any other committers have cycles for point release 0.27.3 and 0.26.2? If
> not, I'll take on it.
>
> - Jie
>
> On Fri, May 27, 2016 at 8:26 AM, Roger Ignazio <rigna...@gmail.com> wrote:
>
>> Hey Jie,
>>
>> Will you also be handling the releases for 0.27.3 and 0.26.2 at the same
>> time? I've been waiting for this particular fix to land:
>> https://issues.apache.org/jira/browse/MESOS-4705.
>>
>> Thanks!
>>
>> -- Roger
>>
>> On Tue, May 24, 2016 at 9:04 AM, Jie Yu <yujie@gmail.com> wrote:
>>
>>> Hi folks,
>>>
>>> According to our release schedule, we should be cutting point release
>>> for 0.28.x. I volunteer to be the release manager. Vinod and Ben already
>>> started a branch (0.28.x) in the repo, so it's just a matter of cutting it.
>>> If you have any patch that you want to backport into 0.28.2, please let me
>>> know asap. I plan to cut it this Thursday.
>>>
>>> Thanks,
>>> - Jie
>>>
>>
>>
>

Re: 0.28.2

[Jie Yu]

Any other committers have cycles for point release 0.27.3 and 0.26.2? If
not, I'll take on it.

- Jie

On Fri, May 27, 2016 at 8:26 AM, Roger Ignazio <rigna...@gmail.com> wrote:

> Hey Jie,
>
> Will you also be handling the releases for 0.27.3 and 0.26.2 at the same
> time? I've been waiting for this particular fix to land:
> https://issues.apache.org/jira/browse/MESOS-4705.
>
> Thanks!
>
> -- Roger
>
> On Tue, May 24, 2016 at 9:04 AM, Jie Yu <yujie@gmail.com> wrote:
>
>> Hi folks,
>>
>> According to our release schedule, we should be cutting point release for
>> 0.28.x. I volunteer to be the release manager. Vinod and Ben already
>> started a branch (0.28.x) in the repo, so it's just a matter of cutting it.
>> If you have any patch that you want to backport into 0.28.2, please let me
>> know asap. I plan to cut it this Thursday.
>>
>> Thanks,
>> - Jie
>>
>
>

Re: 0.28.2

[Roger Ignazio]

Hey Jie,

Will you also be handling the releases for 0.27.3 and 0.26.2 at the same
time? I've been waiting for this particular fix to land:
https://issues.apache.org/jira/browse/MESOS-4705.

Thanks!

-- Roger

On Tue, May 24, 2016 at 9:04 AM, Jie Yu <yujie@gmail.com> wrote:

> Hi folks,
>
> According to our release schedule, we should be cutting point release for
> 0.28.x. I volunteer to be the release manager. Vinod and Ben already
> started a branch (0.28.x) in the repo, so it's just a matter of cutting it.
> If you have any patch that you want to backport into 0.28.2, please let me
> know asap. I plan to cut it this Thursday.
>
> Thanks,
> - Jie
>

Re: 0.28.2

[Vinod Kone]

Looked at the review and the JIRA issue. Not sure why you think it is a
bug? `mesos-execute` only supported the default (*) role before. Now after
the above fix, that role is made configurable. Unless I'm missing
something, I see that as strictly an improvement.

I'm not worried about the cost of backporting this particular fix per se,
I'm more concerned about the precedent and expectations we set around what
can be backported. This is important to keep the overhead on committers
low. Please take a look at our release policy
<http://mesos.apache.org/documentation/latest/versioning/> for further
details.

On Wed, May 25, 2016 at 9:13 AM, June Taylor <j...@umn.edu> wrote:

> Guangya,
>
> Thanks for finding the reference. That is indeed the item I am asking
> about.
>
>
> Thanks,
> June Taylor
> System Administrator, Minnesota Population Center
> University of Minnesota
>
> On Wed, May 25, 2016 at 10:50 AM, Guangya Liu <gyliu...@gmail.com> wrote:
>
>> Hi Vinod,
>>
>> What June requested is actually a bug here
>> https://issues.apache.org/jira/browse/MESOS-4744 , does it make sense to
>> back merge this?
>>
>> Thanks,
>>
>> Guangya
>>
>> On Wed, May 25, 2016 at 10:34 PM, Vinod Kone <vinodk...@gmail.com> wrote:
>>
>>> Patch releases are for bug fixes ugly only. So you have to wait for the
>>> next stable release.
>>>
>>> @vinodkone
>>>
>>> On May 25, 2016, at 5:52 AM, June Taylor <j...@umn.edu> wrote:
>>>
>>> We recently upgraded to 0.28.1 and were looking for the feature where a
>>> role can be specified to mesos-execute. This didn't seem to make it in. Can
>>> you get that into 0.28.2?
>>>
>>>
>>> Thanks,
>>> June Taylor
>>> System Administrator, Minnesota Population Center
>>> University of Minnesota
>>>
>>> On Tue, May 24, 2016 at 11:04 AM, Jie Yu <yujie@gmail.com> wrote:
>>>
>>>> Hi folks,
>>>>
>>>> According to our release schedule, we should be cutting point release
>>>> for 0.28.x. I volunteer to be the release manager. Vinod and Ben already
>>>> started a branch (0.28.x) in the repo, so it's just a matter of cutting it.
>>>> If you have any patch that you want to backport into 0.28.2, please let me
>>>> know asap. I plan to cut it this Thursday.
>>>>
>>>> Thanks,
>>>> - Jie
>>>>
>>>
>>>
>>
>

Re: 0.28.2

[June Taylor]

Guangya,

Thanks for finding the reference. That is indeed the item I am asking about.


Thanks,
June Taylor
System Administrator, Minnesota Population Center
University of Minnesota

On Wed, May 25, 2016 at 10:50 AM, Guangya Liu <gyliu...@gmail.com> wrote:

> Hi Vinod,
>
> What June requested is actually a bug here
> https://issues.apache.org/jira/browse/MESOS-4744 , does it make sense to
> back merge this?
>
> Thanks,
>
> Guangya
>
> On Wed, May 25, 2016 at 10:34 PM, Vinod Kone <vinodk...@gmail.com> wrote:
>
>> Patch releases are for bug fixes ugly only. So you have to wait for the
>> next stable release.
>>
>> @vinodkone
>>
>> On May 25, 2016, at 5:52 AM, June Taylor <j...@umn.edu> wrote:
>>
>> We recently upgraded to 0.28.1 and were looking for the feature where a
>> role can be specified to mesos-execute. This didn't seem to make it in. Can
>> you get that into 0.28.2?
>>
>>
>> Thanks,
>> June Taylor
>> System Administrator, Minnesota Population Center
>> University of Minnesota
>>
>> On Tue, May 24, 2016 at 11:04 AM, Jie Yu <yujie@gmail.com> wrote:
>>
>>> Hi folks,
>>>
>>> According to our release schedule, we should be cutting point release
>>> for 0.28.x. I volunteer to be the release manager. Vinod and Ben already
>>> started a branch (0.28.x) in the repo, so it's just a matter of cutting it.
>>> If you have any patch that you want to backport into 0.28.2, please let me
>>> know asap. I plan to cut it this Thursday.
>>>
>>> Thanks,
>>> - Jie
>>>
>>
>>
>

Re: 0.28.2

[Vinod Kone]

Patch releases are for bug fixes ugly only. So you have to wait for the next 
stable release. 

@vinodkone

> On May 25, 2016, at 5:52 AM, June Taylor <j...@umn.edu> wrote:
> 
> We recently upgraded to 0.28.1 and were looking for the feature where a role 
> can be specified to mesos-execute. This didn't seem to make it in. Can you 
> get that into 0.28.2?
> 
> 
> Thanks,
> June Taylor
> System Administrator, Minnesota Population Center
> University of Minnesota
> 
>> On Tue, May 24, 2016 at 11:04 AM, Jie Yu <yujie@gmail.com> wrote:
>> Hi folks,
>> 
>> According to our release schedule, we should be cutting point release for 
>> 0.28.x. I volunteer to be the release manager. Vinod and Ben already started 
>> a branch (0.28.x) in the repo, so it's just a matter of cutting it. If you 
>> have any patch that you want to backport into 0.28.2, please let me know 
>> asap. I plan to cut it this Thursday.
>> 
>> Thanks,
>> - Jie
> 

Re: 0.28.2

[June Taylor]

We recently upgraded to 0.28.1 and were looking for the feature where a
role can be specified to mesos-execute. This didn't seem to make it in. Can
you get that into 0.28.2?


Thanks,
June Taylor
System Administrator, Minnesota Population Center
University of Minnesota

On Tue, May 24, 2016 at 11:04 AM, Jie Yu <yujie@gmail.com> wrote:

> Hi folks,
>
> According to our release schedule, we should be cutting point release for
> 0.28.x. I volunteer to be the release manager. Vinod and Ben already
> started a branch (0.28.x) in the repo, so it's just a matter of cutting it.
> If you have any patch that you want to backport into 0.28.2, please let me
> know asap. I plan to cut it this Thursday.
>
> Thanks,
> - Jie
>

0.28.2

[Jie Yu]

Hi folks,

According to our release schedule, we should be cutting point release for
0.28.x. I volunteer to be the release manager. Vinod and Ben already
started a branch (0.28.x) in the repo, so it's just a matter of cutting it.
If you have any patch that you want to backport into 0.28.2, please let me
know asap. I plan to cut it this Thursday.

Thanks,
- Jie