Re: Build on Amazon Linux

2014-09-26 Thread Dick Davies
What version of docker does that give you, out of interest?


mainline EL7 is still shipping a pre-1.0 that won't work with mesos
(although since docker is just a static Go binary, it's trivial to overwrite
/usr/bin/docker and get everything to work).


On 25 September 2014 20:23, John Mickey j...@pithoslabs.com wrote:
 Thanks to all for the help

 Tim - thanks for pointing out the obvious
 CCAAT - Great article

 Here are the instructions for getting Mesos to run on Amazon Linux
 amzn-ami-hvm-2014.03.1.x86_64-ebs (ami-383a5008) (us-west-2)

 On a single instance, as root, proof of concept setup

 Install Docker
 yum -y docker
 service docker start

 Install Tools to build Mesos (From Apache Mesos documentation)
 yum -y groupinstall Development Tools
 yum -y install python-devel java-1.7.0-openjdk-devel zlib-devel
 libcurl-devel openssl-devel cyrus-sasl-devel cyrus-sasl-md5
 wget 
 http://mirror.nexcess.net/apache/maven/maven-3/3.0.5/binaries/apache-maven-3.0.5-bin.tar.gz
 tar -zxf apache-maven-3.0.5-bin.tar.gz -C /opt/
 ln -s /opt/apache-maven-3.0.5/bin/mvn /usr/bin/mvn

 Install Oracle Java (Amazon Linux ships with OpenJDK)
 wget --no-check-certificate --no-cookies --header Cookie:
 oraclelicense=accept-securebackup-cookie
 http://download.oracle.com/otn-pub/java/jdk/7u67-b01/jdk-7u67-linux-x64.rpm
 rpm -i jdk-7u67-linux-x64.rpm
 export JAVA_HOME=/usr/java/jdk1.7.0_67
 export PATH=$PATH:/usr/java/jdk1.7.0_67/bin
 alternatives --install /usr/bin/java java /usr/java/jdk1.7.0_67/bin/java 2
 alternatives --config java
 java -version

 Build Mesos
 wget http://mirror.olnevhost.net/pub/apache/mesos/0.20.1/mesos-0.20.1.tar.gz
 tar -zxf mesos-0.20.1.tar.gz
 cd mesos
 mkdir build
 cd build
 ../configure
 make
 make check (This will fail on a cgroups issues, see earlier in this thread)
 make install

 Run Mesos Master and Slave
 /usr/local/sbin/mesos-master --work_dir=/tmp/mesos
 --zk=zk://localhost:2181/mesos --quorum=1 --ip=1.2.3.4
 /usr/local/sbin/mesos-slave --master=zk://localhost:2181/mesos
 --containerizers=docker,mesos

 On Thu, Sep 25, 2014 at 1:56 PM, Tim St Clair tstcl...@redhat.com wrote:
 It looks like docker-daemon isn't running.

 Cheers,
 Tim

 - Original Message -
 From: John Mickey j...@pithoslabs.com
 To: user@mesos.apache.org
 Sent: Thursday, September 25, 2014 10:33:42 AM
 Subject: Re: Build on Amazon Linux

 I tried the --help options before replying in my previous post, but
 did not do a good job of explaining what I was seeing

 --isolation=VALUE  Isolation mechanisms to use, e.g.,
 'posix/cpu,posix/mem', or

 'cgroups/cpu,cgroups/mem', or network/port_mapping
  (configure with flag:
 --with-network-isolator to enable),
  or 'external'. (default:
 posix/cpu,posix/mem)

 If I run this (Master is running)
 $ /usr/local/sbin/mesos-slave --master=zk://localhost:2181/mesos
 --containerizers=docker,mesos --isolation=posix/cpu,posix/mem

 Slave will not start with this message
 $ I0925 15:26:19.118268 18604 main.cpp:128] Version: 0.20.0 Failed to
 create a containerizer: Could not create DockerContainerizer: Failed
 to find a mounted cgroups hierarchy for the 'cpu' subsystem; you
 probably need to mount cgroups manually!

 The default is posix/cpu,posix/mem

 Any ideas why it is still trying to use cgroups?

 Once I get this working, I will post the steps for Amazon Linux.
 Thank you again for the help.


 On Wed, Sep 24, 2014 at 4:31 PM, Tim St Clair tstcl...@redhat.com wrote:
 
  $ mesos-slave --isolation='posix/cpu,posix/mem' ...
 
  for ref:
 
  $ mesos-slave --help
 
  ...
 
  --isolation=VALUE  Isolation mechanisms to use,
  e.g., 'posix/cpu,posix/mem', or
   'cgroups/cpu,cgroups/mem', or
   network/port_mapping
   (configure with flag:
   --with-network-isolator to
   enable),
  ...
 
  Cheers,
  Tim
 
  - Original Message -
  From: John Mickey j...@pithoslabs.com
  To: user@mesos.apache.org
  Sent: Wednesday, September 24, 2014 4:03:37 PM
  Subject: Re: Build on Amazon Linux
 
  Thank you again for the responses.  What is the option to remove
  cgroups isolation from the slave start?
 
  I ran /usr/local/sbin/mesos-slave --help and do not see an option to
  remove cgroups isolation from the slave start
 
  On Wed, Sep 24, 2014 at 1:48 PM, Tim St Clair tstcl...@redhat.com 
  wrote:
   You likely have a systemd problem, and you can edit your slave startup
   to
   remove cgroups isolation until 0.21.0 is released.
  
   # systemd cgroup integration, *only* enable on master/0.21.0  
   #export MESOS_isolation='cgroups/cpu,cgroups/mem'
   #export MESOS_cgroups_root='system.slice/mesos-slave.service'
   #export MESOS_cgroups_hierarchy

