date:20161019

[OMPI users] communicator with MPI_Reduce

2016-10-19 Thread Marlborough, Rick

Designation: Non-Export Controlled Content
Folks;
My MPI_COMM_WORLD size is 2000. I have created a communicator 
based on a small subset. I have used this communicator in MPI_Barrier calls and 
it seems to work fine. Now I want to use this in MPI_Reduce. When I do this I 
get errors like "invalid root" or more mysteriously "on communicator MPI 
communicator 7 group from 0... invalid argument of some kind.". can someone 
specify how to use a communicator (that is not COMM_WORLD) with MPI_Reduce and 
specify rank properly.

Thanx
Rick

3.1.1001
___
users mailing list
users@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/users

Re: [OMPI users] Problem building OpenMPI with CUDA 8.0

2016-10-19 Thread Jeff Squyres (jsquyres)

Justin --

Fair point.  Can you work with Sylvain Jeaugey (at Nvidia) to submit a pull 
request for this functionality?

Thanks.


> On Oct 18, 2016, at 2:26 PM, Justin Luitjens  wrote:
> 
> After looking into this a bit more it appears that the issue is I am building 
> on a head node which does not have the driver installed.  Building on back 
> node resolves this issue.  In CUDA 8.0 the NVML stubs can be found in the 
> toolkit at the following path:  ${CUDA_HOME}/lib64/stubs
>  
> For 8.0 I’d suggest updating the configure/make scripts to look for nvml 
> there and link in the stubs.  This way the build is not dependent on the 
> driver being installed and only the toolkit.
>  
> Thanks,
> Justin
>  
> From: users [mailto:users-boun...@lists.open-mpi.org] On Behalf Of Justin 
> Luitjens
> Sent: Tuesday, October 18, 2016 9:53 AM
> To: users@lists.open-mpi.org
> Subject: [OMPI users] Problem building OpenMPI with CUDA 8.0
>  
> I have the release version of CUDA 8.0 installed and am trying to build 
> OpenMPI.
>  
> Here is my configure and build line:
>  
> ./configure --prefix=$PREFIXPATH --with-cuda=$CUDA_HOME --with-tm= 
> --with-openib= && make && sudo make install
>  
> Where CUDA_HOME points to the cuda install path.  
>  
> When I run the above command it builds for quite a while but eventually 
> errors out wit this:
>  
> make[2]: Entering directory 
> `/home/jluitjens/Perforce/jluitjens_dtlogin_p4sw/sw/devrel/DevtechCompute/Internal/Tools/dtlogin/scripts/mpi/openmpi-1.10.1-gcc5.0_2014_11-cuda8.0/opal/tools/wrappers'
>   CCLD opal_wrapper
> ../../../opal/.libs/libopen-pal.so: undefined reference to `nvmlInit_v2'
> ../../../opal/.libs/libopen-pal.so: undefined reference to 
> `nvmlDeviceGetHandleByIndex_v2'
> ../../../opal/.libs/libopen-pal.so: undefined reference to 
> `nvmlDeviceGetCount_v2'
>  
>  
> Any idea what I might need to change to get around this error?
>  
> Thanks,
> Justin
> This email message is for the sole use of the intended recipient(s) and may 
> contain confidential information.  Any unauthorized review, use, disclosure 
> or distribution is prohibited.  If you are not the intended recipient, please 
> contact the sender by reply email and destroy all copies of the original 
> message.
> ___
> users mailing list
> users@lists.open-mpi.org
> https://rfd.newmexicoconsortium.org/mailman/listinfo/users


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

___
users mailing list
users@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/users

Re: [MTT users] MTT Server Downtime - Fri., Oct. 21, 2016 (Updated)

2016-10-19 Thread Josh Hursey

Based on current estimates we need to extend the window of downtime for MTT
to 24 hours.

*Start time*: *Fri., Oct. 21, 2016 at Noon US Eastern* (11 am US Central)
*End time*: *Sat., Oct. 22, 2016 at Noon US Eastern* (estimated)

I will send an email just before taking down the MTT site on Friday, and
another once it is back up on Sat.

During this time all of the MTT services will be down - MTT Reporter and
MTT submission interface. If you have an MTT client running during this
time you will receive an error message if you try to submit results to the
MTT server.

Let me know if you have any questions or concerns.


On Tue, Oct 18, 2016 at 10:59 AM, Josh Hursey  wrote:

> We are moving this downtime to *Friday, Oct. 21 from 2-5 pm US Eastern*.
>
> We hit a snag with the AWS configuration that we are working through.
>
> On Sun, Oct 16, 2016 at 9:53 AM, Josh Hursey 
> wrote:
>
>> I will announce this on the Open MPI developer's teleconf on Tuesday,
>> before the move.
>>
>> Geoff - Please add this item to the agenda.
>>
>>
>> Short version:
>> ---
>> MTT server (mtt.open-mpi.org) will be going down for maintenance on
>> Tuesday, Oct. 18, 2016 from 2-5 pm US Eastern. During this time the MTT
>> Reporter and the MTT client submission interface will not be accessible. I
>> will send an email out when the service is back online.
>>
>>
>> Longer version:
>> ---
>> We need to move the MTT Server/Database from the IU server to the AWS
>> server. This move will be completely transparent to users submitting to the
>> database, except for a window of downtime to move the database.
>>
>> I estimate that moving the database will take about two hours. So I have
>> blocked off three hours to give us time to test, and redirect the DNS
>> record.
>>
>> Once the service comes back online, you should be able to access MTT
>> using themtt.open-mpi.org URL. No changes are needed in your MTT client
>> setup, and all permalinks are expected to still work after the move.
>>
>>
>> Let me know if you have any questions or concerns about the move.
>>
>>
>> --
>> Josh Hursey
>> IBM Spectrum MPI Developer
>>
>
>
>
> --
> Josh Hursey
> IBM Spectrum MPI Developer
>



