Return-Path: 
 <mesos-dev-return-1990-apmail-incubator-mesos-dev-archive=incubator.apache.org@incubator.apache.org>
X-Original-To: apmail-incubator-mesos-dev-archive@minotaur.apache.org
Delivered-To: apmail-incubator-mesos-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 287C997BE
	for <apmail-incubator-mesos-dev-archive@minotaur.apache.org>;
 Thu, 12 Apr 2012 17:41:42 +0000 (UTC)
Received: (qmail 13510 invoked by uid 500); 12 Apr 2012 17:41:41 -0000
Delivered-To: apmail-incubator-mesos-dev-archive@incubator.apache.org
Received: (qmail 13454 invoked by uid 500); 12 Apr 2012 17:41:41 -0000
Mailing-List: contact mesos-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:mesos-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:mesos-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:mesos-dev@incubator.apache.org>
List-Id: <mesos-dev.incubator.apache.org>
Reply-To: mesos-dev@incubator.apache.org
Delivered-To: mailing list mesos-dev@incubator.apache.org
Received: (qmail 13433 invoked by uid 99); 12 Apr 2012 17:41:41 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Apr 2012 17:41:41 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Apr 2012 17:41:40 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 20F64367E92
	for <mesos-dev@incubator.apache.org>; Thu, 12 Apr 2012 17:41:20 +0000 (UTC)
Date: Thu, 12 Apr 2012 17:41:20 +0000 (UTC)
From: "Jessica J (Commented) (JIRA)" <jira@apache.org>
To: mesos-dev@incubator.apache.org
Message-ID: 
 <1928581666.18228.1334252480147.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1153712837.17694.1334247080891.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MESOS-183) Included MPI Framework Fails to
 Start
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


    [ https://issues.apache.org/jira/browse/MESOS-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252642#comment-13252642 ] 

Jessica J commented on MESOS-183:
---------------------------------

Here's a bonafide bug--looks like the MesosSchedulerDriver signature changed but the calling code did not. Is there an easy way I can patch this on my own machine?

[jessica@golgatha mpi]$ ./nmpiexec -n 10 mesos://master@192.168.41.1:5050 hostname
Connecting to mesos master mesos://master@192.168.41.1:5050
MPD_PID is golgatha.[...].net_40165
Traceback (most recent call last):
  File "./nmpiexec.py", line 171, in <module>
    mesos.MesosSchedulerDriver(sched, args[0]).run()
TypeError: function takes exactly 3 arguments (2 given)

                
> Included MPI Framework Fails to Start
> -------------------------------------
>
>                 Key: MESOS-183
>                 URL: https://issues.apache.org/jira/browse/MESOS-183
>             Project: Mesos
>          Issue Type: Bug
>          Components: documentation, framework
>         Environment: Scientific Linux Cluster
>            Reporter: Jessica J
>            Assignee: Harvey Feng 
>              Labels: documentation, mpi, setup
>
> There are really two facets to this issue. The first is that no good documentation exists for setting up and using the included MPI framework. The second, and more important issue, is that the framework will not run. The second issue is possibly related to the first in that I may not be setting it up properly. 
> To test the MPI framework, by trial and error I determined I needed to run python setup.py build and python setup.py install in the MESOS-HOME/src/python directory. Now when I try to run nmpiexec -h, I get an AttributeError, below: 
> Traceback (most recent call last):
>   File "./nmpiexec.py", line 2, in <module>
>     import mesos
>   File "/usr/lib64/python2.6/site-packages/mesos-0.9.0-py2.6-linux-x86_64.egg/mesos.py", line 22, in <module>
>     import _mesos
>   File "/usr/lib64/python2.6/site-packages/mesos-0.9.0-py2.6-linux-x86_64.egg/mesos_pb2.py", line 1286, in <module>
>     DESCRIPTOR.message_types_by_name['FrameworkID'] = _FRAMEWORKID
> AttributeError: 'FileDescriptor' object has no attribute 'message_types_by_name'
> I've examined setup.py and determined that the version of protobuf it includes (2.4.1) does, indeed, contain a FileDescriptor class in descriptor.py that sets self.message_types_by_name, so I'm not sure what the issue is. Is this a bug? Or is there a step I'm missing? Do I need to also build/install protobuf?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira