Re: [OMPI users] Openmpi 2.0.1 build --with-psm2 failed on CentOS 7.2

[Limin Gu]

Thank you very much, MAC!

Limin




On Tue, Oct 11, 2016 at 10:15 PM, Cabral, Matias A <
matias.a.cab...@intel.com> wrote:

> Building psm2 should not be complicated (in case you cannot find a newer
> binary):
>
>
>
> https://github.com/01org/opa-psm2
>
>
>
> Note that newer rpm are named hfi1-psm*
>
>
>
>
>
> _MAC
>
>
>
> *From:* users [mailto:users-boun...@lists.open-mpi.org] *On Behalf Of *Limin
> Gu
> *Sent:* Tuesday, October 11, 2016 6:44 PM
> *To:* Open MPI Users 
> *Subject:* Re: [OMPI users] Openmpi 2.0.1 build --with-psm2 failed on
> CentOS 7.2
>
>
>
> Thanks Gilles!
>
>
>
> Limin
>
>
>
> On Tue, Oct 11, 2016 at 9:33 PM, Gilles Gouaillardet 
> wrote:
>
> Limin,
>
>
>
> It seems libpsm2 provided by Centos 7 is a bit too old
>
> all symbols are prefixed with psm_, and Open MPI expect they are prefixed
> with psm2_
>
>
> i am afraid your only option is to manually install the latest libpsm2 and
> then configure again with your psm2 install dir
>
>
> Cheers,
>
> Gilles
>
>
>
> On 10/12/2016 9:57 AM, Limin Gu wrote:
>
> Hi MAC,
>
>
>
> It seems /usr/lib64/libpsm2.so.2 has no symbols. Can configure check some
> other ways?
>
>
>
>
>
> [root@uranus ~]# rpm -qi libpsm2-0.7-4.el7.x86_64
>
> Name: libpsm2
>
> Version : 0.7
>
> Release : 4.el7
>
> Architecture: x86_64
>
> Install Date: Tue 11 Oct 2016 05:45:59 PM PDT
>
> Group   : System Environment/Libraries
>
> Size: 400282
>
> License : GPLv2 or BSD
>
> Signature   : RSA/SHA256, Wed 25 Nov 2015 07:02:20 AM PST, Key ID
> 24c6a8a7f4a80eb5
>
> Source RPM  : libpsm2-0.7-4.el7.src.rpm
>
> Build Date  : Fri 20 Nov 2015 08:05:13 AM PST
>
> Build Host  : worker1.bsys.centos.org
>
> Relocations : (not relocatable)
>
> Packager: CentOS BuildSystem 
>
> Vendor  : CentOS
>
> URL : http://www.intel.com/
>
> Summary : Intel PSM Libraries
>
> Description :
>
> The PSM Messaging API, or PSM API, is Intel's low-level
>
> user-level communications interface for the Truescale
>
> family of products. PSM users are enabled with mechanisms
>
> necessary to implement higher level communications
>
> interfaces in parallel environments.
>
> [root@uranus ~]# objdump -p /usr/lib64/libpsm2.so.2 |grep SONAME
>
>   *SONAME*   libpsm2.so.2
>
> [root@uranus ~]# nm /usr/lib64/libpsm2.so.2
>
> nm: /usr/lib64/libpsm2.so.2: no symbols
>
> [root@uranus ~]#
>
>
>
>
>
> Thanks!
>
> Limin
>
>
>
>
>
> On Tue, Oct 11, 2016 at 7:00 PM, Cabral, Matias A <
> matias.a.cab...@intel.com> wrote:
>
> Hi  Limin,
>
>
>
> psm2_mq_irecv2 should be in libpsm2.so.  I’m not quite sure how CentOS
> packs it so I would like a little more info about the version being used.
> Some things to share:
>
>
>
> >rpm -qi libpsm2-0.7-4.el7.x86_64
>
> > objdump –p /usr/lib64/libpsm2.so |grep SONAME
>
> >nm /usr/lib64/libpsm2.so |grep psm2_mq_irecv2 (will not work if the lib
> Stripped)
>
>
>
>
>
> Thanks,
>
> _MAC
>
>
>
> *From:* users [mailto:users-boun...@lists.open-mpi.org] *On Behalf Of *Limin
> Gu
> *Sent:* Tuesday, October 11, 2016 2:58 PM
> *To:* Open MPI Users 
> *Subject:* [OMPI users] Openmpi 2.0.1 build --with-psm2 failed on CentOS
> 7.2
>
>
>
> Hi All,
>
> I am trying to build openmpi 2.0.1 on a CentOS 7.2 system, and I have
> following libpsm2 packages installed:
>
> libpsm2-0.7-4.el7.x86_64
> libpsm2-compat-0.7-4.el7.x86_64
> libpsm2-compat-devel-0.7-4.el7.x86_64
> libpsm2-devel-0.7-4.el7.x86_64
>
> I added --with-psm2 to my configure, but it failed:
>
> --- MCA component mtl:psm2 (m4 configuration macro)
> checking for MCA component mtl:psm2 compile mode... static
> checking --with-psm2 value... simple ok (unspecified)
> checking --with-psm2-libdir value... simple ok (unspecified)
> checking psm2.h usability... yes
> checking psm2.h presence... yes
> checking for psm2.h... yes
> looking for library without search path
> checking for library containing psm2_mq_irecv2... no
> configure: error: PSM2 support requested but not found.  Aborting
> error: Bad exit status from /var/tmp/rpm-tmp.TLxu8O (%build)
>
>
>
>
>
> /usr/lib64/libpsm2.so is on the system though.
>
>
>
> What else libraries do I need for psm2?
>
>
>
> Thank you!
>
>
>
>
> ___
> users mailing list
> users@lists.open-mpi.org
> https://rfd.newmexicoconsortium.org/mailman/listinfo/users
>
>
>
>
>
> ___
>
> users mailing list
>
> users@lists.open-mpi.org
>
> https://rfd.newmexicoconsortium.org/mailman/listinfo/users
>
>
>
>
> ___
> users mailing list
> users@lists.open-mpi.org
> https://rfd.newmexicoconsortium.org/mailman/listinfo/users
>
>
>
> ___
> users mailing list
> users@lists.open-mpi.org
> https://rfd.newmexicoconsortium.org/mailman/listinfo/users
>
___
users mailing list
users@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/l

Re: [OMPI users] Openmpi 2.0.1 build --with-psm2 failed on CentOS 7.2

[Cabral, Matias A]