-- 
Josh Hursey
IBM Spectrum MPI Developer
___
mtt-users mailing list
mtt-users@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/mtt-users

Re: [OMPI users] openmpi-1.10.3 cross compile configure options for arm-openwrt-linux-muslgnueabi on x86_64-linux-gnu

2016-10-19 Thread Mahesh Nanavalla

k...


Thank u very much for your quick reply.

On Wed, Oct 19, 2016 at 4:38 PM, Gilles Gouaillardet <
gilles.gouaillar...@gmail.com> wrote:

> You will not be able to generate VT traces, and since you unlikely want to
> do that, you will likely be just fine
>
> Cheers,
>
> Gilles
>
> On Wednesday, October 19, 2016, Mahesh Nanavalla <
> mahesh.nanavalla...@gmail.com> wrote:
>
>> Hi Gilles,
>>
>> Thanks for reply,
>>
>> If i do *--disable-vt *while configuring the openmpi-1.10.3 ,
>>
>> the size of the installation directory reduced 70MB to 9MB.
>>
>> will it effect anything?
>>
>>
>> On Wed, Oct 19, 2016 at 4:06 PM, Gilles Gouaillardet <
>> gilles.gouaillar...@gmail.com> wrote:
>>
>>> vt is a contrib that produces traces to be used by VaMPIr
>>> IIRC, this has been removed from Open MPI starting v2.0.0
>>>
>>> Worst case scenario is it will fail to build, and most likely case is
>>> you do not need it, so you can save some build time with --disable-vet
>>>
>>> Cheers,
>>>
>>> Gilles
>>>
>>>
>>> On Wednesday, October 19, 2016, Mahesh Nanavalla <
>>> mahesh.nanavalla...@gmail.com> wrote:
>>>
 Hi all,

 can any one tell purpose and importance of *--disable-vt*

 *Thanks,*
 *Mahesh.N*

 On Wed, Oct 19, 2016 at 12:11 PM, Mahesh Nanavalla <
 mahesh.nanavalla...@gmail.com> wrote:

> Hi all
>
> it's working.
>
> I forget to copy all openmpi libs and bin to target board
>
> Now it's working fine...
>
> Thank u all.
>
> Thank u very much for your support
>
> root@OpenWrt:/# cp /openmpi/lib/libopen-rte.so.12 /usr/lib/
> root@OpenWrt:/# cp /openmpi/lib/libopen-pal.so.13 /usr/lib/
> root@OpenWrt:/# /openmpi/bin/mpirun -np 1 helloworld
> 
> --
> mpirun has detected an attempt to run as root.
> Running at root is *strongly* discouraged as any mistake (e.g., in
> defining TMPDIR) or bug can result in catastrophic damage to the OS
> file system, leaving your system in an unusable state.
>
> You can override this protection by adding the --allow-run-as-root
> option to your cmd line. However, we reiterate our strong advice
> against doing so - please do so at your own risk.
> 
> --
> root@OpenWrt:/# /openmpi/bin/mpirun --allow-run-as-root -np 1
> helloworld
> Hello world from processor OpenWrt, rank 0 1
> root@OpenWrt:/# /openmpi/bin/mpirun --allow-run-as-root -np 2
> helloworld
> Hello world from processor OpenWrt, rank 1 2
> Hello world from processor OpenWrt, rank 0 2
> root@OpenWrt:/# /openmpi/bin/mpirun --allow-run-as-root -np 4
> helloworld
> Hello world from processor OpenWrt, rank 0 4
> Hello world from processor OpenWrt, rank 2 4
> Hello world from processor OpenWrt, rank 3 4
> Hello world from processor OpenWrt, rank 1 4
>
>
> On Tue, Oct 18, 2016 at 8:23 PM, Kawashima, Takahiro <
> t-kawash...@jp.fujitsu.com> wrote:
>
>> Hi,
>>
>> You did *not* specify the following options to configure, right?
>> Specifying all these will cause a problem.
>>
>>   --disable-mmap-shmem
>>   --disable-posix-shmem
>>   --disable-sysv-shmem
>>
>> Please send the output of the following command.
>>
>>   mpirun --allow-run-as-root -np 1 --mca shmem_base_verbose 100
>> helloworld
>>
>> And, give us the config.log file which is output in the
>> top directory where configure is executed.
>> Put it on the web or send the compressed (xz or bzip2 is better) file.
>>
>> Regards,
>> Takahiro Kawashima
>>
>> > Hi Gilles,
>> >
>> > Thank you for reply,
>> >
>> > After doing below config options also
>> >
>> > ./configure --enable-orterun-prefix-by-default
>> > --prefix="/home/nmahesh//home/nmahesh/Workspace/ARM_MPI/armm
>> pi/openmpi"
>> > CC=arm-openwrt-linux-muslgnueabi-gcc
>> > CXX=arm-openwrt-linux-muslgnueabi-g++
>> > --host=arm-openwrt-linux-muslgnueabi
>> > --enable-script-wrapper-compilers
>> > --disable-mpi-fortran
>> > --enable-shared
>> > --disable-dlopen
>> >
>> > it's configured ,make & make install successfully.
>> >
>> > i compiled  *helloworld.c *programm got executable for *arm* as
>> below(by
>> > checking the readelf *armhelloworld*),
>> >
>> >
>> > *nmahesh@nmahesh-H81MLV3:~/Workspace/ARM_MPI/mpi$
>> > /home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
>> > -L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
>> helloworld*
>> >
>> > But ,while i run using mpirun on target board as below
>> >
>> > root@OpenWrt:/# mpirun --allow-run-as-root -np 1 helloworld
>> >

Re: [OMPI users] openmpi-1.10.3 cross compile configure options for arm-openwrt-linux-muslgnueabi on x86_64-linux-gnu

2016-10-19 Thread Gilles Gouaillardet

You will not be able to generate VT traces, and since you unlikely want to
do that, you will likely be just fine

Cheers,

Gilles

On Wednesday, October 19, 2016, Mahesh Nanavalla <
mahesh.nanavalla...@gmail.com> wrote:

> Hi Gilles,
>
> Thanks for reply,
>
> If i do *--disable-vt *while configuring the openmpi-1.10.3 ,
>
> the size of the installation directory reduced 70MB to 9MB.
>
> will it effect anything?
>
>
> On Wed, Oct 19, 2016 at 4:06 PM, Gilles Gouaillardet <
> gilles.gouaillar...@gmail.com
> > wrote:
>
>> vt is a contrib that produces traces to be used by VaMPIr
>> IIRC, this has been removed from Open MPI starting v2.0.0
>>
>> Worst case scenario is it will fail to build, and most likely case is you
>> do not need it, so you can save some build time with --disable-vet
>>
>> Cheers,
>>
>> Gilles
>>
>>
>> On Wednesday, October 19, 2016, Mahesh Nanavalla <
>> mahesh.nanavalla...@gmail.com
>> > wrote:
>>
>>> Hi all,
>>>
>>> can any one tell purpose and importance of *--disable-vt*
>>>
>>> *Thanks,*
>>> *Mahesh.N*
>>>
>>> On Wed, Oct 19, 2016 at 12:11 PM, Mahesh Nanavalla <
>>> mahesh.nanavalla...@gmail.com> wrote:
>>>
 Hi all

 it's working.

 I forget to copy all openmpi libs and bin to target board

 Now it's working fine...

 Thank u all.

 Thank u very much for your support

 root@OpenWrt:/# cp /openmpi/lib/libopen-rte.so.12 /usr/lib/
 root@OpenWrt:/# cp /openmpi/lib/libopen-pal.so.13 /usr/lib/
 root@OpenWrt:/# /openmpi/bin/mpirun -np 1 helloworld
 
 --
 mpirun has detected an attempt to run as root.
 Running at root is *strongly* discouraged as any mistake (e.g., in
 defining TMPDIR) or bug can result in catastrophic damage to the OS
 file system, leaving your system in an unusable state.

 You can override this protection by adding the --allow-run-as-root
 option to your cmd line. However, we reiterate our strong advice
 against doing so - please do so at your own risk.
 
 --
 root@OpenWrt:/# /openmpi/bin/mpirun --allow-run-as-root -np 1
 helloworld
 Hello world from processor OpenWrt, rank 0 1
 root@OpenWrt:/# /openmpi/bin/mpirun --allow-run-as-root -np 2
 helloworld
 Hello world from processor OpenWrt, rank 1 2
 Hello world from processor OpenWrt, rank 0 2
 root@OpenWrt:/# /openmpi/bin/mpirun --allow-run-as-root -np 4
 helloworld
 Hello world from processor OpenWrt, rank 0 4
 Hello world from processor OpenWrt, rank 2 4
 Hello world from processor OpenWrt, rank 3 4
 Hello world from processor OpenWrt, rank 1 4


 On Tue, Oct 18, 2016 at 8:23 PM, Kawashima, Takahiro <
 t-kawash...@jp.fujitsu.com> wrote:

> Hi,
>
> You did *not* specify the following options to configure, right?
> Specifying all these will cause a problem.
>
>   --disable-mmap-shmem
>   --disable-posix-shmem
>   --disable-sysv-shmem
>
> Please send the output of the following command.
>
>   mpirun --allow-run-as-root -np 1 --mca shmem_base_verbose 100
> helloworld
>
> And, give us the config.log file which is output in the
> top directory where configure is executed.
> Put it on the web or send the compressed (xz or bzip2 is better) file.
>
> Regards,
> Takahiro Kawashima
>
> > Hi Gilles,
> >
> > Thank you for reply,
> >
> > After doing below config options also
> >
> > ./configure --enable-orterun-prefix-by-default
> > --prefix="/home/nmahesh//home/nmahesh/Workspace/ARM_MPI/armm
> pi/openmpi"
> > CC=arm-openwrt-linux-muslgnueabi-gcc
> > CXX=arm-openwrt-linux-muslgnueabi-g++
> > --host=arm-openwrt-linux-muslgnueabi
> > --enable-script-wrapper-compilers
> > --disable-mpi-fortran
> > --enable-shared
> > --disable-dlopen
> >
> > it's configured ,make & make install successfully.
> >
> > i compiled  *helloworld.c *programm got executable for *arm* as
> below(by
> > checking the readelf *armhelloworld*),
> >
> >
> > *nmahesh@nmahesh-H81MLV3:~/Workspace/ARM_MPI/mpi$
> > /home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
> > -L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
> helloworld*
> >
> > But ,while i run using mpirun on target board as below
> >
> > root@OpenWrt:/# mpirun --allow-run-as-root -np 1 helloworld
> > 
> --
> > It looks like opal_init failed for some reason; your parallel
> process is
> > likely to abort.  There are many

Re: [OMPI users] openmpi-1.10.3 cross compile configure options for arm-openwrt-linux-muslgnueabi on x86_64-linux-gnu

2016-10-19 Thread Mahesh Nanavalla

Hi Gilles,

Thanks for reply,

If i do *--disable-vt *while configuring the openmpi-1.10.3 ,

the size of the installation directory reduced 70MB to 9MB.

will it effect anything?


On Wed, Oct 19, 2016 at 4:06 PM, Gilles Gouaillardet <
gilles.gouaillar...@gmail.com> wrote:

> vt is a contrib that produces traces to be used by VaMPIr
> IIRC, this has been removed from Open MPI starting v2.0.0
>
> Worst case scenario is it will fail to build, and most likely case is you
> do not need it, so you can save some build time with --disable-vet
>
> Cheers,
>
> Gilles
>
>
> On Wednesday, October 19, 2016, Mahesh Nanavalla <
> mahesh.nanavalla...@gmail.com> wrote:
>
>> Hi all,
>>
>> can any one tell purpose and importance of *--disable-vt*
>>
>> *Thanks,*
>> *Mahesh.N*
>>
>> On Wed, Oct 19, 2016 at 12:11 PM, Mahesh Nanavalla <
>> mahesh.nanavalla...@gmail.com> wrote:
>>
>>> Hi all
>>>
>>> it's working.
>>>
>>> I forget to copy all openmpi libs and bin to target board
>>>
>>> Now it's working fine...
>>>
>>> Thank u all.
>>>
>>> Thank u very much for your support
>>>
>>> root@OpenWrt:/# cp /openmpi/lib/libopen-rte.so.12 /usr/lib/
>>> root@OpenWrt:/# cp /openmpi/lib/libopen-pal.so.13 /usr/lib/
>>> root@OpenWrt:/# /openmpi/bin/mpirun -np 1 helloworld
>>> 
>>> --
>>> mpirun has detected an attempt to run as root.
>>> Running at root is *strongly* discouraged as any mistake (e.g., in
>>> defining TMPDIR) or bug can result in catastrophic damage to the OS
>>> file system, leaving your system in an unusable state.
>>>
>>> You can override this protection by adding the --allow-run-as-root
>>> option to your cmd line. However, we reiterate our strong advice
>>> against doing so - please do so at your own risk.
>>> 
>>> --
>>> root@OpenWrt:/# /openmpi/bin/mpirun --allow-run-as-root -np 1 helloworld
>>> Hello world from processor OpenWrt, rank 0 1
>>> root@OpenWrt:/# /openmpi/bin/mpirun --allow-run-as-root -np 2 helloworld
>>> Hello world from processor OpenWrt, rank 1 2
>>> Hello world from processor OpenWrt, rank 0 2
>>> root@OpenWrt:/# /openmpi/bin/mpirun --allow-run-as-root -np 4 helloworld
>>> Hello world from processor OpenWrt, rank 0 4
>>> Hello world from processor OpenWrt, rank 2 4
>>> Hello world from processor OpenWrt, rank 3 4
>>> Hello world from processor OpenWrt, rank 1 4
>>>
>>>
>>> On Tue, Oct 18, 2016 at 8:23 PM, Kawashima, Takahiro <
>>> t-kawash...@jp.fujitsu.com> wrote:
>>>
 Hi,

 You did *not* specify the following options to configure, right?
 Specifying all these will cause a problem.

   --disable-mmap-shmem
   --disable-posix-shmem
   --disable-sysv-shmem

 Please send the output of the following command.

   mpirun --allow-run-as-root -np 1 --mca shmem_base_verbose 100
 helloworld

 And, give us the config.log file which is output in the
 top directory where configure is executed.
 Put it on the web or send the compressed (xz or bzip2 is better) file.

 Regards,
 Takahiro Kawashima

 > Hi Gilles,
 >
 > Thank you for reply,
 >
 > After doing below config options also
 >
 > ./configure --enable-orterun-prefix-by-default
 > --prefix="/home/nmahesh//home/nmahesh/Workspace/ARM_MPI/armm
 pi/openmpi"
 > CC=arm-openwrt-linux-muslgnueabi-gcc
 > CXX=arm-openwrt-linux-muslgnueabi-g++
 > --host=arm-openwrt-linux-muslgnueabi
 > --enable-script-wrapper-compilers
 > --disable-mpi-fortran
 > --enable-shared
 > --disable-dlopen
 >
 > it's configured ,make & make install successfully.
 >
 > i compiled  *helloworld.c *programm got executable for *arm* as
 below(by
 > checking the readelf *armhelloworld*),
 >
 >
 > *nmahesh@nmahesh-H81MLV3:~/Workspace/ARM_MPI/mpi$
 > /home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
 > -L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
 helloworld*
 >
 > But ,while i run using mpirun on target board as below
 >
 > root@OpenWrt:/# mpirun --allow-run-as-root -np 1 helloworld
 > 
 --
 > It looks like opal_init failed for some reason; your parallel process
 is
 > likely to abort.  There are many reasons that a parallel process can
 > fail during opal_init; some of which are due to configuration or
 > environment problems.  This failure appears to be an internal failure;
 > here's some additional information (which may only be relevant to an
 > Open MPI developer):
 >
 >   opal_shmem_base_select failed
 >   --> Returned value -1 instead of OPAL_SUCCESS
 >
 > Kindly help me.
 >
 > On Tue, Oct 18, 2016 at 7:31 PM, Mahesh Nanavalla <
 >

Re: [OMPI users] openmpi-1.10.3 cross compile configure options for arm-openwrt-linux-muslgnueabi on x86_64-linux-gnu

2016-10-19 Thread Gilles Gouaillardet

vt is a contrib that produces traces to be used by VaMPIr
IIRC, this has been removed from Open MPI starting v2.0.0

Worst case scenario is it will fail to build, and most likely case is you
do not need it, so you can save some build time with --disable-vet

Cheers,

Gilles

On Wednesday, October 19, 2016, Mahesh Nanavalla <
mahesh.nanavalla...@gmail.com> wrote:

> Hi all,
>
> can any one tell purpose and importance of *--disable-vt*
>
> *Thanks,*
> *Mahesh.N*
>
> On Wed, Oct 19, 2016 at 12:11 PM, Mahesh Nanavalla <
> mahesh.nanavalla...@gmail.com
> > wrote:
>
>> Hi all
>>
>> it's working.
>>
>> I forget to copy all openmpi libs and bin to target board
>>
>> Now it's working fine...
>>
>> Thank u all.
>>
>> Thank u very much for your support
>>
>> root@OpenWrt:/# cp /openmpi/lib/libopen-rte.so.12 /usr/lib/
>> root@OpenWrt:/# cp /openmpi/lib/libopen-pal.so.13 /usr/lib/
>> root@OpenWrt:/# /openmpi/bin/mpirun -np 1 helloworld
>> 
>> --
>> mpirun has detected an attempt to run as root.
>> Running at root is *strongly* discouraged as any mistake (e.g., in
>> defining TMPDIR) or bug can result in catastrophic damage to the OS
>> file system, leaving your system in an unusable state.
>>
>> You can override this protection by adding the --allow-run-as-root
>> option to your cmd line. However, we reiterate our strong advice
>> against doing so - please do so at your own risk.
>> 
>> --
>> root@OpenWrt:/# /openmpi/bin/mpirun --allow-run-as-root -np 1 helloworld
>> Hello world from processor OpenWrt, rank 0 1
>> root@OpenWrt:/# /openmpi/bin/mpirun --allow-run-as-root -np 2 helloworld
>> Hello world from processor OpenWrt, rank 1 2
>> Hello world from processor OpenWrt, rank 0 2
>> root@OpenWrt:/# /openmpi/bin/mpirun --allow-run-as-root -np 4 helloworld
>> Hello world from processor OpenWrt, rank 0 4
>> Hello world from processor OpenWrt, rank 2 4
>> Hello world from processor OpenWrt, rank 3 4
>> Hello world from processor OpenWrt, rank 1 4
>>
>>
>> On Tue, Oct 18, 2016 at 8:23 PM, Kawashima, Takahiro <
>> t-kawash...@jp.fujitsu.com
>> > wrote:
>>
>>> Hi,
>>>
>>> You did *not* specify the following options to configure, right?
>>> Specifying all these will cause a problem.
>>>
>>>   --disable-mmap-shmem
>>>   --disable-posix-shmem
>>>   --disable-sysv-shmem
>>>
>>> Please send the output of the following command.
>>>
>>>   mpirun --allow-run-as-root -np 1 --mca shmem_base_verbose 100
>>> helloworld
>>>
>>> And, give us the config.log file which is output in the
>>> top directory where configure is executed.
>>> Put it on the web or send the compressed (xz or bzip2 is better) file.
>>>
>>> Regards,
>>> Takahiro Kawashima
>>>
>>> > Hi Gilles,
>>> >
>>> > Thank you for reply,
>>> >
>>> > After doing below config options also
>>> >
>>> > ./configure --enable-orterun-prefix-by-default
>>> > --prefix="/home/nmahesh//home/nmahesh/Workspace/ARM_MPI/armm
>>> pi/openmpi"
>>> > CC=arm-openwrt-linux-muslgnueabi-gcc
>>> > CXX=arm-openwrt-linux-muslgnueabi-g++
>>> > --host=arm-openwrt-linux-muslgnueabi
>>> > --enable-script-wrapper-compilers
>>> > --disable-mpi-fortran
>>> > --enable-shared
>>> > --disable-dlopen
>>> >
>>> > it's configured ,make & make install successfully.
>>> >
>>> > i compiled  *helloworld.c *programm got executable for *arm* as
>>> below(by
>>> > checking the readelf *armhelloworld*),
>>> >
>>> >
>>> > *nmahesh@nmahesh-H81MLV3:~/Workspace/ARM_MPI/mpi$
>>> > /home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
>>> > -L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
>>> helloworld*
>>> >
>>> > But ,while i run using mpirun on target board as below
>>> >
>>> > root@OpenWrt:/# mpirun --allow-run-as-root -np 1 helloworld
>>> > 
>>> --
>>> > It looks like opal_init failed for some reason; your parallel process
>>> is
>>> > likely to abort.  There are many reasons that a parallel process can
>>> > fail during opal_init; some of which are due to configuration or
>>> > environment problems.  This failure appears to be an internal failure;
>>> > here's some additional information (which may only be relevant to an
>>> > Open MPI developer):
>>> >
>>> >   opal_shmem_base_select failed
>>> >   --> Returned value -1 instead of OPAL_SUCCESS
>>> >
>>> > Kindly help me.
>>> >
>>> > On Tue, Oct 18, 2016 at 7:31 PM, Mahesh Nanavalla <
>>> > mahesh.nanavalla...@gmail.com
>>> > wrote:
>>> >
>>> > > Hi Gilles,
>>> > >
>>> > > Thank you for reply,
>>> > >
>>> > > After doing below config options also
>>> > >
>>> > > ./configure --enable-orterun-prefix-by-default
>>> > >