Re: Build on Amazon Linux

2014-09-26 Thread John Mickey
Docker version 1.2.0, build fa7b24f/1.2.0

It's available in the AMZN repos by default

On Fri, Sep 26, 2014 at 1:58 AM, Dick Davies d...@hellooperator.net wrote:
 What version of docker does that give you, out of interest?


 mainline EL7 is still shipping a pre-1.0 that won't work with mesos
 (although since docker is just a static Go binary, it's trivial to overwrite
 /usr/bin/docker and get everything to work).


 On 25 September 2014 20:23, John Mickey j...@pithoslabs.com wrote:
 Thanks to all for the help

 Tim - thanks for pointing out the obvious
 CCAAT - Great article

 Here are the instructions for getting Mesos to run on Amazon Linux
 amzn-ami-hvm-2014.03.1.x86_64-ebs (ami-383a5008) (us-west-2)

 On a single instance, as root, proof of concept setup

 Install Docker
 yum -y docker
 service docker start

 Install Tools to build Mesos (From Apache Mesos documentation)
 yum -y groupinstall Development Tools
 yum -y install python-devel java-1.7.0-openjdk-devel zlib-devel
 libcurl-devel openssl-devel cyrus-sasl-devel cyrus-sasl-md5
 wget 
 http://mirror.nexcess.net/apache/maven/maven-3/3.0.5/binaries/apache-maven-3.0.5-bin.tar.gz
 tar -zxf apache-maven-3.0.5-bin.tar.gz -C /opt/
 ln -s /opt/apache-maven-3.0.5/bin/mvn /usr/bin/mvn

 Install Oracle Java (Amazon Linux ships with OpenJDK)
 wget --no-check-certificate --no-cookies --header Cookie:
 oraclelicense=accept-securebackup-cookie
 http://download.oracle.com/otn-pub/java/jdk/7u67-b01/jdk-7u67-linux-x64.rpm
 rpm -i jdk-7u67-linux-x64.rpm
 export JAVA_HOME=/usr/java/jdk1.7.0_67
 export PATH=$PATH:/usr/java/jdk1.7.0_67/bin
 alternatives --install /usr/bin/java java /usr/java/jdk1.7.0_67/bin/java 2
 alternatives --config java
 java -version

 Build Mesos
 wget http://mirror.olnevhost.net/pub/apache/mesos/0.20.1/mesos-0.20.1.tar.gz
 tar -zxf mesos-0.20.1.tar.gz
 cd mesos
 mkdir build
 cd build
 ../configure
 make
 make check (This will fail on a cgroups issues, see earlier in this thread)
 make install

 Run Mesos Master and Slave
 /usr/local/sbin/mesos-master --work_dir=/tmp/mesos
 --zk=zk://localhost:2181/mesos --quorum=1 --ip=1.2.3.4
 /usr/local/sbin/mesos-slave --master=zk://localhost:2181/mesos
 --containerizers=docker,mesos

 On Thu, Sep 25, 2014 at 1:56 PM, Tim St Clair tstcl...@redhat.com wrote:
 It looks like docker-daemon isn't running.

 Cheers,
 Tim

 - Original Message -
 From: John Mickey j...@pithoslabs.com
 To: user@mesos.apache.org
 Sent: Thursday, September 25, 2014 10:33:42 AM
 Subject: Re: Build on Amazon Linux

 I tried the --help options before replying in my previous post, but
 did not do a good job of explaining what I was seeing

 --isolation=VALUE  Isolation mechanisms to use, e.g.,
 'posix/cpu,posix/mem', or

 'cgroups/cpu,cgroups/mem', or network/port_mapping
  (configure with flag:
 --with-network-isolator to enable),
  or 'external'. (default:
 posix/cpu,posix/mem)

 If I run this (Master is running)
 $ /usr/local/sbin/mesos-slave --master=zk://localhost:2181/mesos
 --containerizers=docker,mesos --isolation=posix/cpu,posix/mem

 Slave will not start with this message
 $ I0925 15:26:19.118268 18604 main.cpp:128] Version: 0.20.0 Failed to
 create a containerizer: Could not create DockerContainerizer: Failed
 to find a mounted cgroups hierarchy for the 'cpu' subsystem; you
 probably need to mount cgroups manually!

 The default is posix/cpu,posix/mem

 Any ideas why it is still trying to use cgroups?

 Once I get this working, I will post the steps for Amazon Linux.
 Thank you again for the help.


 On Wed, Sep 24, 2014 at 4:31 PM, Tim St Clair tstcl...@redhat.com wrote:
 
  $ mesos-slave --isolation='posix/cpu,posix/mem' ...
 
  for ref:
 
  $ mesos-slave --help
 
  ...
 
  --isolation=VALUE  Isolation mechanisms to use,
  e.g., 'posix/cpu,posix/mem', or
   'cgroups/cpu,cgroups/mem', 
  or
   network/port_mapping
   (configure with flag:
   --with-network-isolator to
   enable),
  ...
 
  Cheers,
  Tim
 
  - Original Message -
  From: John Mickey j...@pithoslabs.com
  To: user@mesos.apache.org
  Sent: Wednesday, September 24, 2014 4:03:37 PM
  Subject: Re: Build on Amazon Linux
 
  Thank you again for the responses.  What is the option to remove
  cgroups isolation from the slave start?
 
  I ran /usr/local/sbin/mesos-slave --help and do not see an option to
  remove cgroups isolation from the slave start
 
  On Wed, Sep 24, 2014 at 1:48 PM, Tim St Clair tstcl...@redhat.com 
  wrote:
   You likely have a systemd problem, and you can edit your slave startup
   to
   remove cgroups isolation until 0.21.0 is released.
  
   # systemd cgroup integration, *only* enable

