Return-Path: X-Original-To: apmail-aurora-dev-archive@minotaur.apache.org Delivered-To: apmail-aurora-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0EC5511956 for ; Tue, 16 Sep 2014 18:28:21 +0000 (UTC) Received: (qmail 62376 invoked by uid 500); 16 Sep 2014 18:28:20 -0000 Delivered-To: apmail-aurora-dev-archive@aurora.apache.org Received: (qmail 62332 invoked by uid 500); 16 Sep 2014 18:28:20 -0000 Mailing-List: contact dev-help@aurora.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aurora.incubator.apache.org Delivered-To: mailing list dev@aurora.incubator.apache.org Received: (qmail 61767 invoked by uid 99); 16 Sep 2014 18:28:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Sep 2014 18:28:20 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of yasumoto7@gmail.com designates 209.85.220.44 as permitted sender) Received: from [209.85.220.44] (HELO mail-pa0-f44.google.com) (209.85.220.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Sep 2014 18:28:16 +0000 Received: by mail-pa0-f44.google.com with SMTP id kx10so343818pab.3 for ; Tue, 16 Sep 2014 11:27:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=do/aFEsn/N60mBJry6bBFbtm/ao7NRz/1ImXgB9QraE=; b=pJm1uiLhtWfaZbMoE4tL0/MKNjYTX9/CLYDO4noqDDTLUud6ECqgrjxecPhikRDG7/ mCOTzrG58QZXs7S17CNwIwC4t1AqaED01xh7b0gDcD3/G1CFF194aL/B12quP94XrXgU i/qrPPq25u/YH1sB3zZ1cKn4w0evJ6XesYA0vVn4pgQxPoaAYLcgnMRBLdpNdKvo6q74 FlDs6TX1g4Iej3aeBVyh4gmI/Mi8DqTGOyXVIANvfqJLrIIfrV74Q5miKjImpXQLOI0P crFlF0hHc9LoW6K41mmg3zgMsxJ/yWEmPlJLX1aw/S3RE1XJYROd1waJgqbGcxZGHLco olXQ== X-Received: by 10.70.91.176 with SMTP id cf16mr24084389pdb.137.1410892076228; Tue, 16 Sep 2014 11:27:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.70.49.102 with HTTP; Tue, 16 Sep 2014 11:27:36 -0700 (PDT) In-Reply-To: References: <54186DD2.1090807@blue-yonder.com> From: Joe Smith Date: Tue, 16 Sep 2014 11:27:36 -0700 Message-ID: Subject: Re: Mesos 12.04 Python2.7 Egg To: Zameer Manji Cc: dev@aurora.incubator.apache.org, user@mesos.apache.org Content-Type: multipart/alternative; boundary=001a11c212c0052607050332e9b4 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c212c0052607050332e9b4 Content-Type: text/plain; charset=UTF-8 At first I was going to say we should fix up the eggs on PyPI, however the pypa has sort of side-stepped the 'linux-distro' problem, so if we were to 'fix' the eggs to work on debian, they probably would not work on CentOS or Fedora anymore. Can you indeed try patching https://github.com/apache/incubator-aurora/blob/master/pants.ini#L89 to a local mirror where you've built eggs for your version of Debian? If you decide to go that route, I'd be very interested to hear if you bump into any build issues! On Tue, Sep 16, 2014 at 10:07 AM, Zameer Manji wrote: > Stephan, > > We sidestepped this problem by upgrading our vagrant image to Ubuntu 14.04 > LTS which ships with GLIBC 2.16. I suspect to fix this properly we need to > file a bug against Apache Mesos. > > On Tue, Sep 16, 2014 at 10:05 AM, Stephan Erb > wrote: > >> Did you find a solution for your question? >> >> I am currently having similar issues when trying to run the thermos >> executor on Debian 7, which doesn't ship GLIBC 2.16 either. Seems like we >> have to patch the Aurora build process (probably in 3rdparty/python/BUILD) >> to download the correct eggs form mesosphere.io instead of using the >> default ones on pypi. >> >> Does anyone have experience in how to do this? >> >> Thanks, >> Stephan >> >> >> >> On Sa 30 Aug 2014 08:08:24 CEST, Joe Smith wrote: >> >>> Howdy all, >>> >>> I'm to migrating Apache Aurora >>> to mesos 0.20.0[1][2], but am >>> having an issue using the published dist on PyPI >>> . I also gave the >>> mesosphere-provided (thank you!) egg >>> for Ubuntu >>> 12.04, and am getting the same stack trace: >>> >>> vagrant@192:~$ >>> PYTHONPATH=/home/vagrant/.pex/install/mesos.native-0.20.0- >>> py2.7-linux-x86_64.egg.be6632b790cd03172f858e7f875cda >>> b4ef415ca5/mesos.native-0.20.0-py2.7-linux-x86_64.egg/mesos/ >>> python2.7 >>> Python 2.7.3 (default, Feb 27 2014, 19:58:35) >>> [GCC 4.6.3] on linux2 >>> Type "help", "copyright", "credits" or "license" for more information. >>> >>> import mesos >>> Traceback (most recent call last): >>> File "", line 1, in >>> ImportError: No module named mesos >>> >>> import native >>> Traceback (most recent call last): >>> File "", line 1, in >>> File >>> "/home/vagrant/.pex/install/mesos.native-0.20.0-py2.7-linux-x86_64.egg. >>> be6632b790cd03172f858e7f875cdab4ef415ca5/mesos.native-0.20. >>> 0-py2.7-linux-x86_64.egg/mesos/native/__init__.py", >>> line 17, in >>> from ._mesos import MesosExecutorDriverImpl >>> ImportError: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.16' not >>> found (required by >>> /home/vagrant/.pex/install/mesos.native-0.20.0-py2.7-linux-x86_64.egg. >>> be6632b790cd03172f858e7f875cdab4ef415ca5/mesos.native-0.20. >>> 0-py2.7-linux-x86_64.egg/mesos/native/_mesos.so) >>> >>> >>> >>> It looks like the issue is it was built with a non-standard glibc (if >>> I'm following right): >>> >>> vagrant@192:~/mesos-0.20.0$ /lib/x86_64-linux-gnu/libc.so.6 | grep >>> release\ version >>> GNU C Library (Ubuntu EGLIBC 2.15-0ubuntu10) stable release version >>> 2.15, by Roland McGrath et al. >>> >>> Any feedback or suggestions would be greatly appreciated! >>> >>> Thanks, >>> Joe >>> >>> [1] https://reviews.apache.org/r/25208/ >>> [2] https://issues.apache.org/jira/browse/AURORA-674 >>> >> >> >> >> >> > > > -- > Zameer Manji > --001a11c212c0052607050332e9b4--