Re: [OMPI users] openmpi-1.10.3 cross compile configure options for arm-openwrt-linux-muslgnueabi on x86_64-linux-gnu

2016-10-19 Thread Mahesh Nanavalla

Hi all,

can any one tell purpose and importance of *--disable-vt*

*Thanks,*
*Mahesh.N*

On Wed, Oct 19, 2016 at 12:11 PM, Mahesh Nanavalla <
mahesh.nanavalla...@gmail.com> wrote:

> Hi all
>
> it's working.
>
> I forget to copy all openmpi libs and bin to target board
>
> Now it's working fine...
>
> Thank u all.
>
> Thank u very much for your support
>
> root@OpenWrt:/# cp /openmpi/lib/libopen-rte.so.12 /usr/lib/
> root@OpenWrt:/# cp /openmpi/lib/libopen-pal.so.13 /usr/lib/
> root@OpenWrt:/# /openmpi/bin/mpirun -np 1 helloworld
> --
> mpirun has detected an attempt to run as root.
> Running at root is *strongly* discouraged as any mistake (e.g., in
> defining TMPDIR) or bug can result in catastrophic damage to the OS
> file system, leaving your system in an unusable state.
>
> You can override this protection by adding the --allow-run-as-root
> option to your cmd line. However, we reiterate our strong advice
> against doing so - please do so at your own risk.
> --
> root@OpenWrt:/# /openmpi/bin/mpirun --allow-run-as-root -np 1 helloworld
> Hello world from processor OpenWrt, rank 0 1
> root@OpenWrt:/# /openmpi/bin/mpirun --allow-run-as-root -np 2 helloworld
> Hello world from processor OpenWrt, rank 1 2
> Hello world from processor OpenWrt, rank 0 2
> root@OpenWrt:/# /openmpi/bin/mpirun --allow-run-as-root -np 4 helloworld
> Hello world from processor OpenWrt, rank 0 4
> Hello world from processor OpenWrt, rank 2 4
> Hello world from processor OpenWrt, rank 3 4
> Hello world from processor OpenWrt, rank 1 4
>
>
> On Tue, Oct 18, 2016 at 8:23 PM, Kawashima, Takahiro <
> t-kawash...@jp.fujitsu.com> wrote:
>
>> Hi,
>>
>> You did *not* specify the following options to configure, right?
>> Specifying all these will cause a problem.
>>
>>   --disable-mmap-shmem
>>   --disable-posix-shmem
>>   --disable-sysv-shmem
>>
>> Please send the output of the following command.
>>
>>   mpirun --allow-run-as-root -np 1 --mca shmem_base_verbose 100 helloworld
>>
>> And, give us the config.log file which is output in the
>> top directory where configure is executed.
>> Put it on the web or send the compressed (xz or bzip2 is better) file.
>>
>> Regards,
>> Takahiro Kawashima
>>
>> > Hi Gilles,
>> >
>> > Thank you for reply,
>> >
>> > After doing below config options also
>> >
>> > ./configure --enable-orterun-prefix-by-default
>> > --prefix="/home/nmahesh//home/nmahesh/Workspace/ARM_MPI/armmpi/openmpi"
>> > CC=arm-openwrt-linux-muslgnueabi-gcc
>> > CXX=arm-openwrt-linux-muslgnueabi-g++
>> > --host=arm-openwrt-linux-muslgnueabi
>> > --enable-script-wrapper-compilers
>> > --disable-mpi-fortran
>> > --enable-shared
>> > --disable-dlopen
>> >
>> > it's configured ,make & make install successfully.
>> >
>> > i compiled  *helloworld.c *programm got executable for *arm* as below(by
>> > checking the readelf *armhelloworld*),
>> >
>> >
>> > *nmahesh@nmahesh-H81MLV3:~/Workspace/ARM_MPI/mpi$
>> > /home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
>> > -L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
>> helloworld*
>> >
>> > But ,while i run using mpirun on target board as below
>> >
>> > root@OpenWrt:/# mpirun --allow-run-as-root -np 1 helloworld
>> > 
>> --
>> > It looks like opal_init failed for some reason; your parallel process is
>> > likely to abort.  There are many reasons that a parallel process can
>> > fail during opal_init; some of which are due to configuration or
>> > environment problems.  This failure appears to be an internal failure;
>> > here's some additional information (which may only be relevant to an
>> > Open MPI developer):
>> >
>> >   opal_shmem_base_select failed
>> >   --> Returned value -1 instead of OPAL_SUCCESS
>> >
>> > Kindly help me.
>> >
>> > On Tue, Oct 18, 2016 at 7:31 PM, Mahesh Nanavalla <
>> > mahesh.nanavalla...@gmail.com> wrote:
>> >
>> > > Hi Gilles,
>> > >
>> > > Thank you for reply,
>> > >
>> > > After doing below config options also
>> > >
>> > > ./configure --enable-orterun-prefix-by-default
>> > > --prefix="/home/nmahesh//home/nmahesh/Workspace/ARM_MPI/armm
>> pi/openmpi"
>> > > CC=arm-openwrt-linux-muslgnueabi-gcc
>> > > CXX=arm-openwrt-linux-muslgnueabi-g++
>> > > --host=arm-openwrt-linux-muslgnueabi
>> > > --enable-script-wrapper-compilers
>> > > --disable-mpi-fortran
>> > > --enable-shared
>> > > --disable-dlopen
>> > >
>> > > it's configured ,make & make install successfully.
>> > >
>> > > i compiled  *helloworld.c *programm got executable for *arm* as
>> below(by
>> > > checking the readelf *armhelloworld*),
>> > >
>> > >
>> > > *nmahesh@nmahesh-H81MLV3:~/Workspace/ARM_MPI/mpi$
>> > > /home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
>> > > -L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
>>