Building psm2 should not be complicated (in case you cannot find a newer 
binary):

https://github.com/01org/opa-psm2


Note that newer rpm are named hfi1-psm*


_MAC

From: users [mailto:users-boun...@lists.open-mpi.org] On Behalf Of Limin Gu
Sent: Tuesday, October 11, 2016 6:44 PM
To: Open MPI Users 
Subject: Re: [OMPI users] Openmpi 2.0.1 build --with-psm2 failed on CentOS 7.2


Thanks Gilles!



Limin

On Tue, Oct 11, 2016 at 9:33 PM, Gilles Gouaillardet 
mailto:gil...@rist.or.jp>> wrote:

Limin,



It seems libpsm2 provided by Centos 7 is a bit too old

all symbols are prefixed with psm_, and Open MPI expect they are prefixed with 
psm2_

i am afraid your only option is to manually install the latest libpsm2 and then 
configure again with your psm2 install dir


Cheers,

Gilles

On 10/12/2016 9:57 AM, Limin Gu wrote:
Hi MAC,

It seems /usr/lib64/libpsm2.so.2 has no symbols. Can configure check some other 
ways?



[root@uranus ~]# rpm -qi libpsm2-0.7-4.el7.x86_64

Name: libpsm2

Version : 0.7

Release : 4.el7

Architecture: x86_64

Install Date: Tue 11 Oct 2016 05:45:59 PM PDT

Group   : System Environment/Libraries

Size: 400282

License : GPLv2 or BSD

Signature   : RSA/SHA256, Wed 25 Nov 2015 07:02:20 AM PST, Key ID 
24c6a8a7f4a80eb5

Source RPM  : libpsm2-0.7-4.el7.src.rpm

Build Date  : Fri 20 Nov 2015 08:05:13 AM PST

Build Host  : worker1.bsys.centos.org

Relocations : (not relocatable)

Packager: CentOS BuildSystem 

Vendor  : CentOS

URL : http://www.intel.com/

Summary : Intel PSM Libraries

Description :

The PSM Messaging API, or PSM API, is Intel's low-level

user-level communications interface for the Truescale

family of products. PSM users are enabled with mechanisms

necessary to implement higher level communications

interfaces in parallel environments.

[root@uranus ~]# objdump -p /usr/lib64/libpsm2.so.2 |grep SONAME

  SONAME   libpsm2.so.2

[root@uranus ~]# nm /usr/lib64/libpsm2.so.2

nm: /usr/lib64/libpsm2.so.2: no symbols

[root@uranus ~]#


Thanks!
Limin


On Tue, Oct 11, 2016 at 7:00 PM, Cabral, Matias A 
mailto:matias.a.cab...@intel.com>> wrote:
Hi  Limin,

psm2_mq_irecv2 should be in libpsm2.so.  I’m not quite sure how CentOS packs it 
so I would like a little more info about the version being used. Some things to 
share:

>rpm -qi libpsm2-0.7-4.el7.x86_64
> objdump –p /usr/lib64/libpsm2.so |grep SONAME
>nm /usr/lib64/libpsm2.so |grep psm2_mq_irecv2 (will not work if the lib 
>Stripped)


Thanks,
_MAC

From: users 
[mailto:users-boun...@lists.open-mpi.org]
 On Behalf Of Limin Gu
Sent: Tuesday, October 11, 2016 2:58 PM
To: Open MPI Users mailto:users@lists.open-mpi.org>>
Subject: [OMPI users] Openmpi 2.0.1 build --with-psm2 failed on CentOS 7.2

Hi All,

I am trying to build openmpi 2.0.1 on a CentOS 7.2 system, and I have following 
libpsm2 packages installed:

libpsm2-0.7-4.el7.x86_64
libpsm2-compat-0.7-4.el7.x86_64
libpsm2-compat-devel-0.7-4.el7.x86_64
libpsm2-devel-0.7-4.el7.x86_64

I added --with-psm2 to my configure, but it failed:

--- MCA component mtl:psm2 (m4 configuration macro)
checking for MCA component mtl:psm2 compile mode... static
checking --with-psm2 value... simple ok (unspecified)
checking --with-psm2-libdir value... simple ok (unspecified)
checking psm2.h usability... yes
checking psm2.h presence... yes
checking for psm2.h... yes
looking for library without search path
checking for library containing psm2_mq_irecv2... no
configure: error: PSM2 support requested but not found.  Aborting
error: Bad exit status from /var/tmp/rpm-tmp.TLxu8O (%build)


/usr/lib64/libpsm2.so is on the system though.

What else libraries do I need for psm2?

Thank you!


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



___

users mailing list

users@lists.open-mpi.org

https://rfd.newmexicoconsortium.org/mailman/listinfo/users


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

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

Re: [OMPI users] Openmpi 2.0.1 build --with-psm2 failed on CentOS 7.2

[Limin Gu]

Thanks Gilles!


Limin

On Tue, Oct 11, 2016 at 9:33 PM, Gilles Gouaillardet 
wrote:

> Limin,
>
>
> It seems libpsm2 provided by Centos 7 is a bit too old
>
> all symbols are prefixed with psm_, and Open MPI expect they are prefixed
> with psm2_
>
> i am afraid your only option is to manually install the latest libpsm2 and
> then configure again with your psm2 install dir
>
>
> Cheers,
>
> Gilles
>
>
> On 10/12/2016 9:57 AM, Limin Gu wrote:
>
> Hi MAC,
>
> It seems /usr/lib64/libpsm2.so.2 has no symbols. Can configure check some
> other ways?
>
>
> [root@uranus ~]# rpm -qi libpsm2-0.7-4.el7.x86_64
>
> Name: libpsm2
>
> Version : 0.7
>
> Release : 4.el7
>
> Architecture: x86_64
>
> Install Date: Tue 11 Oct 2016 05:45:59 PM PDT
>
> Group   : System Environment/Libraries
>
> Size: 400282
>
> License : GPLv2 or BSD
>
> Signature   : RSA/SHA256, Wed 25 Nov 2015 07:02:20 AM PST, Key ID
> 24c6a8a7f4a80eb5
>
> Source RPM  : libpsm2-0.7-4.el7.src.rpm
>
> Build Date  : Fri 20 Nov 2015 08:05:13 AM PST
>
> Build Host  : worker1.bsys.centos.org
>
> Relocations : (not relocatable)
>
> Packager: CentOS BuildSystem 
>
> Vendor  : CentOS
>
> URL : http://www.intel.com/
>
> Summary : Intel PSM Libraries
>
> Description :
>
> The PSM Messaging API, or PSM API, is Intel's low-level
>
> user-level communications interface for the Truescale
>
> family of products. PSM users are enabled with mechanisms
>
> necessary to implement higher level communications
>
> interfaces in parallel environments.
>
> [root@uranus ~]# objdump -p /usr/lib64/libpsm2.so.2 |grep SONAME
>
>   *SONAME*   libpsm2.so.2
>
> [root@uranus ~]# nm /usr/lib64/libpsm2.so.2
>
> nm: /usr/lib64/libpsm2.so.2: no symbols
>
> [root@uranus ~]#
>
>
> Thanks!
> Limin
>
>
> On Tue, Oct 11, 2016 at 7:00 PM, Cabral, Matias A <
> matias.a.cab...@intel.com> wrote:
>
>> Hi  Limin,
>>
>>
>>
>> psm2_mq_irecv2 should be in libpsm2.so.  I’m not quite sure how CentOS
>> packs it so I would like a little more info about the version being used.
>> Some things to share:
>>
>>
>>
>> >rpm -qi libpsm2-0.7-4.el7.x86_64
>>
>> > objdump –p /usr/lib64/libpsm2.so |grep SONAME
>>
>> >nm /usr/lib64/libpsm2.so |grep psm2_mq_irecv2 (will not work if the lib
>> Stripped)
>>
>>
>>
>>
>>
>> Thanks,
>>
>> _MAC
>>
>>
>>
>> *From:* users [mailto:users-boun...@lists.open-mpi.org] *On Behalf Of *Limin
>> Gu
>> *Sent:* Tuesday, October 11, 2016 2:58 PM
>> *To:* Open MPI Users 
>> *Subject:* [OMPI users] Openmpi 2.0.1 build --with-psm2 failed on CentOS
>> 7.2
>>
>>
>>
>> Hi All,
>>
>> I am trying to build openmpi 2.0.1 on a CentOS 7.2 system, and I have
>> following libpsm2 packages installed:
>>
>> libpsm2-0.7-4.el7.x86_64
>> libpsm2-compat-0.7-4.el7.x86_64
>> libpsm2-compat-devel-0.7-4.el7.x86_64
>> libpsm2-devel-0.7-4.el7.x86_64
>>
>> I added --with-psm2 to my configure, but it failed:
>>
>> --- MCA component mtl:psm2 (m4 configuration macro)
>> checking for MCA component mtl:psm2 compile mode... static
>> checking --with-psm2 value... simple ok (unspecified)
>> checking --with-psm2-libdir value... simple ok (unspecified)
>> checking psm2.h usability... yes
>> checking psm2.h presence... yes
>> checking for psm2.h... yes
>> looking for library without search path
>> checking for library containing psm2_mq_irecv2... no
>> configure: error: PSM2 support requested but not found.  Aborting
>> error: Bad exit status from /var/tmp/rpm-tmp.TLxu8O (%build)
>>
>>
>>
>>
>>
>> /usr/lib64/libpsm2.so is on the system though.
>>
>>
>>
>> What else libraries do I need for psm2?
>>
>>
>>
>> Thank you!
>>
>>
>>
>> ___
>> users mailing list
>> users@lists.open-mpi.org
>> https://rfd.newmexicoconsortium.org/mailman/listinfo/users
>>
>
>
>
> ___
> users mailing 
> listus...@lists.open-mpi.orghttps://rfd.newmexicoconsortium.org/mailman/listinfo/users
>
>
>
> ___
> users mailing list
> users@lists.open-mpi.org
> https://rfd.newmexicoconsortium.org/mailman/listinfo/users
>
___
users mailing list
users@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/users

Re: [OMPI users] Openmpi 2.0.1 build --with-psm2 failed on CentOS 7.2

[Gilles Gouaillardet]

Limin,


It seems libpsm2 provided by Centos 7 is a bit too old

all symbols are prefixed with psm_, and Open MPI expect they are 
prefixed with psm2_



i am afraid your only option is to manually install the latest libpsm2 
and then configure again with your psm2 install dir



Cheers,

Gilles

On 10/12/2016 9:57 AM, Limin Gu wrote:

Hi MAC,

It seems /usr/lib64/libpsm2.so.2 has no symbols. Can configure check 
some other ways?



[root@uranus ~]# rpm -qi libpsm2-0.7-4.el7.x86_64

Name : libpsm2

Version : 0.7

Release : 4.el7

Architecture: x86_64

Install Date: Tue 11 Oct 2016 05:45:59 PM PDT

Group : System Environment/Libraries

Size : 400282

License : GPLv2 or BSD

Signature   : RSA/SHA256, Wed 25 Nov 2015 07:02:20 AM PST, Key ID 
24c6a8a7f4a80eb5


Source RPM  : libpsm2-0.7-4.el7.src.rpm

Build Date  : Fri 20 Nov 2015 08:05:13 AM PST

Build Host  : worker1.bsys.centos.org 

Relocations : (not relocatable)

Packager   : CentOS BuildSystem 

Vendor : CentOS

URL : http://www.intel.com/

Summary : Intel PSM Libraries

Description :

The PSM Messaging API, or PSM API, is Intel's low-level

user-level communications interface for the Truescale

family of products. PSM users are enabled with mechanisms

necessary to implement higher level communications

interfaces in parallel environments.

[root@uranus ~]# objdump -p /usr/lib64/libpsm2.so.2 |grep SONAME

*SONAME*libpsm2.so.2

[root@uranus ~]# nm /usr/lib64/libpsm2.so.2

nm: /usr/lib64/libpsm2.so.2: no symbols

[root@uranus ~]#



Thanks!
Limin


On Tue, Oct 11, 2016 at 7:00 PM, Cabral, Matias A 
mailto:matias.a.cab...@intel.com>> wrote:


Hi Limin,

psm2_mq_irecv2 should be in libpsm2.so.  I’m not quite sure how
CentOS packs it so I would like a little more info about the
version being used. Some things to share:

>rpm -qi libpsm2-0.7-4.el7.x86_64

> objdump –p /usr/lib64/libpsm2.so |grep SONAME

>nm /usr/lib64/libpsm2.so |grep psm2_mq_irecv2 (will not work if the
lib Stripped)

Thanks,

_MAC

*From:*users [mailto:users-boun...@lists.open-mpi.org
] *On Behalf Of *Limin Gu
*Sent:* Tuesday, October 11, 2016 2:58 PM
*To:* Open MPI Users mailto:users@lists.open-mpi.org>>
*Subject:* [OMPI users] Openmpi 2.0.1 build --with-psm2 failed on
CentOS 7.2

Hi All,

I am trying to build openmpi 2.0.1 on a CentOS 7.2 system, and I
have following libpsm2 packages installed:

libpsm2-0.7-4.el7.x86_64
libpsm2-compat-0.7-4.el7.x86_64
libpsm2-compat-devel-0.7-4.el7.x86_64
libpsm2-devel-0.7-4.el7.x86_64

I added --with-psm2 to my configure, but it failed:

--- MCA component mtl:psm2 (m4 configuration macro)
checking for MCA component mtl:psm2 compile mode... static
checking --with-psm2 value... simple ok (unspecified)
checking --with-psm2-libdir value... simple ok (unspecified)
checking psm2.h usability... yes
checking psm2.h presence... yes
checking for psm2.h... yes
looking for library without search path
checking for library containing psm2_mq_irecv2... no
configure: error: PSM2 support requested but not found.  Aborting
error: Bad exit status from /var/tmp/rpm-tmp.TLxu8O (%build)

/usr/lib64/libpsm2.so is on the system though.

What else libraries do I need for psm2?

Thank you!


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





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


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

Re: [OMPI users] Openmpi 2.0.1 build --with-psm2 failed on CentOS 7.2

[Limin Gu]

Hi MAC,

It seems /usr/lib64/libpsm2.so.2 has no symbols. Can configure check some
other ways?


[root@uranus ~]# rpm -qi libpsm2-0.7-4.el7.x86_64

Name: libpsm2

Version : 0.7

Release : 4.el7

Architecture: x86_64

Install Date: Tue 11 Oct 2016 05:45:59 PM PDT

Group   : System Environment/Libraries

Size: 400282

License : GPLv2 or BSD

Signature   : RSA/SHA256, Wed 25 Nov 2015 07:02:20 AM PST, Key ID
24c6a8a7f4a80eb5

Source RPM  : libpsm2-0.7-4.el7.src.rpm

Build Date  : Fri 20 Nov 2015 08:05:13 AM PST

Build Host  : worker1.bsys.centos.org

Relocations : (not relocatable)

Packager: CentOS BuildSystem 

Vendor  : CentOS

URL : http://www.intel.com/

Summary : Intel PSM Libraries

Description :

The PSM Messaging API, or PSM API, is Intel's low-level

user-level communications interface for the Truescale

family of products. PSM users are enabled with mechanisms

necessary to implement higher level communications

interfaces in parallel environments.

[root@uranus ~]# objdump -p /usr/lib64/libpsm2.so.2 |grep SONAME

  *SONAME*   libpsm2.so.2

[root@uranus ~]# nm /usr/lib64/libpsm2.so.2

nm: /usr/lib64/libpsm2.so.2: no symbols

[root@uranus ~]#


Thanks!
Limin


On Tue, Oct 11, 2016 at 7:00 PM, Cabral, Matias A  wrote:

> Hi  Limin,
>
>
>
> psm2_mq_irecv2 should be in libpsm2.so.  I’m not quite sure how CentOS
> packs it so I would like a little more info about the version being used.
> Some things to share:
>
>
>
> >rpm -qi libpsm2-0.7-4.el7.x86_64
>
> > objdump –p /usr/lib64/libpsm2.so |grep SONAME
>
> >nm /usr/lib64/libpsm2.so |grep psm2_mq_irecv2 (will not work if the lib
> Stripped)
>
>
>
>
>
> Thanks,
>
> _MAC
>
>
>
> *From:* users [mailto:users-boun...@lists.open-mpi.org] *On Behalf Of *Limin
> Gu
> *Sent:* Tuesday, October 11, 2016 2:58 PM
> *To:* Open MPI Users 
> *Subject:* [OMPI users] Openmpi 2.0.1 build --with-psm2 failed on CentOS
> 7.2
>
>
>
> Hi All,
>
> I am trying to build openmpi 2.0.1 on a CentOS 7.2 system, and I have
> following libpsm2 packages installed:
>
> libpsm2-0.7-4.el7.x86_64
> libpsm2-compat-0.7-4.el7.x86_64
> libpsm2-compat-devel-0.7-4.el7.x86_64
> libpsm2-devel-0.7-4.el7.x86_64
>
> I added --with-psm2 to my configure, but it failed:
>
> --- MCA component mtl:psm2 (m4 configuration macro)
> checking for MCA component mtl:psm2 compile mode... static
> checking --with-psm2 value... simple ok (unspecified)
> checking --with-psm2-libdir value... simple ok (unspecified)
> checking psm2.h usability... yes
> checking psm2.h presence... yes
> checking for psm2.h... yes
> looking for library without search path
> checking for library containing psm2_mq_irecv2... no
> configure: error: PSM2 support requested but not found.  Aborting
> error: Bad exit status from /var/tmp/rpm-tmp.TLxu8O (%build)
>
>
>
>
>
> /usr/lib64/libpsm2.so is on the system though.
>
>
>
> What else libraries do I need for psm2?
>
>
>
> Thank you!
>
>
>
> ___
> users mailing list
> users@lists.open-mpi.org
> https://rfd.newmexicoconsortium.org/mailman/listinfo/users
>
___
users mailing list
users@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/users

Re: [OMPI users] Using Open MPI with multiple versions of GCC and G++

[Gilles Gouaillardet]

FWIW.


mpicxx does two things :

1) use the C++ compiler (e.g. g++)

2) if Open MPI was configured with (deprecated) C++ bindings (e.g. 
--enable-mpi-cxx), then link with


the Open MPI C++ library that contains bindings.


IIRC, Open MPI v1.10 does build C++ bindings by default, but v2.0 does 
not any more.


So if you are *not* using Open MPI C++ bindings (for example, you use C 
bindings only,


or you use a third party lib such as BoostMPI), then you should not be 
worried about


compatibility between C++ versions.


Cheers,


Gilles


On 10/12/2016 12:23 AM, Dave Love wrote:

"Jeff Squyres (jsquyres)"  writes:


Especially with C++, the Open MPI team strongly recommends you
building Open MPI with the target versions of the compilers that you
want to use.  Unexpected things can happen when you start mixing
versions of compilers (particularly across major versions of a
compiler).  To be clear: compilers are *supposed* to be compatible
across multiple versions (i.e., compile a library with one version of
the compiler, and then use that library with an application compiled
by a different version of the compiler), but a) there's other issues,
such as C++ ABI issues and other run-time bootstrapping that can
complicate things, and b) bugs in forward and backward compatibility
happen.