Re: Build on Amazon Linux

2014-09-25 Thread CCAAT

On 09/25/14 10:33, John Mickey wrote:


The default is posix/cpu,posix/mem



Any ideas why it is still trying to use cgroups?


Perhaps this short posting my help a bit?
http://blog.jorgenschaefer.de/2014/07/why-systemd.html

Short answer, systemd is controlling cgroups now, and it is
a huge, monolith of software vs the traditional init systems.

I run gentoo system, with openrc in lieu of systemd. Most all
other distros have or are moving to systemd. There is lots published
on systemd.



hth,
James




Re: Build on Amazon Linux

2014-09-25 Thread John Mickey
Thanks to all for the help

Tim - thanks for pointing out the obvious
CCAAT - Great article

Here are the instructions for getting Mesos to run on Amazon Linux
amzn-ami-hvm-2014.03.1.x86_64-ebs (ami-383a5008) (us-west-2)

On a single instance, as root, proof of concept setup

Install Docker
yum -y docker
service docker start

Install Tools to build Mesos (From Apache Mesos documentation)
yum -y groupinstall Development Tools
yum -y install python-devel java-1.7.0-openjdk-devel zlib-devel
libcurl-devel openssl-devel cyrus-sasl-devel cyrus-sasl-md5
wget 
http://mirror.nexcess.net/apache/maven/maven-3/3.0.5/binaries/apache-maven-3.0.5-bin.tar.gz
tar -zxf apache-maven-3.0.5-bin.tar.gz -C /opt/
ln -s /opt/apache-maven-3.0.5/bin/mvn /usr/bin/mvn

Install Oracle Java (Amazon Linux ships with OpenJDK)
wget --no-check-certificate --no-cookies --header Cookie:
oraclelicense=accept-securebackup-cookie
http://download.oracle.com/otn-pub/java/jdk/7u67-b01/jdk-7u67-linux-x64.rpm
rpm -i jdk-7u67-linux-x64.rpm
export JAVA_HOME=/usr/java/jdk1.7.0_67
export PATH=$PATH:/usr/java/jdk1.7.0_67/bin
alternatives --install /usr/bin/java java /usr/java/jdk1.7.0_67/bin/java 2
alternatives --config java
java -version

Build Mesos
wget http://mirror.olnevhost.net/pub/apache/mesos/0.20.1/mesos-0.20.1.tar.gz
tar -zxf mesos-0.20.1.tar.gz
cd mesos
mkdir build
cd build
../configure
make
make check (This will fail on a cgroups issues, see earlier in this thread)
make install

Run Mesos Master and Slave
/usr/local/sbin/mesos-master --work_dir=/tmp/mesos
--zk=zk://localhost:2181/mesos --quorum=1 --ip=1.2.3.4
/usr/local/sbin/mesos-slave --master=zk://localhost:2181/mesos
--containerizers=docker,mesos

