Return-Path: X-Original-To: apmail-mesos-user-archive@www.apache.org Delivered-To: apmail-mesos-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 36436177E0 for ; Mon, 23 Mar 2015 12:41:43 +0000 (UTC) Received: (qmail 93669 invoked by uid 500); 23 Mar 2015 12:41:40 -0000 Delivered-To: apmail-mesos-user-archive@mesos.apache.org Received: (qmail 93617 invoked by uid 500); 23 Mar 2015 12:41:39 -0000 Mailing-List: contact user-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@mesos.apache.org Delivered-To: mailing list user@mesos.apache.org Received: (qmail 93607 invoked by uid 99); 23 Mar 2015 12:41:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Mar 2015 12:41:39 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of codecraig@gmail.com designates 209.85.213.174 as permitted sender) Received: from [209.85.213.174] (HELO mail-ig0-f174.google.com) (209.85.213.174) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Mar 2015 12:41:35 +0000 Received: by igcau2 with SMTP id au2so40678255igc.0 for ; Mon, 23 Mar 2015 05:41:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=vcNDK3VptpsLxJJ1AXIk27DnjBYa6SioVufpMVW7J4E=; b=ftdTHUDcNKG5Zp3yEySpamfpvwR6yfCnFRmaxMEtmZCh6l4AaFJmd3CQ01YBYUpwNv h7JtT9ILu4MEW7BQu7M23Hxk70qPKbNl4qsQaN6BQ1D6tX9PF3eqG3NYbGk9Wi9HRrmC Pn1YaDuFSLT7JlHG/UKn3h310ED3bBJlGAxCtXG5GEpO2sKTpuanXjF/ndQGE3doj7b7 6sj5DIlZdaBTy6jbWfkY9DlFlpzV3Gqz4UDF4cx4yYWZRs8G5PZndVupY7NLKD1OL5cB X+e1WvdVBmB8E9ZIWdkX/pqwuCcBFbLXWPkOYS+qe5r3+uUUWCIj4Ytv7BNVVFL/Tnlc HU3Q== MIME-Version: 1.0 X-Received: by 10.43.64.134 with SMTP id xi6mr19034632icb.83.1427114475371; Mon, 23 Mar 2015 05:41:15 -0700 (PDT) Received: by 10.36.71.147 with HTTP; Mon, 23 Mar 2015 05:41:15 -0700 (PDT) In-Reply-To: <6F26503B67E25B4599CEDE7E1304D0CC3DFB9FC9@mailbox18.lucas.alllucas.com> References: <6F26503B67E25B4599CEDE7E1304D0CC3DFB9FAE@mailbox18.lucas.alllucas.com> <6F26503B67E25B4599CEDE7E1304D0CC3DFB9FC9@mailbox18.lucas.alllucas.com> Date: Mon, 23 Mar 2015 08:41:15 -0400 Message-ID: Subject: Re: Unable to install subversion-devel 1.8+ on CentOS 7 From: craig w To: user@mesos.apache.org Content-Type: multipart/alternative; boundary=bcaec51f987b5bc51d0511f3fbe8 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec51f987b5bc51d0511f3fbe8 Content-Type: text/plain; charset=UTF-8 https://issues.apache.org/jira/browse/MESOS-2115 On Mon, Mar 23, 2015 at 8:30 AM, Aaron Carey wrote: > ah interesting.. what causes this difference? > > I think this probably makes sense for our setup currently.. > > ------------------------------ > *From:* craig w [codecraig@gmail.com] > *Sent:* 23 March 2015 12:20 > *To:* user@mesos.apache.org > *Subject:* Re: Unable to install subversion-devel 1.8+ on CentOS 7 > > I had considered running Mesos in docker containers, however with Mesos > 0.21 if the slaves are running in a container and you have tasks running in > containers, if the slave container were to exit/die, the tasks running in > containers would also exit. If running mesos-slave on the host, any tasks > that it had running will remain running even if the process dies. That's > why I hadn't gone that route. Have you considered that? > > On Mon, Mar 23, 2015 at 8:15 AM, craig w wrote: > >> What OS is your docker image based on? >> >> On Mon, Mar 23, 2015 at 8:11 AM, Aaron Carey wrote: >> >>> Not sure if this helps, but we've been using docker to run Mesos on >>> Centos 7 hosts. >>> >>> ------------------------------ >>> *From:* craig w [codecraig@gmail.com] >>> *Sent:* 23 March 2015 12:06 >>> *To:* user@mesos.apache.org >>> *Subject:* Unable to install subversion-devel 1.8+ on CentOS 7 >>> >>> Mesos 0.21.0+ requires subversion-devel 1.8+, which can be >>> installed by adding the Wandisco yum repo. However, it appears that >>> subversion-devel 1.8+ requires libsasl2.so.2, which is not available on >>> CentOS7. >>> >>> I've seen one person try to create a symlink to libsasl2.so.3 and it >>> worked [1], while another person found it did not work [2]. >>> >>> I created a CentOS 7 droplet on DigitalOcean, added the Wandisco repo >>> and tried to install subversion-devel and it failed b/c of the >>> libsasl2.so.2 missing. I tried creating a symlink (ln -s >>> /usr/lib64/libsasl2.so.3 /usr/lib64/libsasl2.so.2), restarting the server >>> and installing subversion-devel still failed b/c of the libsasl issue: >>> >>> Error: Package: subversion-1.8.11-1.x86_64 (WandiscoSVN) >>>> Requires: libsasl2.so.2()(64bit) >>>> >>> >>> Anyone had any success on CentOS 7 with Mesos 0.21+? >>> >>> [1] - did work: http://unix.stackexchange.com/a/178408 >>> >>> [2] - did not work: >>> http://www.wandisco.com/svnforum/forum/smartsvn-community/smartsvn-help-and-support/69834-installing-subversion-command-line-client-on-centos-7 >>> >> >> >> >> -- >> >> https://github.com/mindscratch >> https://www.google.com/+CraigWickesser >> https://twitter.com/mind_scratch >> https://twitter.com/craig_links >> >> > > > -- > > https://github.com/mindscratch > https://www.google.com/+CraigWickesser > https://twitter.com/mind_scratch > https://twitter.com/craig_links > > -- https://github.com/mindscratch https://www.google.com/+CraigWickesser https://twitter.com/mind_scratch https://twitter.com/craig_links --bcaec51f987b5bc51d0511f3fbe8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On Mon, Mar 23, 2015 at 8:3= 0 AM, Aaron Carey <acarey@ilm.com> wrote:
ah interesting.. what causes this difference?