Is that actually observed in GNU/Linux systems?  I'd expect it either to
work or just fail to link.  For instance, the RHEL 6 devtoolset-4 (gcc
5) uses the system libstdc++, and the system compiler is gcc 4.4.


The short answer is in this FAQ item:
https://www.open-mpi.org/faq/?category=mpi-apps#override-wrappers-after-v1.0.
Substituting the gcc 5 compiler may work just fine.

For what it's worth, not for GNU Fortran, which unfortunately changes
the module format incompatibly with each release, or at least most
releases.
___
users mailing list
users@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/users



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

Re: [OMPI users] Openmpi 2.0.1 build --with-psm2 failed on CentOS 7.2

[Jeff Squyres (jsquyres)]

Limin --

Can you send the items listed here:

https://www.open-mpi.org/community/help/


> On Oct 11, 2016, at 4:00 PM, Cabral, Matias A  
> wrote:
> 
> Hi  Limin,
>  
> psm2_mq_irecv2 should be in libpsm2.so.  I’m not quite sure how CentOS packs 
> it so I would like a little more info about the version being used. Some 
> things to share:
>  
> >rpm -qi libpsm2-0.7-4.el7.x86_64
> > objdump –p /usr/lib64/libpsm2.so |grep SONAME
> >nm /usr/lib64/libpsm2.so |grep psm2_mq_irecv2 (will not work if the lib 
> >Stripped)
>  
>  
> Thanks,
> _MAC
>  
> From: users [mailto:users-boun...@lists.open-mpi.org] On Behalf Of Limin Gu
> Sent: Tuesday, October 11, 2016 2:58 PM
> To: Open MPI Users 
> Subject: [OMPI users] Openmpi 2.0.1 build --with-psm2 failed on CentOS 7.2
>  
> Hi All,
> 
> I am trying to build openmpi 2.0.1 on a CentOS 7.2 system, and I have 
> following libpsm2 packages installed:
> 
> libpsm2-0.7-4.el7.x86_64
> libpsm2-compat-0.7-4.el7.x86_64
> libpsm2-compat-devel-0.7-4.el7.x86_64
> libpsm2-devel-0.7-4.el7.x86_64
> 
> I added --with-psm2 to my configure, but it failed:
> 
> --- MCA component mtl:psm2 (m4 configuration macro)
> checking for MCA component mtl:psm2 compile mode... static
> checking --with-psm2 value... simple ok (unspecified)
> checking --with-psm2-libdir value... simple ok (unspecified)
> checking psm2.h usability... yes
> checking psm2.h presence... yes
> checking for psm2.h... yes
> looking for library without search path
> checking for library containing psm2_mq_irecv2... no
> configure: error: PSM2 support requested but not found.  Aborting
> error: Bad exit status from /var/tmp/rpm-tmp.TLxu8O (%build)
>  
>  
> /usr/lib64/libpsm2.so is on the system though.
>  
> What else libraries do I need for psm2?
>  
> Thank you!
>  
> ___
> 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: [OMPI users] Openmpi 2.0.1 build --with-psm2 failed on CentOS 7.2

[Cabral, Matias A]

Hi  Limin,

psm2_mq_irecv2 should be in libpsm2.so.  I’m not quite sure how CentOS packs it 
so I would like a little more info about the version being used. Some things to 
share:

>rpm -qi libpsm2-0.7-4.el7.x86_64
> objdump –p /usr/lib64/libpsm2.so |grep SONAME
>nm /usr/lib64/libpsm2.so |grep psm2_mq_irecv2 (will not work if the lib 
>Stripped)


Thanks,
_MAC

From: users [mailto:users-boun...@lists.open-mpi.org] On Behalf Of Limin Gu
Sent: Tuesday, October 11, 2016 2:58 PM
To: Open MPI Users 
Subject: [OMPI users] Openmpi 2.0.1 build --with-psm2 failed on CentOS 7.2

Hi All,

I am trying to build openmpi 2.0.1 on a CentOS 7.2 system, and I have following 
libpsm2 packages installed:

libpsm2-0.7-4.el7.x86_64
libpsm2-compat-0.7-4.el7.x86_64
libpsm2-compat-devel-0.7-4.el7.x86_64
libpsm2-devel-0.7-4.el7.x86_64

I added --with-psm2 to my configure, but it failed:

--- MCA component mtl:psm2 (m4 configuration macro)
checking for MCA component mtl:psm2 compile mode... static
checking --with-psm2 value... simple ok (unspecified)
checking --with-psm2-libdir value... simple ok (unspecified)
checking psm2.h usability... yes
checking psm2.h presence... yes
checking for psm2.h... yes
looking for library without search path
checking for library containing psm2_mq_irecv2... no
configure: error: PSM2 support requested but not found.  Aborting
error: Bad exit status from /var/tmp/rpm-tmp.TLxu8O (%build)


/usr/lib64/libpsm2.so is on the system though.

What else libraries do I need for psm2?

Thank you!

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

[OMPI users] Openmpi 2.0.1 build --with-psm2 failed on CentOS 7.2

[Limin Gu]

Hi All,

I am trying to build openmpi 2.0.1 on a CentOS 7.2 system, and I have
following libpsm2 packages installed:

libpsm2-0.7-4.el7.x86_64
libpsm2-compat-0.7-4.el7.x86_64
libpsm2-compat-devel-0.7-4.el7.x86_64
libpsm2-devel-0.7-4.el7.x86_64

I added --with-psm2 to my configure, but it failed:

--- MCA component mtl:psm2 (m4 configuration macro)
checking for MCA component mtl:psm2 compile mode... static
checking --with-psm2 value... simple ok (unspecified)
checking --with-psm2-libdir value... simple ok (unspecified)
checking psm2.h usability... yes
checking psm2.h presence... yes
checking for psm2.h... yes
looking for library without search path
checking for library containing psm2_mq_irecv2... no
configure: error: PSM2 support requested but not found.  Aborting
error: Bad exit status from /var/tmp/rpm-tmp.TLxu8O (%build)


/usr/lib64/libpsm2.so is on the system though.

What else libraries do I need for psm2?

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

Re: [OMPI users] Crash during MPI_Finalize

[Jeff Squyres (jsquyres)]