On Thu, Sep 25, 2014 at 1:56 PM, Tim St Clair tstcl...@redhat.com wrote:
 It looks like docker-daemon isn't running.

 Cheers,
 Tim

 - Original Message -
 From: John Mickey j...@pithoslabs.com
 To: user@mesos.apache.org
 Sent: Thursday, September 25, 2014 10:33:42 AM
 Subject: Re: Build on Amazon Linux

 I tried the --help options before replying in my previous post, but
 did not do a good job of explaining what I was seeing

 --isolation=VALUE  Isolation mechanisms to use, e.g.,
 'posix/cpu,posix/mem', or

 'cgroups/cpu,cgroups/mem', or network/port_mapping
  (configure with flag:
 --with-network-isolator to enable),
  or 'external'. (default:
 posix/cpu,posix/mem)

 If I run this (Master is running)
 $ /usr/local/sbin/mesos-slave --master=zk://localhost:2181/mesos
 --containerizers=docker,mesos --isolation=posix/cpu,posix/mem

 Slave will not start with this message
 $ I0925 15:26:19.118268 18604 main.cpp:128] Version: 0.20.0 Failed to
 create a containerizer: Could not create DockerContainerizer: Failed
 to find a mounted cgroups hierarchy for the 'cpu' subsystem; you
 probably need to mount cgroups manually!

 The default is posix/cpu,posix/mem

 Any ideas why it is still trying to use cgroups?

 Once I get this working, I will post the steps for Amazon Linux.
 Thank you again for the help.


 On Wed, Sep 24, 2014 at 4:31 PM, Tim St Clair tstcl...@redhat.com wrote:
 
  $ mesos-slave --isolation='posix/cpu,posix/mem' ...
 
  for ref:
 
  $ mesos-slave --help
 
  ...
 
  --isolation=VALUE  Isolation mechanisms to use,
  e.g., 'posix/cpu,posix/mem', or
   'cgroups/cpu,cgroups/mem', or
   network/port_mapping
   (configure with flag:
   --with-network-isolator to
   enable),
  ...
 
  Cheers,
  Tim
 
  - Original Message -
  From: John Mickey j...@pithoslabs.com
  To: user@mesos.apache.org
  Sent: Wednesday, September 24, 2014 4:03:37 PM
  Subject: Re: Build on Amazon Linux
 
  Thank you again for the responses.  What is the option to remove
  cgroups isolation from the slave start?
 
  I ran /usr/local/sbin/mesos-slave --help and do not see an option to
  remove cgroups isolation from the slave start
 
  On Wed, Sep 24, 2014 at 1:48 PM, Tim St Clair tstcl...@redhat.com wrote:
   You likely have a systemd problem, and you can edit your slave startup
   to
   remove cgroups isolation until 0.21.0 is released.
  
   # systemd cgroup integration, *only* enable on master/0.21.0  
   #export MESOS_isolation='cgroups/cpu,cgroups/mem'
   #export MESOS_cgroups_root='system.slice/mesos-slave.service'
   #export MESOS_cgroups_hierarchy=/sys/fs/cgroup
  
   Cheers,
   Tim
  
  
   - Original Message -
   From: John Mickey j...@pithoslabs.com
   To: user@mesos.apache.org
   Sent: Wednesday, September 24, 2014 1:43:31 PM
   Subject: Re: Build on Amazon Linux
  
   Mesos: 0.20.0 (Using latest tar from Apache mirror)
  
   AMI: amzn-ami-hvm-2014.03.1.x86_64-ebs (ami-383a5008) (us-west-2

Re: Build on Amazon Linux

2014-09-24 Thread John Mickey
Thank you for the responses.

I replaced OpenJDK with Oracle JDK and was able to build successfully.
During make check, I received the following error:

F0924 18:12:05.325278 13960 isolator_tests.cpp:136]
CHECK_SOME(isolator): Failed to create isolator: Failed to mount
cgroups hierarchy at '/sys/fs/cgroup/cpu': Failed to create directory
'/sys/fs/cgroup/cpu': No such file or directory
*** Check failure stack trace: ***
@ 0x7f41ff742b4d  google::LogMessage::Fail()
@ 0x7f41ff74488c  google::LogMessage::SendToLog()
@ 0x7f41ff74273c  google::LogMessage::Flush()
@ 0x7f41ff745189  google::LogMessageFatal::~LogMessageFatal()
@   0x5c1e68  _CheckFatal::~_CheckFatal()
@   0x6b6a8d  CpuIsolatorTest_UserCpuUsage_Test::TestBody()
@   0x975b43
testing::internal::HandleExceptionsInMethodIfSupported()
@   0x96cdf7  testing::Test::Run()
@   0x96ce9e  testing::TestInfo::Run()
@   0x96cfa5  testing::TestCase::Run()
@   0x96d248  testing::internal::UnitTestImpl::RunAllTests()
@   0x96d4d7  testing::UnitTest::Run()
@   0x4908be  main
@ 0x7f41fd5497d5  __libc_start_main
@   0x49edb9  (unknown)
make[3]: *** [check-local] Aborted
make[3]: Leaving directory `/root/mesos-0.20.0/build/src'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory `/root/mesos-0.20.0/build/src'
make[1]: *** [check] Error 2
make[1]: Leaving directory `/root/mesos-0.20.0/build/src'
make: *** [check-recursive] Error 1

Any guidance on this issue?

On Wed, Sep 24, 2014 at 12:09 PM, CCAAT cc...@tampabay.rr.com wrote:
 On 09/24/14 10:47, Jing Dong wrote:

  From my experience, I had issues with OpenJDK. You should try to build
 with Oracle JDK.


 I used icedtea for openjdk and it built ok on gentoo. [1]

 [1]  http://openjdk.java.net/projects/icedtea/




 configure: error: failed to determine linker flags for using Java (bad
 JAVA_HOME or missing support for your architecture?)

 $JAVA_HOME is set

 Java version
 java version 1.7.0_65
 OpenJDK Runtime Environment (amzn-2.5.1.2.45.amzn1-x86_64 u65-b17)
 OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)


 hth,
 James


Re: Build on Amazon Linux

2014-09-24 Thread CCAAT

On 09/24/14 13:23, John Mickey wrote:

Thank you for the responses.

I replaced OpenJDK with Oracle JDK and was able to build successfully.
During make check, I received the following error:

F0924 18:12:05.325278 13960 isolator_tests.cpp:136]
CHECK_SOME(isolator): Failed to create isolator: Failed to mount
cgroups hierarchy at '/sys/fs/cgroup/cpu': Failed to create directory
'/sys/fs/cgroup/cpu': No such file or directory



Sounds like a systemd problem. If you have access to
Ftrace/trace-cmd/KernelShark it may help you find the
problem, but really a WAG. (Wile Arse Guess)..

James




Re: Build on Amazon Linux

2014-09-24 Thread Tim St Clair
1.) What version of Mesos are you running? 

2.) What's your version of amazon Linux EL (6|7) based?  

Cheers,
Tim

- Original Message -
 From: John Mickey j...@pithoslabs.com
 To: user@mesos.apache.org
 Sent: Wednesday, September 24, 2014 1:23:19 PM
 Subject: Re: Build on Amazon Linux
 
 Thank you for the responses.
 
 I replaced OpenJDK with Oracle JDK and was able to build successfully.
 During make check, I received the following error:
 
 F0924 18:12:05.325278 13960 isolator_tests.cpp:136]
 CHECK_SOME(isolator): Failed to create isolator: Failed to mount
 cgroups hierarchy at '/sys/fs/cgroup/cpu': Failed to create directory
 '/sys/fs/cgroup/cpu': No such file or directory
 *** Check failure stack trace: ***
 @ 0x7f41ff742b4d  google::LogMessage::Fail()
 @ 0x7f41ff74488c  google::LogMessage::SendToLog()
 @ 0x7f41ff74273c  google::LogMessage::Flush()
 @ 0x7f41ff745189  google::LogMessageFatal::~LogMessageFatal()
 @   0x5c1e68  _CheckFatal::~_CheckFatal()
 @   0x6b6a8d  CpuIsolatorTest_UserCpuUsage_Test::TestBody()
 @   0x975b43
 testing::internal::HandleExceptionsInMethodIfSupported()
 @   0x96cdf7  testing::Test::Run()
 @   0x96ce9e  testing::TestInfo::Run()
 @   0x96cfa5  testing::TestCase::Run()
 @   0x96d248  testing::internal::UnitTestImpl::RunAllTests()
 @   0x96d4d7  testing::UnitTest::Run()
 @   0x4908be  main
 @ 0x7f41fd5497d5  __libc_start_main
 @   0x49edb9  (unknown)
 make[3]: *** [check-local] Aborted
 make[3]: Leaving directory `/root/mesos-0.20.0/build/src'
 make[2]: *** [check-am] Error 2
 make[2]: Leaving directory `/root/mesos-0.20.0/build/src'
 make[1]: *** [check] Error 2
 make[1]: Leaving directory `/root/mesos-0.20.0/build/src'
 make: *** [check-recursive] Error 1
 
 Any guidance on this issue?
 
 On Wed, Sep 24, 2014 at 12:09 PM, CCAAT cc...@tampabay.rr.com wrote:
  On 09/24/14 10:47, Jing Dong wrote:
 
   From my experience, I had issues with OpenJDK. You should try to build
  with Oracle JDK.
 
 
  I used icedtea for openjdk and it built ok on gentoo. [1]
 
  [1]  http://openjdk.java.net/projects/icedtea/
 
 
 
 
  configure: error: failed to determine linker flags for using Java (bad
  JAVA_HOME or missing support for your architecture?)
 
  $JAVA_HOME is set
 
  Java version
  java version 1.7.0_65
  OpenJDK Runtime Environment (amzn-2.5.1.2.45.amzn1-x86_64 u65-b17)
  OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)
 
 
  hth,
  James
 