[OMPI users] fail to run client/server mode using MPI_COMM_ACCEPT/MPI_COMM_CONNECT without mpirun

2016-10-19 Thread 王亮

I was doing the work to integrate OpenMPI into our application, and we did
not want to rely on mpirun.
And it seems that singleton MPI_INIT could meet our need. So I wrote a
client/sever demo to verify it.
However, it did not work. Is there anything wrong here or OpenMPI does not
support connect/accept work under singleton MPI_INIT?

The way I started client/server:
./server
./client $port_name(The port name is printed in server side)

I testes this on two versions(1.8.8 and 2.0.1)
On 1.8.8:
Trying connect to 2164981760.0;tcp://10.152.111.77,169.254.182.77:55937
+2164981761.0;tcp://10.152.111.77,169.254.182.77:21560:300
--
An attempt was made to send a message to a process whose
address is unknown:

  Sender: [[50549,1],0]
  From node:  busaa024
  Recipient:  [[50549,1],0]
  On node:busaa024
The message could not be delivered, and we are aborting.

On 2.0.1: timeout after 60s
Trying connect to 2540140922.0:2850261964
[busj50bda16.us.oracle.com:31952] OPAL ERROR: Timeout in file
base/pmix_base_fns.c at line 193
[busj50bda16:31952] *** An error occurred in MPI_Comm_connect
[busj50bda16:31952] *** reported by process [139681870123024,0]
[busj50bda16:31952] *** on communicator MPI_COMM_WORLD
[busj50bda16:31952] *** MPI_ERR_UNKNOWN: unknown error
[busj50bda16:31952] *** MPI_ERRORS_ARE_FATAL (processes in this
communicator will now abort,
[busj50bda16:31952] ***and potentially your MPI job)

The server code:
#include
#include
#include

int size, rank, msg;

int main(int argc, char *argv[]){
   MPI_Comm cliente;
   MPI_Status status;
   char portname[MPI_MAX_PORT_NAME];

   MPI_Init(,);
   MPI_Comm_size(MPI_COMM_WORLD,);
   MPI_Comm_rank(MPI_COMM_WORLD,);

   MPI_Open_port(MPI_INFO_NULL, portname);
   printf("portname: %s\n", portname);
   MPI_Comm_accept(portname, MPI_INFO_NULL, 0, MPI_COMM_SELF, );
   printf("client connected\n");
   MPI_Recv(, 1, MPI_INT, MPI_ANY_SOURCE, MPI_ANY_TAG, cliente,
);
   printf("msg: %d\n", msg);
   MPI_Comm_free();
   MPI_Close_port(portname);
   MPI_Finalize();
}

The client code:
#include
#include
#include
#include

int size, rank;
int main(int argc, char *argv[]){
   MPI_Comm servidor;
   int msg, tag, dest;
   char portname[MPI_MAX_PORT_NAME];

   MPI_Init(,);
   MPI_Comm_size(MPI_COMM_WORLD,);
   MPI_Comm_rank(MPI_COMM_WORLD,);
   if (argc >= 2){
  printf("Trying connect to %s\n", argv[1]);
  strcpy(portname, argv[1]);
  MPI_Comm_connect(portname, MPI_INFO_NULL, 0, MPI_COMM_WORLD,
);
  msg = 42; tag = 0; dest = 0;
  MPI_Send(, 1, MPI_INT, dest, tag, servidor);
  MPI_Comm_disconnect();
   }
   MPI_Finalize();
}

Thanks,
Bright Wang
___
users mailing list
users@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/users

Re: [OMPI users] openmpi-1.10.3 cross compile configure options for arm-openwrt-linux-muslgnueabi on x86_64-linux-gnu

2016-10-19 Thread Mahesh Nanavalla

Hi all

it's working.

I forget to copy all openmpi libs and bin to target board

Now it's working fine...

Thank u all.

Thank u very much for your support

root@OpenWrt:/# cp /openmpi/lib/libopen-rte.so.12 /usr/lib/
root@OpenWrt:/# cp /openmpi/lib/libopen-pal.so.13 /usr/lib/
root@OpenWrt:/# /openmpi/bin/mpirun -np 1 helloworld
--
mpirun has detected an attempt to run as root.
Running at root is *strongly* discouraged as any mistake (e.g., in
defining TMPDIR) or bug can result in catastrophic damage to the OS
file system, leaving your system in an unusable state.