On Oct 11, 2016, at 8:58 AM, George Reeke  wrote:
> 
> George B. et al,
>   --Is it normal to top-post on this list?  I am following your
> example but other lists I am on prefer bottom-posting.

Stylistic note: we do both on this list.  Specifically: there's no religious 
hate if you top-post.

-- 
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: [OMPI users] Crash during MPI_Finalize

[George Reeke]

George B. et al,
   --Is it normal to top-post on this list?  I am following your
example but other lists I am on prefer bottom-posting.
   --I attach the complete code of the andmsg program, as it is
quite short (some bits removed for brevity and I have omitted
my headers and startup function aninit() as they are probably
irrelevant to the problem).  The idea I had
was to have each node in the main program send a SHUTDOWN_ANDMSG
when it is ready to shut down and andmsg counts these and does not
begin its own shutdown until the number received matches the number
of nodes in the main program.  Debugging shows that the number it
is counting is correct.  It then sends a message back to the main
application so each node there waits to shut down until they are
all ready to shut down.  I developed this protocol with tiny test
programs where just having everybody stop when finished led to
similar MPI console messages.  In my initial posting I did not
show the code that counts these messages; that is why your matchup
seems wrong.  Also, I have since added code to the main nodes to do
an IProbe before stopping and report any unread messages.  There are
none.
   --I cannot really post the main program, as it is about 40,000
lines of C code, recently updated for parallel processing with MPI.
When I have time I will try to make a short version for further testing.
   Thanks,
   George Reeke


On Mon, 2016-10-10 at 21:37 -0400, George Bosilca wrote:
> George,
> 
> 
> There is too much information missing from your example. If I try to
> run the code on the top assuming the process is is_host(NC.node), I
> have on NC.commd 3 communications (ignore the others):
> 
> 
> rc = MPI_Send(&ival, 1, MPI_INT, NC.dmsgid,
> SHUTDOWN_ANDMSG, NC.commd);
> MPI_Recv(&ival, 1, MPI_INT, NC.dmsgid, CLOSING_ANDMSG, NC.commd,
> MPI_STATUS_IGNORE);
> rc = MPI_Send(&ival, 1, MPI_INT, NC.dmsgid, SHUTDOWN_ANDMSG,
> NC.commd); }
> 
> 
> 
> On the andmsg I can only see 2 matching communications:
> 
> 
> rc = MPI_Send(&num2stop, 1, MPI_INT, NC.hostid, CLOSING_ANDMSG,
> NC.commd);
> rc = MPI_Recv(&sdmsg, 1, MPI_INT, NC.hostid, MPI_ANY_TAG, NC.commd,
> MPI_STATUS_IGNORE);
> 
> 
> 
> So either there is a pending send (which is treated as an eager by
> OMPI because it is of length 4 bytes), or there is something missing
> on the code example. Can you post a more complete example ?
> 
> 
> Thanks,
> George.
> 
> 


/* (c) Copyright 2016, The Rockefeller University */
/* $Id: andmsg.c 1 2009-12-29 23:04:48Z  $ */
/***
*  andmsg.c*
*  *
* EDITED VERSION FOR POSTING   *
*  *
*  This is the main program spawned by a parallel program using the*
*  MPI library to receive "out-of-stream" messages and act upon them.  *
*  *
*  This program should receive (as ASCII strings) two command-line *
*  arguments from aninit in the parent (spawning) process: *
*  (1) The number of SHUTDOWN_ANDMSG messages needed to quit   *
*  (2) Any debug codes relevant to this process*
*--*
*  V1A, 07/06/16, GNR - New program*
*  ==>, 08/10/16, GNR - Last mod before committing to svn repository   *
***/

#define MAIN
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include "sysdef.h"
#include "mpitools.h"
#include "swap.h"

#define ANDDBG

int main(int argc, char *argv[]) {

#ifdef ANDDBG
   FILE *andlog;   /* Debug log file */
#endif
   struct {/* Struct for receiving messages */
  /* This inner struct is used by the main application to
  *  encode information for error messages going to andmsg.  */
  struct ErrMsg Err;
  char msg[MAX_EMSG_LENGTH];
  } emsg;
   MPI_Status mstat;
   int msrc, mtag;
   int sdmsg;
   int num2stop;

/* Startup */

   /* This routine makes inquiries of the MPI library to fill
   *  in the communicators, numbers of nodes, etc. in the NC
   *  common structure.  The header mpitools.h defines this
   *  structure.  */
   aninit(0, 0, 0);
   MPI_Comm_get_parent(&NC.commd);
   /* Interpret command-line arguments */
   if (argc > 1) NC.debug = atoi(argv[2]);
   if (argc > 0) num2stop = atoi(argv[1]);
   if (NC.debug & DBG_START) {
  /* ssprintf is my own version of sprintf with some mods */
  fputs(ssprintf(NULL,"andmsg started w/num2stop = %d, "
 "NC.debug = 0x%x\n", num2stop, NC.debug), stderr);
  fflush(stderr);
  }

#ifdef ANDDBG
   andlog = fopen("/var/tmp/andmsg.debug.l

Re: [OMPI users] centos 7.2 openmpi from repo, stdout issue

[Emre Brookes]

FYI -

We upgraded to Open MPI 2.0.1 and this resolved the issue.

Of course, it was not so simple to get there, as the Centos 7.2 default 
gcc (4.8.4) produced "internal compiler error" when recompiling NAMD 
with OMPI 2.0.1 and 1.10.4.  So we had to install a newer compiler.  One 
interesting result was the OMPI + NAMD performance comparisons with 
various gcc versions.  gcc 5.4.0 significantly outperformed gcc 6.2.0 on 
our tests...


Jeff Squyres (jsquyres) wrote:

We did have some kind of stdout/stderr truncation issue a little while ago, but 
I don't remember what version it specifically affected.

I would definitely update to at least Open MPI 1.10.4 (lots of bug fixes since 
1.10.0).  Better would be to update to Open MPI 2.0.1 -- that's the current 
generation and where all of our work is going these days.



On Oct 5, 2016, at 9:23 AM, Emre Brookes  wrote:

$ cat /etc/redhat-release
CentOS Linux release 7.2.1511 (Core)

$ yum list installed | grep openmpi
openmpi.x86_64 1.10.0-10.el7   @base
openmpi-devel.x86_64   1.10.0-10.el7   @base

(1) When I run
$ mpirun -H myhosts -np myprocs executable
the job runs fine and outputs correctly to stdout

(2) When I run
$ mpirun -H myhosts -np myprocs executable > stdout.log
The stdout.log file prematurely ends (without full output)
... but the mpi executable itself seems to keep running forever until manually terminated 
will a "kill".

(3) When I run
$ mpirun -H myhosts -np myprocs executable | cat > stdout.log
the job runs fine and outputs correctly to the stdout.log file

I tried playing with a 'stdbuf' prefix to the command, but this didn't seem to 
help
I would like (2) to work, but have resorted to (3).

I tried digging around in the parameters after seeing 
https://github.com/open-mpi/ompi/issues/341
and thinking it might be something similar, but didn't see any poll or epoll in 
.conf
I am hesitant to try to compile from scratch and get away from the repo release 
cycle.

Is this a known bug?
If so, and if it has been fixed, would you recommend I install the latest 
stable rpm of 1.10.4-1 from https://www.open-mpi.org/software/ompi/v1.10/ ?

Thanks,
Emre






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




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

Re: [OMPI users] Using Open MPI with multiple versions of GCC and G++

[Dave Love]

"Jeff Squyres (jsquyres)"  writes:

> Especially with C++, the Open MPI team strongly recommends you
> building Open MPI with the target versions of the compilers that you
> want to use.  Unexpected things can happen when you start mixing
> versions of compilers (particularly across major versions of a
> compiler).  To be clear: compilers are *supposed* to be compatible
> across multiple versions (i.e., compile a library with one version of
> the compiler, and then use that library with an application compiled
> by a different version of the compiler), but a) there's other issues,
> such as C++ ABI issues and other run-time bootstrapping that can
> complicate things, and b) bugs in forward and backward compatibility
> happen.