-- 
Cheers,
Timothy St. Clair
Red Hat Inc.


Re: Build on Amazon Linux

2014-09-24 Thread John Mickey
Mesos: 0.20.0 (Using latest tar from Apache mirror)

AMI: amzn-ami-hvm-2014.03.1.x86_64-ebs (ami-383a5008) (us-west-2)
Kernel: 3.10.35-43.137.amzn1.x86_64 #1 SMP Wed Apr 2 09:36:59 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux

On Wed, Sep 24, 2014 at 1:42 PM, Tim St Clair tstcl...@redhat.com wrote:
 1.) What version of Mesos are you running?

 2.) What's your version of amazon Linux EL (6|7) based?

 Cheers,
 Tim

 - Original Message -
 From: John Mickey j...@pithoslabs.com
 To: user@mesos.apache.org
 Sent: Wednesday, September 24, 2014 1:23:19 PM
 Subject: Re: Build on Amazon Linux

 Thank you for the responses.

 I replaced OpenJDK with Oracle JDK and was able to build successfully.
 During make check, I received the following error:

 F0924 18:12:05.325278 13960 isolator_tests.cpp:136]
 CHECK_SOME(isolator): Failed to create isolator: Failed to mount
 cgroups hierarchy at '/sys/fs/cgroup/cpu': Failed to create directory
 '/sys/fs/cgroup/cpu': No such file or directory
 *** Check failure stack trace: ***
 @ 0x7f41ff742b4d  google::LogMessage::Fail()
 @ 0x7f41ff74488c  google::LogMessage::SendToLog()
 @ 0x7f41ff74273c  google::LogMessage::Flush()
 @ 0x7f41ff745189  google::LogMessageFatal::~LogMessageFatal()
 @   0x5c1e68  _CheckFatal::~_CheckFatal()
 @   0x6b6a8d  CpuIsolatorTest_UserCpuUsage_Test::TestBody()
 @   0x975b43
 testing::internal::HandleExceptionsInMethodIfSupported()
 @   0x96cdf7  testing::Test::Run()
 @   0x96ce9e  testing::TestInfo::Run()
 @   0x96cfa5  testing::TestCase::Run()
 @   0x96d248  testing::internal::UnitTestImpl::RunAllTests()
 @   0x96d4d7  testing::UnitTest::Run()
 @   0x4908be  main
 @ 0x7f41fd5497d5  __libc_start_main
 @   0x49edb9  (unknown)
 make[3]: *** [check-local] Aborted
 make[3]: Leaving directory `/root/mesos-0.20.0/build/src'
 make[2]: *** [check-am] Error 2
 make[2]: Leaving directory `/root/mesos-0.20.0/build/src'
 make[1]: *** [check] Error 2
 make[1]: Leaving directory `/root/mesos-0.20.0/build/src'
 make: *** [check-recursive] Error 1

 Any guidance on this issue?

 On Wed, Sep 24, 2014 at 12:09 PM, CCAAT cc...@tampabay.rr.com wrote:
  On 09/24/14 10:47, Jing Dong wrote:
 
   From my experience, I had issues with OpenJDK. You should try to build
  with Oracle JDK.
 
 
  I used icedtea for openjdk and it built ok on gentoo. [1]
 
  [1]  http://openjdk.java.net/projects/icedtea/
 
 
 
 
  configure: error: failed to determine linker flags for using Java (bad
  JAVA_HOME or missing support for your architecture?)
 
  $JAVA_HOME is set
 
  Java version
  java version 1.7.0_65
  OpenJDK Runtime Environment (amzn-2.5.1.2.45.amzn1-x86_64 u65-b17)
  OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)
 
 
  hth,
  James


 --
 Cheers,
 Timothy St. Clair
 Red Hat Inc.


Re: Build on Amazon Linux

2014-09-24 Thread John Mickey
Thank you again for the responses.  What is the option to remove
cgroups isolation from the slave start?

I ran /usr/local/sbin/mesos-slave --help and do not see an option to
remove cgroups isolation from the slave start

On Wed, Sep 24, 2014 at 1:48 PM, Tim St Clair tstcl...@redhat.com wrote:
 You likely have a systemd problem, and you can edit your slave startup to 
 remove cgroups isolation until 0.21.0 is released.

 # systemd cgroup integration, *only* enable on master/0.21.0  
 #export MESOS_isolation='cgroups/cpu,cgroups/mem'
 #export MESOS_cgroups_root='system.slice/mesos-slave.service'
 #export MESOS_cgroups_hierarchy=/sys/fs/cgroup

 Cheers,
 Tim


 - Original Message -
 From: John Mickey j...@pithoslabs.com
 To: user@mesos.apache.org
 Sent: Wednesday, September 24, 2014 1:43:31 PM
 Subject: Re: Build on Amazon Linux

 Mesos: 0.20.0 (Using latest tar from Apache mirror)

 AMI: amzn-ami-hvm-2014.03.1.x86_64-ebs (ami-383a5008) (us-west-2)
 Kernel: 3.10.35-43.137.amzn1.x86_64 #1 SMP Wed Apr 2 09:36:59 UTC 2014
 x86_64 x86_64 x86_64 GNU/Linux

 On Wed, Sep 24, 2014 at 1:42 PM, Tim St Clair tstcl...@redhat.com wrote:
  1.) What version of Mesos are you running?
 
  2.) What's your version of amazon Linux EL (6|7) based?
 
  Cheers,
  Tim
 
  - Original Message -
  From: John Mickey j...@pithoslabs.com
  To: user@mesos.apache.org
  Sent: Wednesday, September 24, 2014 1:23:19 PM
  Subject: Re: Build on Amazon Linux
 
  Thank you for the responses.
 
  I replaced OpenJDK with Oracle JDK and was able to build successfully.
  During make check, I received the following error:
 
  F0924 18:12:05.325278 13960 isolator_tests.cpp:136]
  CHECK_SOME(isolator): Failed to create isolator: Failed to mount
  cgroups hierarchy at '/sys/fs/cgroup/cpu': Failed to create directory
  '/sys/fs/cgroup/cpu': No such file or directory
  *** Check failure stack trace: ***
  @ 0x7f41ff742b4d  google::LogMessage::Fail()
  @ 0x7f41ff74488c  google::LogMessage::SendToLog()
  @ 0x7f41ff74273c  google::LogMessage::Flush()
  @ 0x7f41ff745189  google::LogMessageFatal::~LogMessageFatal()
  @   0x5c1e68  _CheckFatal::~_CheckFatal()
  @   0x6b6a8d  CpuIsolatorTest_UserCpuUsage_Test::TestBody()
  @   0x975b43
  testing::internal::HandleExceptionsInMethodIfSupported()
  @   0x96cdf7  testing::Test::Run()
  @   0x96ce9e  testing::TestInfo::Run()
  @   0x96cfa5  testing::TestCase::Run()
  @   0x96d248  testing::internal::UnitTestImpl::RunAllTests()
  @   0x96d4d7  testing::UnitTest::Run()
  @   0x4908be  main
  @ 0x7f41fd5497d5  __libc_start_main
  @   0x49edb9  (unknown)
  make[3]: *** [check-local] Aborted
  make[3]: Leaving directory `/root/mesos-0.20.0/build/src'
  make[2]: *** [check-am] Error 2
  make[2]: Leaving directory `/root/mesos-0.20.0/build/src'
  make[1]: *** [check] Error 2
  make[1]: Leaving directory `/root/mesos-0.20.0/build/src'
  make: *** [check-recursive] Error 1
 
  Any guidance on this issue?
 
  On Wed, Sep 24, 2014 at 12:09 PM, CCAAT cc...@tampabay.rr.com wrote:
   On 09/24/14 10:47, Jing Dong wrote:
  
