On May 7, 2013, at 10:30 AM, Paul Kapinos wrote:
> On 05/07/13 17:55, Ralph Castain wrote:
>>>
>>> *1.* *OpenMPI support for 1.6 seems to be broken, and was fixed maybe in
>>> 1.7?*
>>> http://www.open-mpi.org/community/lists/users/2013/03/21640.php
>>
>> It is indeed fixed in 1.7 - we will l
Are people in community using MPI libraries in their application for
real time processing / analytics? I have access to a cluster with
infiniband and want to test millions of hypotheses and depending upon
which one passed would run an aggregate function over them. I would like
to achieve a subs
On 05/07/13 17:55, Ralph Castain wrote:
*1.* *OpenMPI support for 1.6 seems to be broken, and was fixed maybe in 1.7?*
http://www.open-mpi.org/community/lists/users/2013/03/21640.php
It is indeed fixed in 1.7 - we will look at backporting a fix to 1.6
well, we're using 1.6.4 with tight integ
The FAQ assumes you realize that CIDR notation requires a value for the "x"...
:-)
On May 7, 2013, at 9:04 AM, Angel de Vicente wrote:
> Hi,
>
> "Jeff Squyres (jsquyres)" writes:
>> The list of names in the hostfile specifies the servers that will be used,
>> not the network interfaces. Ha
On May 7, 2013, at 12:04 PM, Angel de Vicente wrote:
> But, the FAQ seems to be wrong, since it also says that I should be able
> to run like:
>
> [angelv@comer RTI2D.Parallel]$ mpiexec -loadbalance --mca
> btl_tcp_if_include 192.168.1.x/24 -prefix $OMPI_PREFIX -hostfile
I think I meant the "x
Hi,
"Jeff Squyres (jsquyres)" writes:
> The list of names in the hostfile specifies the servers that will be used,
> not the network interfaces. Have a look at the TCP portion of the FAQ:
>
> http://www.open-mpi.org/faq/?category=tcp
Thanks a lot for this.
Now it works OK if I run it lik
On May 7, 2013, at 7:09 AM, Andrey Rubshtein wrote:
> Hi everyone,
>
> I want to install OpenMPI on LSF cluster in our organization. I am not
> proficient with Linux/LSF, and some of my questions might be from lack of
> understanding of the system, and not related to OpenMPI directly.
>
> So
I'm afraid our Windows support person has moved on to greener pastures, and so
we don't actually support it any more (in fact, the 1.7 version specifically
removed the support code).
Our friends in the cygwin world have a module that allows you to continue using
OMPI on those systems - you migh
Look at the MCA params btl_tcp_if_include and btl_tcp_if_exclude. Either
include the internal network (to restrict to *only* using that one), or exclude
the public one
On May 7, 2013, at 8:25 AM, Angel de Vicente wrote:
> Hi again,
>
> Angel de Vicente writes:
>> yes, that's just what I did
The list of names in the hostfile specifies the servers that will be used, not
the network interfaces. Have a look at the TCP portion of the FAQ:
http://www.open-mpi.org/faq/?category=tcp
On May 7, 2013, at 11:25 AM, Angel de Vicente wrote:
> Hi again,
>
> Angel de Vicente writes:
>> y
Hi again,
Angel de Vicente writes:
> yes, that's just what I did with orted. I saw the port that it was
> trying to connect and telnet to it, and I got "No route to host", so
> that's why I was going the firewall path. Hopefully the sysadmins can
> disable the firewall for the internal network to
Hello everyone,
I'm having troubles with building OpenMPI v1.6.4 (actually all v1.6 and
v1.7 versions) release sources (in both x86 and x64 modes) on Windows
machine using VS 2010 and VS 2012 compilers and cmake v2.8.10.2. Just to
note, I tried it with VS2008 too and it worked fine in x86 mode, bu
On 5/7/13 9:48 PM, Ralph Castain wrote:
>
> On May 7, 2013, at 7:39 AM, Duke Nguyen wrote:
>
>>
>>
>> No I didnt (and that maybe the reason, I am not really sure I was
>> correct when installation these things). What I did was:
>>
>> $ cd /opt/apps/openmpi/openmpi-1.7.2r28341_composer_xe_2013.3.
On May 7, 2013, at 7:39 AM, Duke Nguyen wrote:
>
>
> No I didnt (and that maybe the reason, I am not really sure I was
> correct when installation these things). What I did was:
>
> $ cd /opt/apps/openmpi/openmpi-1.7.2r28341_composer_xe_2013.3.163
> $ ./configure CC=/opt/intel/composer_xe_201
On 5/7/13 9:25 PM, Ralph Castain wrote:
> Look at your ld-library-path. Breaking it down, you have the following
> elements
>
> /opt/apps/abinit/abinit-7.2.1_composer_xe_2013.3.163_openmpi-1.7.2_intel_fftw3-mkl/usr/local/lib
$ export LD_LIBRARY_PATH=
$ module load mpi/openmpi-1.7.2_composer_xe_2
On 5/7/13 9:07 PM, Ralph Castain wrote:
> Is there a typo here?
>
> /opt/apps/abinit/abinit-7.2.1_composer_xe_2013.3.163_openmpi-1.7.2_intel_fftw3-mkl/usr/local/lib:/opt/apps/openmpi/openmpi-1.7.2r28341_composer_xe_2013.3.163/usr/local/lib/openmpi:/opt/apps/openmpi/openmpi-1.7.2r28341_composer_xe_
Look at your ld-library-path. Breaking it down, you have the following elements
/opt/apps/abinit/abinit-7.2.1_composer_xe_2013.3.163_openmpi-1.7.2_intel_fftw3-mkl/usr/local/lib
repeated three times. Did you actually configure with
--prefix=/opt/apps/openmpi/openmpi-1.7.2r28341_composer_xe_2013.3
On 5/7/13 8:10 PM, Jeff Squyres (jsquyres) wrote:
> On May 7, 2013, at 7:36 AM, Duke Nguyen wrote:
>
>> So apparently openmpi 1.7.2 looks for the old library at
>> /usr/loca/lib/openmpi for 1.6.3 instead of at
>> /opt/apps/openmpi/openmpi-1.7.2r28341_composer_xe_2013.3.163/usr/local/lib/openmpi.
Hi everyone,
I want to install OpenMPI on LSF cluster in our organization. I am not
proficient with Linux/LSF, and some of my questions might be from lack of
understanding of the system, and not related to OpenMPI directly.
So far I found these bits of information on the site of OpenMPI
*1.* *Op
Is there a typo here?
/opt/apps/abinit/abinit-7.2.1_composer_xe_2013.3.163_openmpi-1.7.2_intel_fftw3-mkl/usr/local/lib:/opt/apps/openmpi/openmpi-1.7.2r28341_composer_xe_2013.3.163/usr/local/lib/openmpi:/opt/apps/openmpi/openmpi-1.7.2r28341_composer_xe_2013.3.163/usr/local/lib:/usr/local/lib:/opt/i
On 5/7/13 7:02 PM, Reuti wrote:
> Hi,
>
> Am 07.05.2013 um 13:36 schrieb Duke Nguyen:
>
>> I am testing our cluster with module environment, and am having a
>> headache to understand openmpi 1.7.2!!! So our system currently has
>> openmpi 1.6.3 (at default location /usr/local), 1.6.4 and 1.7.2 co
On May 7, 2013, at 7:36 AM, Duke Nguyen wrote:
> So apparently openmpi 1.7.2 looks for the old library at
> /usr/loca/lib/openmpi for 1.6.3 instead of at
> /opt/apps/openmpi/openmpi-1.7.2r28341_composer_xe_2013.3.163/usr/local/lib/openmpi.
> Is there away to force openmpi 1.7.2 look at
> /opt/app
Hi,
Am 07.05.2013 um 13:36 schrieb Duke Nguyen:
> I am testing our cluster with module environment, and am having a
> headache to understand openmpi 1.7.2!!! So our system currently has
> openmpi 1.6.3 (at default location /usr/local), 1.6.4 and 1.7.2 compiled
> with intel compilers (installed at
Hi folks,
I am testing our cluster with module environment, and am having a
headache to understand openmpi 1.7.2!!! So our system currently has
openmpi 1.6.3 (at default location /usr/local), 1.6.4 and 1.7.2 compiled
with intel compilers (installed at /opt/apps). In order to use openmpi
1.7.2 for
Hi,
"Jeff Squyres (jsquyres)" writes:
>>> I'm starting to think that perhaps is a firewall issue? I don't have
>>> root access in these machines but I'll try to investigate.
> A simple test is to try any socket-based server app between the two
> machines that opens a random listening socket. Tr
25 matches
Mail list logo