You can override this protection by adding the --allow-run-as-root
option to your cmd line. However, we reiterate our strong advice
against doing so - please do so at your own risk.
--
root@OpenWrt:/# /openmpi/bin/mpirun --allow-run-as-root -np 1 helloworld
Hello world from processor OpenWrt, rank 0 1
root@OpenWrt:/# /openmpi/bin/mpirun --allow-run-as-root -np 2 helloworld
Hello world from processor OpenWrt, rank 1 2
Hello world from processor OpenWrt, rank 0 2
root@OpenWrt:/# /openmpi/bin/mpirun --allow-run-as-root -np 4 helloworld
Hello world from processor OpenWrt, rank 0 4
Hello world from processor OpenWrt, rank 2 4
Hello world from processor OpenWrt, rank 3 4
Hello world from processor OpenWrt, rank 1 4


On Tue, Oct 18, 2016 at 8:23 PM, Kawashima, Takahiro <
t-kawash...@jp.fujitsu.com> wrote:

> Hi,
>
> You did *not* specify the following options to configure, right?
> Specifying all these will cause a problem.
>
>   --disable-mmap-shmem
>   --disable-posix-shmem
>   --disable-sysv-shmem
>
> Please send the output of the following command.
>
>   mpirun --allow-run-as-root -np 1 --mca shmem_base_verbose 100 helloworld
>
> And, give us the config.log file which is output in the
> top directory where configure is executed.
> Put it on the web or send the compressed (xz or bzip2 is better) file.
>
> Regards,
> Takahiro Kawashima
>
> > Hi Gilles,
> >
> > Thank you for reply,
> >
> > After doing below config options also
> >
> > ./configure --enable-orterun-prefix-by-default
> > --prefix="/home/nmahesh//home/nmahesh/Workspace/ARM_MPI/armmpi/openmpi"
> > CC=arm-openwrt-linux-muslgnueabi-gcc
> > CXX=arm-openwrt-linux-muslgnueabi-g++
> > --host=arm-openwrt-linux-muslgnueabi
> > --enable-script-wrapper-compilers
> > --disable-mpi-fortran
> > --enable-shared
> > --disable-dlopen
> >
> > it's configured ,make & make install successfully.
> >
> > i compiled  *helloworld.c *programm got executable for *arm* as below(by
> > checking the readelf *armhelloworld*),
> >
> >
> > *nmahesh@nmahesh-H81MLV3:~/Workspace/ARM_MPI/mpi$
> > /home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
> > -L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
> helloworld*
> >
> > But ,while i run using mpirun on target board as below
> >
> > root@OpenWrt:/# mpirun --allow-run-as-root -np 1 helloworld
> > 
> --
> > It looks like opal_init failed for some reason; your parallel process is
> > likely to abort.  There are many reasons that a parallel process can
> > fail during opal_init; some of which are due to configuration or
> > environment problems.  This failure appears to be an internal failure;
> > here's some additional information (which may only be relevant to an
> > Open MPI developer):
> >
> >   opal_shmem_base_select failed
> >   --> Returned value -1 instead of OPAL_SUCCESS
> >
> > Kindly help me.
> >
> > On Tue, Oct 18, 2016 at 7:31 PM, Mahesh Nanavalla <
> > mahesh.nanavalla...@gmail.com> wrote:
> >
> > > Hi Gilles,
> > >
> > > Thank you for reply,
> > >
> > > After doing below config options also
> > >
> > > ./configure --enable-orterun-prefix-by-default
> > > --prefix="/home/nmahesh//home/nmahesh/Workspace/ARM_MPI/
> armmpi/openmpi"
> > > CC=arm-openwrt-linux-muslgnueabi-gcc
> > > CXX=arm-openwrt-linux-muslgnueabi-g++
> > > --host=arm-openwrt-linux-muslgnueabi
> > > --enable-script-wrapper-compilers
> > > --disable-mpi-fortran
> > > --enable-shared
> > > --disable-dlopen
> > >
> > > it's configured ,make & make install successfully.
> > >
> > > i compiled  *helloworld.c *programm got executable for *arm* as
> below(by
> > > checking the readelf *armhelloworld*),
> > >
> > >
> > > *nmahesh@nmahesh-H81MLV3:~/Workspace/ARM_MPI/mpi$
> > > /home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
> > > -L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
> helloworld*
> > >
> > > But ,while i run using mpirun on target board as below
> > >
> > > root@OpenWrt:/# mpirun --allow-run-as-root -np 1 helloworld
> > > 
> --
> > > It looks like opal_init failed for some reason; your parallel process
> is
> > > likely to abort.  There are many

[OMPI users] communicator with MPI_Reduce

Re: [OMPI users] Problem building OpenMPI with CUDA 8.0

Re: [MTT users] MTT Server Downtime - Fri., Oct. 21, 2016 (Updated)

Re: [OMPI users] openmpi-1.10.3 cross compile configure options for arm-openwrt-linux-muslgnueabi on x86_64-linux-gnu

Re: [OMPI users] openmpi-1.10.3 cross compile configure options for arm-openwrt-linux-muslgnueabi on x86_64-linux-gnu

Re: [OMPI users] openmpi-1.10.3 cross compile configure options for arm-openwrt-linux-muslgnueabi on x86_64-linux-gnu

Re: [OMPI users] openmpi-1.10.3 cross compile configure options for arm-openwrt-linux-muslgnueabi on x86_64-linux-gnu

Re: [OMPI users] openmpi-1.10.3 cross compile configure options for arm-openwrt-linux-muslgnueabi on x86_64-linux-gnu

[OMPI users] fail to run client/server mode using MPI_COMM_ACCEPT/MPI_COMM_CONNECT without mpirun

Re: [OMPI users] openmpi-1.10.3 cross compile configure options for arm-openwrt-linux-muslgnueabi on x86_64-linux-gnu

10 matches

Site Navigation

Mail list logo

Footer information