Is that actually observed in GNU/Linux systems?  I'd expect it either to
work or just fail to link.  For instance, the RHEL 6 devtoolset-4 (gcc
5) uses the system libstdc++, and the system compiler is gcc 4.4.

> The short answer is in this FAQ item:
> https://www.open-mpi.org/faq/?category=mpi-apps#override-wrappers-after-v1.0.
> Substituting the gcc 5 compiler may work just fine.

For what it's worth, not for GNU Fortran, which unfortunately changes
the module format incompatibly with each release, or at least most
releases.
___
users mailing list
users@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/users

Re: [OMPI users] Launching hybrid MPI/OpenMP jobs on a cluster: correct OpenMPI flags?

[Dave Love]

Wirawan Purwanto  writes:

> Instead of the scenario above, I was trying to get the MPI processes
> side-by-side (more like "fill_up" policy in SGE scheduler), i.e. fill
> node 0 first, then fill node 1, and so on. How do I do this properly?
>
> I tried a few attempts that fail:
>
> $ export OMP_NUM_THREADS=2
> $ mpirun -np 16 -map-by core:PE=2 ./EXECUTABLE

...

> Clearly I am not understanding how this map-by works. Could somebody
> help me? There was a wiki article partially written:
>
> https://github.com/open-mpi/ompi/wiki/ProcessPlacement
>
> but unfortunately it is also not clear to me.

Me neither; this stuff has traditionally been quite unclear and really
needs documenting/explaining properly.

This sort of thing from my local instructions for OMPI 1.8 probably does
what you want for OMP_NUM_THREADS=2 (where the qrsh options just get me
a couple of small nodes):

  $ qrsh -pe mpi 24 -l num_proc=12 \
 mpirun -n 12 --map-by slot:PE=2 --bind-to core --report-bindings true |&
 sort -k 4 -n
  [comp544:03093] MCW rank 0 bound to socket 0[core 0[hwt 0]], socket 0[core 
1[hwt 0]]: [B/B/./././.][./././././.]
  [comp544:03093] MCW rank 1 bound to socket 0[core 2[hwt 0]], socket 0[core 
3[hwt 0]]: [././B/B/./.][./././././.]
  [comp544:03093] MCW rank 2 bound to socket 0[core 4[hwt 0]], socket 0[core 
5[hwt 0]]: [././././B/B][./././././.]
  [comp544:03093] MCW rank 3 bound to socket 1[core 6[hwt 0]], socket 1[core 
7[hwt 0]]: [./././././.][B/B/./././.]
  [comp544:03093] MCW rank 4 bound to socket 1[core 8[hwt 0]], socket 1[core 
9[hwt 0]]: [./././././.][././B/B/./.]
  [comp544:03093] MCW rank 5 bound to socket 1[core 10[hwt 0]], socket 1[core 
11[hwt 0]]: [./././././.][././././B/B]
  [comp527:03056] MCW rank 6 bound to socket 0[core 0[hwt 0]], socket 0[core 
1[hwt 0]]: [B/B/./././.][./././././.]
  [comp527:03056] MCW rank 7 bound to socket 0[core 2[hwt 0]], socket 0[core 
3[hwt 0]]: [././B/B/./.][./././././.]
  [comp527:03056] MCW rank 8 bound to socket 0[core 4[hwt 0]], socket 0[core 
5[hwt 0]]: [././././B/B][./././././.]
  [comp527:03056] MCW rank 9 bound to socket 1[core 6[hwt 0]], socket 1[core 
7[hwt 0]]: [./././././.][B/B/./././.]
  [comp527:03056] MCW rank 10 bound to socket 1[core 8[hwt 0]], socket 1[core 
9[hwt 0]]: [./././././.][././B/B/./.]
  [comp527:03056] MCW rank 11 bound to socket 1[core 10[hwt 0]], socket 1[core 
11[hwt 0]]: [./././././.][././././B/B]

I don't remember how I found that out.
___
users mailing list
users@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/users

Re: [OMPI users] what was the rationale behind rank mapping by socket?

[Dave Love]

Gilles Gouaillardet  writes:

> Bennet,
>
>
> my guess is mapping/binding to sockets was deemed the best compromise
> from an
>
> "out of the box" performance point of view.
>
>
> iirc, we did fix some bugs that occured when running under asymmetric
> cpusets/cgroups.
>
> if you still have some issues with the latest Open MPI version (2.0.1)
> and the default policy,
>
> could you please describe them ?

I also don't understand why binding to sockets is the right thing to do.
Binding to cores seems the right default to me, and I set that locally,
with instructions about running OpenMP.  (Isn't that what other
implementations do, which makes them look better?)

I think at least numa should be used, rather than socket.  Knights
Landing, for instance, is single-socket, so no gets no actual binding by
default.
___
users mailing list
users@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/users

Re: [OMPI users] MPI Behaviour Question

[Reuti]