From my experience, I had issues with OpenJDK. You should try to build
   with Oracle JDK.
  
  
   I used icedtea for openjdk and it built ok on gentoo. [1]
  
   [1]  http://openjdk.java.net/projects/icedtea/
  
  
  
  
   configure: error: failed to determine linker flags for using Java
   (bad
   JAVA_HOME or missing support for your architecture?)
  
   $JAVA_HOME is set
  
   Java version
   java version 1.7.0_65
   OpenJDK Runtime Environment (amzn-2.5.1.2.45.amzn1-x86_64 u65-b17)
   OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)
  
  
   hth,
   James
 
 
  --
  Cheers,
  Timothy St. Clair
  Red Hat Inc.


 --
 Cheers,
 Timothy St. Clair
 Red Hat Inc.


Re: Build on Amazon Linux

2014-09-24 Thread Tim St Clair

$ mesos-slave --isolation='posix/cpu,posix/mem' ... 

for ref:

$ mesos-slave --help 

...

--isolation=VALUE  Isolation mechanisms to use, e.g., 
'posix/cpu,posix/mem', or
 'cgroups/cpu,cgroups/mem', or 
network/port_mapping
 (configure with flag: 
--with-network-isolator to enable),
...

Cheers,
Tim

- Original Message -
 From: John Mickey j...@pithoslabs.com
 To: user@mesos.apache.org
 Sent: Wednesday, September 24, 2014 4:03:37 PM
 Subject: Re: Build on Amazon Linux
 
 Thank you again for the responses.  What is the option to remove
 cgroups isolation from the slave start?
 
 I ran /usr/local/sbin/mesos-slave --help and do not see an option to
 remove cgroups isolation from the slave start
 
 On Wed, Sep 24, 2014 at 1:48 PM, Tim St Clair tstcl...@redhat.com wrote:
  You likely have a systemd problem, and you can edit your slave startup to
  remove cgroups isolation until 0.21.0 is released.
 
  # systemd cgroup integration, *only* enable on master/0.21.0  
  #export MESOS_isolation='cgroups/cpu,cgroups/mem'
  #export MESOS_cgroups_root='system.slice/mesos-slave.service'
  #export MESOS_cgroups_hierarchy=/sys/fs/cgroup
 
  Cheers,
  Tim
 
 
  - Original Message -
  From: John Mickey j...@pithoslabs.com
  To: user@mesos.apache.org
  Sent: Wednesday, September 24, 2014 1:43:31 PM
  Subject: Re: Build on Amazon Linux
 
  Mesos: 0.20.0 (Using latest tar from Apache mirror)
 
  AMI: amzn-ami-hvm-2014.03.1.x86_64-ebs (ami-383a5008) (us-west-2)
  Kernel: 3.10.35-43.137.amzn1.x86_64 #1 SMP Wed Apr 2 09:36:59 UTC 2014
  x86_64 x86_64 x86_64 GNU/Linux
 
  On Wed, Sep 24, 2014 at 1:42 PM, Tim St Clair tstcl...@redhat.com wrote:
   1.) What version of Mesos are you running?
  
   2.) What's your version of amazon Linux EL (6|7) based?
  
   Cheers,
   Tim
  
   - Original Message -
   From: John Mickey j...@pithoslabs.com
   To: user@mesos.apache.org
   Sent: Wednesday, September 24, 2014 1:23:19 PM
   Subject: Re: Build on Amazon Linux
  
   Thank you for the responses.
  
   I replaced OpenJDK with Oracle JDK and was able to build successfully.
   During make check, I received the following error:
  
   F0924 18:12:05.325278 13960 isolator_tests.cpp:136]
   CHECK_SOME(isolator): Failed to create isolator: Failed to mount
   cgroups hierarchy at '/sys/fs/cgroup/cpu': Failed to create directory
   '/sys/fs/cgroup/cpu': No such file or directory
   *** Check failure stack trace: ***
   @ 0x7f41ff742b4d  google::LogMessage::Fail()
   @ 0x7f41ff74488c  google::LogMessage::SendToLog()
   @ 0x7f41ff74273c  google::LogMessage::Flush()
   @ 0x7f41ff745189  google::LogMessageFatal::~LogMessageFatal()
   @   0x5c1e68  _CheckFatal::~_CheckFatal()
   @   0x6b6a8d
   CpuIsolatorTest_UserCpuUsage_Test::TestBody()
   @   0x975b43
   testing::internal::HandleExceptionsInMethodIfSupported()
   @   0x96cdf7  testing::Test::Run()
   @   0x96ce9e  testing::TestInfo::Run()
   @   0x96cfa5  testing::TestCase::Run()
   @   0x96d248
   testing::internal::UnitTestImpl::RunAllTests()
   @   0x96d4d7  testing::UnitTest::Run()
   @   0x4908be  main
   @ 0x7f41fd5497d5  __libc_start_main
   @   0x49edb9  (unknown)
   make[3]: *** [check-local] Aborted
   make[3]: Leaving directory `/root/mesos-0.20.0/build/src'
   make[2]: *** [check-am] Error 2
   make[2]: Leaving directory `/root/mesos-0.20.0/build/src'
   make[1]: *** [check] Error 2
   make[1]: Leaving directory `/root/mesos-0.20.0/build/src'
   make: *** [check-recursive] Error 1
  
   Any guidance on this issue?
  
   On Wed, Sep 24, 2014 at 12:09 PM, CCAAT cc...@tampabay.rr.com wrote:
On 09/24/14 10:47, Jing Dong wrote:
   
 From my experience, I had issues with OpenJDK. You should try to
 build
with Oracle JDK.
   
   
I used icedtea for openjdk and it built ok on gentoo. [1]
   
[1]  http://openjdk.java.net/projects/icedtea/
   
   
   
   
configure: error: failed to determine linker flags for using
Java
(bad
JAVA_HOME or missing support for your architecture?)
   
$JAVA_HOME is set
   
Java version
java version 1.7.0_65
OpenJDK Runtime Environment (amzn-2.5.1.2.45.amzn1-x86_64
u65-b17)
OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)
   
   
hth,
James
  
  
   --
   Cheers,
   Timothy St. Clair
   Red Hat Inc.
 
 
  --
  Cheers,
  Timothy St. Clair
  Red Hat Inc.
 

-- 
Cheers,
Timothy St. Clair
Red Hat Inc.