mesos-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Avinash Sridharan <avin...@mesosphere.io>
Subject Re: [VOTE] Release Apache Mesos 0.28.0 (rc1)
Date Sun, 06 Mar 2016 08:11:07 GMT
Looks like this issue is not a regression. I can see the same crash on
Debian 8 running on AWS with 0.27.2-rc1 .

The root cause is that the cgroups memory subsystem was disabled. Enabled
it at boot up and all root test cases passed.

BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64
root=UUID=5cfc0e59-b149-4ddc-8741-74bd7e71f91c ro init=/bin/systemd
console=hvc0 console=ttyS0 cgroup_enable=memory

I think the test filters should have caught the absence of the cgroup
memory subsystem. If I can't find a JIRA for this, will go ahead and file
one.



On Fri, Mar 4, 2016 at 6:52 PM, Avinash Sridharan <avinash@mesosphere.io>
wrote:

> Sorry,
> Forgot to mention the platform details. Seeing the crash on Debian 8
> dmin@ip-172-31-26-151:~/mesos/build$ cat /etc/issue
> Debian GNU/Linux 8 \n \l
>
> admin@ip-172-31-26-151:~/mesos/build$ uname -a
> Linux ip-172-31-26-151 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u3
> (2016-01-17) x86_64 GNU/Linux
>
> On Fri, Mar 4, 2016 at 6:49 PM, Avinash Sridharan <avinash@mesosphere.io>
> wrote:
>
>> I am seeing the following crash when I run mesos build of 0.28.0-rc1
>> `sudo bin/mesos-tests.sh` :
>> [ RUN      ] MemIsolatorTest/1.MemUsage
>> F0305 02:43:01.791003 32494 isolator_tests.cpp:905] CHECK_SOME(isolator):
>> Failed to create memory cgroup: Failed to mount cg
>> roups hierarchy at '/sys/fs/cgroup/memory': 'memory' is not enabled by
>> the kernel
>> *** Check failure stack trace: ***
>>     @     0x7fc4630a025d  google::LogMessage::Fail()
>>     @     0x7fc46309f63e  google::LogMessage::SendToLog()
>>     @     0x7fc46309ff1d  google::LogMessage::Flush()
>>     @     0x7fc4630a3388  google::LogMessageFatal::~LogMessageFatal()
>>     @           0x8bed57  _CheckFatal::~_CheckFatal()
>>     @          0x17c0ab7
>>  mesos::internal::tests::MemIsolatorTest_MemUsage_Test<>::TestBody()
>>     @          0x1985243
>>  testing::internal::HandleSehExceptionsInMethodIfSupported<>()
>>     @          0x1971d31
>>  testing::internal::HandleExceptionsInMethodIfSupported<>()
>>     @          0x1952a55  testing::Test::Run()
>>     @          0x19536cb  testing::TestInfo::Run()
>>     @          0x1953dd7  testing::TestCase::Run()
>>     @          0x195b4ce  testing::internal::UnitTestImpl::RunAllTests()
>>     @          0x19825d3
>>  testing::internal::HandleSehExceptionsInMethodIfSupported<>()
>>     @          0x1973d01
>>  testing::internal::HandleExceptionsInMethodIfSupported<>()
>>     @          0x195b18b  testing::UnitTest::Run()
>>     @           0xe43611  RUN_ALL_TESTS()
>>     @           0xe424dc  main
>>     @     0x7fc45e147b45  (unknown)
>>     @           0x8a0bbc  (unknown)
>>
>>
>> Looks like the memory cgroup memory is disabled:
>>
>> admin@ip-172-31-26-151:~/mesos/build$ cat /proc/cgroups
>> #subsys_name    hierarchy       num_cgroups     enabled
>> cpuset  2       1       1
>> cpu     3       2       1
>> cpuacct 3       2       1
>> memory  0       1       0
>> devices 4       1       1
>> freezer 5       2       1
>> net_cls 6       1       1
>>
>> But I thought the test filters should have caught this ?
>>
>> On Fri, Mar 4, 2016 at 1:52 PM, Kapil Arya <kapil@mesosphere.io> wrote:
>>
>>> +1 (Binding)
>>>
>>> Successful CI builds for the following distros:
>>>
>>> amd64/centos/6
>>> amd64/centos/7
>>> amd64/debian/jessie
>>> amd64/ubuntu/precise
>>> amd64/ubuntu/trusty
>>> amd64/ubuntu/vivid
>>>
>>>
>>> On Fri, Mar 4, 2016 at 1:06 PM, Vinod Kone <vinodkone@apache.org> wrote:
>>>
>>>> Bad copy paste into the email, sorry. It looks fine in the CHANGELOG.
>>>>
>>>> On Fri, Mar 4, 2016 at 12:52 AM, Shuai Lin <linshuai2012@gmail.com>
>>>> wrote:
>>>>
>>>> >   * [MESOS-4712] - Remove 'force' field from the Subscribe Call in v1
>>>> >> Scheduler API.
>>>> >>   * [MESOS-4591] - Change the object of ReserveResources and
>>>> CreateVolume
>>>> >> ACLs to `roles`.
>>>> >>   * [MESOS-4712] - Remove 'force' field from the Subscribe Call
in v1
>>>> >> Scheduler API.
>>>> >
>>>> >
>>>> > MESOS-4712 is included twice.
>>>> >
>>>> > On Fri, Mar 4, 2016 at 1:25 PM, Vinod Kone <vinodkone@apache.org>
>>>> wrote:
>>>> >
>>>> >> On Thu, Mar 3, 2016 at 5:43 PM, Vinod Kone <vinodkone@apache.org>
>>>> wrote:
>>>> >>
>>>> >> > Tue Mar  10 17:00:00 PST 2016
>>>> >>
>>>> >>
>>>> >> Sorry. This should be Mar 8th not 10th.
>>>> >>
>>>> >
>>>> >
>>>>
>>>
>>>
>>
>>
>> --
>> Avinash Sridharan, Mesosphere
>> +1 (323) 702 5245
>>
>
>
>
> --
> Avinash Sridharan, Mesosphere
> +1 (323) 702 5245
>



-- 
Avinash Sridharan, Mesosphere
+1 (323) 702 5245

Mime
View raw message