I think this probably makes sense for our setup currently..

Fro= m: craig w [co= decraig@gmail.com]
Sent: 23 March 2015 12:20
To: user@= mesos.apache.org
Subject: Re: Unable to install subversion-devel 1.8+ on CentOS 7

I had considered running Mesos in docker containers, howev= er with Mesos 0.21 if the slaves are running in a container and you have ta= sks running in containers, if the slave container were to exit/die, the tas= ks running in containers would also exit. If running mesos-slave on the host, any tasks that it had running wi= ll remain running even if the process dies. That's why I hadn't gon= e that route. Have you considered that?

On Mon, Mar 23, 2015 at 8:15 AM, craig w <codecraig@gmai= l.com> wrote:
What OS is your docker image based on?

On Mon, Mar 23, 2015 at 8:11 AM, Aaron Carey <acarey@ilm.com&= gt; wrote:
Not sure if this helps, but we've been using docker to run Mesos on C= entos 7 hosts.

Fro= m: craig w [co= decraig@gmail.com]
Sent: 23 March 2015 12:06
To: user@= mesos.apache.org
Subject: Unable to install subversion-devel 1.8+ on CentOS 7

Mesos 0.21.0+ requires subversion-devel 1.8+, which can be installed b= y adding the Wandisco yum repo. However, it appears that subversion-devel 1= .8+ requires libsasl2.so.2, which is not available on CentOS7.

I've seen one person try to create a symlink to libsasl2.so.3 and it wo= rked [1], while another person found it did not work [2].

I created a CentOS 7 droplet on DigitalOcean, added the Wandisco repo = and tried to install subversion-devel and it failed b/c of the libsasl2.so.= 2 missing. I tried creating a symlink (ln -s /usr/lib64/libsasl2.so.3 /usr/= lib64/libsasl2.so.2), restarting the server and installing subversion-devel still failed b/c of the libsasl= issue:

Error: Package: subversion-1.8.11-1.x86_64 (WandiscoSVN)
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Requires: libs= asl2.so.2()(64bit)

Anyone had any success on CentOS 7 with Mesos 0.21+?


[2] - did not work:http://www.wandisco.com/svnforum= /forum/smartsvn-community/smartsvn-help-and-support/69834-installing-subver= sion-command-line-client-on-centos-7



--



--



--
--bcaec51f987b5bc51d0511f3fbe8--