Hi,

> Am 11.10.2016 um 14:56 schrieb Mark Potter :
> 
> This question is related to OpenMPI 2.0.1 compiled with GCC 4.8.2 on
> RHEL 6.8 using Torque 6.0.2 with Moab 9.0.2. To be clear, I am an
> administrator and not a coder and I suspect this is expected behavior
> but I have been asked by a client to explain why this is happening.
> 
> Using Torque, the following command returns the hostname of the first
> node only, regardless of how the nodes/cores are split up:
> 
> mpirun -np 20 echo "Hello from $HOSTNAME"

The $HOSTNAME will be expanded and used as argument before `mpirun` even 
starts. Instead it has to be evaluated on the nodes:

$ mpirun bash -c "echo \$HOSTNAME"


> (the behaviour is the same with "echo $(hostname))
> 
> The Torque script looks like this:
> 
> #PBS -V
> #PBS -N test-job
> #PBS -l nodes=2:ppn=16
> #PBS -e ERROR
> #PBS -o OUTPUT
> 
> 
> cd $PBS_O_WORKDIR
> date
> cat $PBS_NODEFILE
> 
> mpirun -np32 echo "Hello from $HOSTNAME"
> 
> If the echo statement is replaced with "hostname" then a proper
> response is received from all nodes.
> 
> While I know there are better ways to test OpenMPI's functionality,
> like compiling and using the programs in examples/, this is the method
> a specific client chose.

There are small "Hello world" programs like here:

http://mpitutorial.com/tutorials/mpi-hello-world/

to test whether e.g. the libraries are found at runtime by the application(s).

-- Reuti


> I was using both the examples and a Torque job
> script calling just "hostname" as a command and not using echo and the
> client was using the script above. It took some doing to figure out why
> he thought it wasn't working and all my tests were successful and when
> I figured it, he wanted an explanation that's beyond my current
> knowledge. Any help towards explaining the behaviour would be greatly
> appreciated.
> 
> -- 
> Regards,
> 
> Mark L. Potter
> Senior Consultant
> PCPC Direct, Ltd.
> O: 713-344-0952 
> M: 713-965-4133
> S: mpot...@pcpcdirect.com
> ___
> users mailing list
> users@lists.open-mpi.org
> https://rfd.newmexicoconsortium.org/mailman/listinfo/users
> 

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

Re: [OMPI users] MPI Behaviour Question

[Gilles Gouaillardet]

Mark,

My understanding is that shell meta expansion occurs once on the first node, so 
from an Open MPI point of view, you really invoke
mpirun echo node0
I suspect
mpirun echo 'Hello from $(hostname)'
Is what you want to do
I do not know about
mpirun echo 'Hello from $HOSTNAME'
$HOSTNAME might be passed by the first node to all tasks, and hence might not 
have the value you expect on all the nodes
Feel free to
mpirun env | grep ^HOSTNAME=
To check if the HOSTNAME variable is set to what you expect

/* i an afk, so i cannot check that right now ... */


Cheers,

Gilles

Mark Potter  wrote:
>This question is related to OpenMPI 2.0.1 compiled with GCC 4.8.2 on
>RHEL 6.8 using Torque 6.0.2 with Moab 9.0.2. To be clear, I am an
>administrator and not a coder and I suspect this is expected behavior
>but I have been asked by a client to explain why this is happening.
>
>Using Torque, the following command returns the hostname of the first
>node only, regardless of how the nodes/cores are split up:
>
>mpirun -np 20 echo "Hello from $HOSTNAME"
>
>(the behaviour is the same with "echo $(hostname))
>
>The Torque script looks like this:
>
>#PBS -V
>#PBS -N test-job
>#PBS -l nodes=2:ppn=16
>#PBS -e ERROR
>#PBS -o OUTPUT
>
>
>cd $PBS_O_WORKDIR
>date
>cat $PBS_NODEFILE
>
>mpirun -np32 echo "Hello from $HOSTNAME"
>
>If the echo statement is replaced with "hostname" then a proper
>response is received from all nodes.
>
>While I know there are better ways to test OpenMPI's functionality,
>like compiling and using the programs in examples/, this is the method
>a specific client chose. I was using both the examples and a Torque job
>script calling just "hostname" as a command and not using echo and the
>client was using the script above. It took some doing to figure out why
>he thought it wasn't working and all my tests were successful and when
>I figured it, he wanted an explanation that's beyond my current
>knowledge. Any help towards explaining the behaviour would be greatly
>appreciated.
>
>-- 
>Regards,
>
>Mark L. Potter
>Senior Consultant
>PCPC Direct, Ltd.
>O: 713-344-0952 
>M: 713-965-4133
>S: mpot...@pcpcdirect.com
>___
>users mailing list
>users@lists.open-mpi.org
>https://rfd.newmexicoconsortium.org/mailman/listinfo/users
___
users mailing list
users@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/users

[OMPI users] MPI Behaviour Question

[Mark Potter]

This question is related to OpenMPI 2.0.1 compiled with GCC 4.8.2 on
RHEL 6.8 using Torque 6.0.2 with Moab 9.0.2. To be clear, I am an
administrator and not a coder and I suspect this is expected behavior
but I have been asked by a client to explain why this is happening.

Using Torque, the following command returns the hostname of the first
node only, regardless of how the nodes/cores are split up:

mpirun -np 20 echo "Hello from $HOSTNAME"

(the behaviour is the same with "echo $(hostname))

The Torque script looks like this:

#PBS -V
#PBS -N test-job
#PBS -l nodes=2:ppn=16
#PBS -e ERROR
#PBS -o OUTPUT


cd $PBS_O_WORKDIR
date
cat $PBS_NODEFILE

mpirun -np32 echo "Hello from $HOSTNAME"

If the echo statement is replaced with "hostname" then a proper
response is received from all nodes.

While I know there are better ways to test OpenMPI's functionality,
like compiling and using the programs in examples/, this is the method
a specific client chose. I was using both the examples and a Torque job
script calling just "hostname" as a command and not using echo and the
client was using the script above. It took some doing to figure out why
he thought it wasn't working and all my tests were successful and when
I figured it, he wanted an explanation that's beyond my current
knowledge. Any help towards explaining the behaviour would be greatly
appreciated.

-- 
Regards,

Mark L. Potter
Senior Consultant
PCPC Direct, Ltd.
O: 713-344-0952 
M: 713-965-4133
S: mpot...@pcpcdirect.com
___
users mailing list
users@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/users