.@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 whe
<
> 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 Er
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
>
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
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
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
sos-master[1156]: *WARNING:
>>>>>>>>>>> Logging before InitGoogleLogging() is written to STDERR*
>>>>>>>>>>>
>>>>>>>>>>> giu 09 23:25:35 master.novalocal mesos-master[1156]: *F0609
>>>>>
gt;
>>>>>>>>>> giu 09 23:25:35 master.novalocal mesos-master[1156]: **** Check
>>>>>>>>>> failure stack trace:
>>>>>>>>>>
>>>>>>>>>> giu 09 23:25:35 master.novalocal system
ng restart.
>>>>>>>>
>>>>>>>> giu 09 23:25:55 master.novalocal systemd[1]: Started Mesos Master.
>>>>>>>>
>>>>>>>> giu 09 23:25:55 master.novalocal systemd[1]: Starting Mesos
>>>>>>
re 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
&g
ode=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.
*
>>>>>
>>>>> 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.
>>>>>
&
ng() 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
=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.*
>>>
>
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,
t;> 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>:
>>>
>>>>
t 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 chrono
rote:
>>
>> 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
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
g 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
>
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-ma
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
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
ll 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 importa
taj...@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 libmeso
t; 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
> &
bmesos-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 fou
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+0
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-doc
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
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 fixe
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
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
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.
>>
>>
elow:
> > [19:05:43][Step 10/10] [ FAILED ]
> > LinuxFilesystemIsolatorTest.ROOT_MultipleContainers
> >
> > Centos 7 - SSL
> >
> >
> ---
> > [19:04:53][
>
> 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 ]
&g
+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=
+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
t;
> 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...@um
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
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
gt;> 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
>>>
>>
>>
>
ule, 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
>>
>
>
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 in
gt;>> @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.
g 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
>
d 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:
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
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
49 matches
Mail list logo