September 2015 - discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] Usage of MPICH_PORT_RANGE has no impact
by Kenneth Raffenetti 18 Sep '15

18 Sep '15

On 09/18/2015 06:19 AM, Mark Bonnekessel wrote: > root@pi1:/mnt/docker# mpiexec -f machines -env MPIEXC_PORT_RANGE > 10000:10100 -n 2 ./mpi-hello > [proxy:0:1@pi2] HYDU_sock_connect (utils/sock/sock.c:172): unable to > connect from "pi2" to "pi1" (Connection refused) > [proxy:0:1@pi2] main (pm/pmiserv/pmip.c:189): unable to connect to > server pi1 at port 35994 (check for firewalls!) 1. The envvar is misspelled in this output, so mpiexec will not have recognized it. 2. The wiki link you posted (MPIR_CVAR_CH3_PORT_RANGE) is the correct method of forcing MPI to use a specific port range. The combination of the 2 environment variables (MPIEXEC_PORT_RANGE, MPIR_CVAR_CH3_PORT_RANGE) will ensure communication for mpiexec and mpi both go over the specified port range. Ken _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] MPICH with heterogeneous architectures
by Andrew Green 18 Sep '15

18 Sep '15

Hi Dmitry, Thank you, that works perfectly! Thanks, Andrew > On 18 Sep 2015, at 11:53, Durnov, Dmitry <dmitry.durnov(a)intel.com> wrote: > > Hi Andrew, > > As a quick solution I would recommend you to try to wrap the proxy (into a shell script) and add architecture recognition/specific logic via something like "uname -m" + check for "k1om" (and execute corresponding binary). > So hydra would run the script and the script would select an appropriate proxy binary. > > There are several ways but this one should be quick and work fine. > > BR, > Dmitry > > -----Original Message----- > From: Andrew Green [mailto:[email protected]] > Sent: Friday, September 18, 2015 12:03 PM > To: discuss(a)mpich.org > Subject: [mpich-discuss] MPICH with heterogeneous architectures > > Hello, > > I've been trying to use MPICH2 with an application on the Intel Xeon Phi. I have two builds of MPICH2: one host-compatible and one MIC-compatible. So far I have only been able to run either only on the host or only on the MIC; I would ideally like to be able to run on both simultaneously. > > I can see what is going wrong: hydra tries to launch a proxy on the MIC which has been compiled for the host and therefore can't be executed. Is there any way to change this default behaviour? I tried changing the launch executable, but it didn't have the effect I wanted. > > Thanks for your help, > Andrew > > -------------------------------------------------------------------- > Joint Stock Company Intel A/O > Registered legal address: Krylatsky Hills Business Park, > 17 Krylatskaya Str., Bldg 4, Moscow 121614, > Russian Federation > > This e-mail and any attachments may contain confidential material for > the sole use of the intended recipient(s). Any review or distribution > by others is strictly prohibited. If you are not the intended > recipient, please contact the sender and delete all copies. > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] Usage of MPICH_PORT_RANGE has no impact
by Mark Bonnekessel 18 Sep '15

18 Sep '15

Ok, the solution is listed here: https://wiki.mpich.org/mpich/index.php/Frequently_Asked_Questions#Q:_How_do… <https://wiki.mpich.org/mpich/index.php/Frequently_Asked_Questions#Q:_How_do…> I thought i could configure that ports with -env. > Am 18.09.2015 um 11:03 schrieb Mark Bonnekessel <bonnekessel(a)mailbox.org>: > > Hi, > > we want to setup a mpi-cluster with raspberry pis. > The mpi-process run in a docker-container. That’s why we need to configure the ports, that mpi uses. > > We found the env flag MPI_PORT_RANGE / MPIEXEC_PORT_RANGE to configure the port range, that is used by mpi. > Our problem is, that this flag has no impact to the running mpi-process: > > root@pi1:/mnt/docker# mpiexec -f machines -env MPIEXC_PORT_RANGE 10000:10100 -n 2 ./mpi-hello > [proxy:0:1@pi2] HYDU_sock_connect (utils/sock/sock.c:172): unable to connect from "pi2" to "pi1" (Connection refused) > [proxy:0:1@pi2] main (pm/pmiserv/pmip.c:189): unable to connect to server pi1 at port 35994 (check for firewalls!) > > We tried every other combination of mpirun/mipexec and MPICH_PORT_RANGE/ MPIEXEC_PORT_RANGE. > > Is there any other configuration needed or something, that we are missing to specify the used ports for mpi? > > Regards, > Mark > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Argonne Spam Quarantine Notification
by Argonne Anti Spam Quarantine 18 Sep '15

18 Sep '15

++ Note: This message has been sent by a notification only system. Please do not reply ++ IronPort Spam Quarantine Notification If a spam message was missed, or if a message was incorrectly flagged as spam, you can add the sender to a personal safelist or blocklist via the quarantine. Senders on the safelist will not be flagged as spam, and senders on the blocklist will be automatically quarantined. For more information, visit: https://wiki.inside.anl.gov/inside/Ironport_Anti-Spam_Appliances/Documentat… The message(s) below have been quarantined by the Argonne National Laboratory spam filtering system. There are 1 new messages in your Email Quarantine since you received your last Spam Quarantine Notification. If the messages below are spam, you do not need to take any action. Messages will be automatically deleted from the quarantine after 28 day(s). If any of the messages below are not spam, click the 'Release' link to have them sent to your Inbox. Messages that have been correctly flagged as spam do not need to be reported. ----------- New Quarantine Messages --------------- Message 1 From: "leader" <gjfvd(a)a2al4q57pqet.mvvisionlimited.com> Subject: *****SPAM*****MPICH | High-Performance Portable MPI discuss(a)mpich.org Date: 17 Sep 2015 Release: http://mailgateway.anl.gov:8080/Message?action=Release&mid=94153664&h=7c2a5… --------------------------------------------------- To manage your quarantine please visit the URL below: http://mailgateway.anl.gov:8080/Search?h=30dbb0a1c0b4b0fc77bfe24644601714&e… If you have any questions regarding the Laboratory spam filtering product, please contact the CIS helpdesk at help(a)anl.gov or x-9999 option 2.

1 0

Re: [mpich-discuss] MPICH with heterogeneous architectures
by Durnov, Dmitry 18 Sep '15

18 Sep '15

Hi Andrew, As a quick solution I would recommend you to try to wrap the proxy (into a shell script) and add architecture recognition/specific logic via something like "uname -m" + check for "k1om" (and execute corresponding binary). So hydra would run the script and the script would select an appropriate proxy binary. There are several ways but this one should be quick and work fine. BR, Dmitry -----Original Message----- From: Andrew Green [mailto:[email protected]] Sent: Friday, September 18, 2015 12:03 PM To: discuss(a)mpich.org Subject: [mpich-discuss] MPICH with heterogeneous architectures Hello, I've been trying to use MPICH2 with an application on the Intel Xeon Phi. I have two builds of MPICH2: one host-compatible and one MIC-compatible. So far I have only been able to run either only on the host or only on the MIC; I would ideally like to be able to run on both simultaneously. I can see what is going wrong: hydra tries to launch a proxy on the MIC which has been compiled for the host and therefore can't be executed. Is there any way to change this default behaviour? I tried changing the launch executable, but it didn't have the effect I wanted. Thanks for your help, Andrew -------------------------------------------------------------------- Joint Stock Company Intel A/O Registered legal address: Krylatsky Hills Business Park, 17 Krylatskaya Str., Bldg 4, Moscow 121614, Russian Federation This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Usage of MPICH_PORT_RANGE has no impact
by Mark Bonnekessel 18 Sep '15

18 Sep '15

Hi, we want to setup a mpi-cluster with raspberry pis. The mpi-process run in a docker-container. That’s why we need to configure the ports, that mpi uses. We found the env flag MPI_PORT_RANGE / MPIEXEC_PORT_RANGE to configure the port range, that is used by mpi. Our problem is, that this flag has no impact to the running mpi-process: root@pi1:/mnt/docker# mpiexec -f machines -env MPIEXC_PORT_RANGE 10000:10100 -n 2 ./mpi-hello [proxy:0:1@pi2] HYDU_sock_connect (utils/sock/sock.c:172): unable to connect from "pi2" to "pi1" (Connection refused) [proxy:0:1@pi2] main (pm/pmiserv/pmip.c:189): unable to connect to server pi1 at port 35994 (check for firewalls!) We tried every other combination of mpirun/mipexec and MPICH_PORT_RANGE/ MPIEXEC_PORT_RANGE. Is there any other configuration needed or something, that we are missing to specify the used ports for mpi? Regards, Mark _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

MPICH with heterogeneous architectures
by Andrew Green 18 Sep '15

18 Sep '15

Hello, I've been trying to use MPICH2 with an application on the Intel Xeon Phi. I have two builds of MPICH2: one host-compatible and one MIC-compatible. So far I have only been able to run either only on the host or only on the MIC; I would ideally like to be able to run on both simultaneously. I can see what is going wrong: hydra tries to launch a proxy on the MIC which has been compiled for the host and therefore can't be executed. Is there any way to change this default behaviour? I tried changing the launch executable, but it didn't have the effect I wanted. Thanks for your help, Andrew _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Argonne Spam Quarantine Notification
by Argonne Anti Spam Quarantine 16 Sep '15

16 Sep '15

++ Note: This message has been sent by a notification only system. Please do not reply ++ IronPort Spam Quarantine Notification If a spam message was missed, or if a message was incorrectly flagged as spam, you can add the sender to a personal safelist or blocklist via the quarantine. Senders on the safelist will not be flagged as spam, and senders on the blocklist will be automatically quarantined. For more information, visit: https://wiki.inside.anl.gov/inside/Ironport_Anti-Spam_Appliances/Documentat… The message(s) below have been quarantined by the Argonne National Laboratory spam filtering system. There are 1 new messages in your Email Quarantine since you received your last Spam Quarantine Notification. If the messages below are spam, you do not need to take any action. Messages will be automatically deleted from the quarantine after 28 day(s). If any of the messages below are not spam, click the 'Release' link to have them sent to your Inbox. Messages that have been correctly flagged as spam do not need to be reported. ----------- New Quarantine Messages --------------- Message 1 From: "Google Inc."<g.office(a)representative.com> Subject: REWARDS Date: 15 Sep 2015 Release: http://mailgateway.anl.gov:8080/Message?action=Release&mid=93758834&h=a7b6e… --------------------------------------------------- To manage your quarantine please visit the URL below: http://mailgateway.anl.gov:8080/Search?h=8be816e00e3ab6f636ca3e5a8ced6f90&e… If you have any questions regarding the Laboratory spam filtering product, please contact the CIS helpdesk at help(a)anl.gov or x-9999 option 2.

1 0

Argonne Spam Quarantine Notification
by Argonne Anti Spam Quarantine 16 Sep '15

16 Sep '15

++ Note: This message has been sent by a notification only system. Please do not reply ++ IronPort Spam Quarantine Notification If a spam message was missed, or if a message was incorrectly flagged as spam, you can add the sender to a personal safelist or blocklist via the quarantine. Senders on the safelist will not be flagged as spam, and senders on the blocklist will be automatically quarantined. For more information, visit: https://wiki.inside.anl.gov/inside/Ironport_Anti-Spam_Appliances/Documentat… The message(s) below have been quarantined by the Argonne National Laboratory spam filtering system. There are 1 new messages in your Email Quarantine since you received your last Spam Quarantine Notification. If the messages below are spam, you do not need to take any action. Messages will be automatically deleted from the quarantine after 28 day(s). If any of the messages below are not spam, click the 'Release' link to have them sent to your Inbox. Messages that have been correctly flagged as spam do not need to be reported. ----------- New Quarantine Messages --------------- Message 1 From: "nice" <nice19881(a)live.cn> Subject: *****SPAM*****Professional waste Copper scrap buyer Date: 15 Sep 2015 Release: http://mailgateway.anl.gov:8080/Message?action=Release&mid=93841713&h=ad31a… --------------------------------------------------- To manage your quarantine please visit the URL below: http://mailgateway.anl.gov:8080/Search?h=30dbb0a1c0b4b0fc77bfe24644601714&e… If you have any questions regarding the Laboratory spam filtering product, please contact the CIS helpdesk at help(a)anl.gov or x-9999 option 2.

1 0

ROMIO configure looks for lstat in the wrong header
by William Throwe 14 Sep '15

14 Sep '15

Hello, I hope this is the correct place to report a minor bug. If not, please point me in the right direction. The ROMIO configure script checks for a declaration of lstat in unistd.h, but, at least on the Linux machines I checked, lstat is in sys/stat.h. (The detection failure led to a linker error when building ROMIO as part of OpenMPI on one of my admittedly strangely configured machines, somehow.) It appears from the man page that either location is possible, so I suggest checking both. Suggested patch below. Thanks, William Throwe diff -Naur a/src/mpi/romio/configure.ac b/src/mpi/romio/configure.ac --- a/src/mpi/romio/configure.ac 2015-09-14 18:33:06.000000000 -0400 +++ b/src/mpi/romio/configure.ac 2015-09-14 18:36:06.000000000 -0400 @@ -1562,7 +1562,8 @@ AC_CHECK_FUNCS(lstat) if test "$ac_cv_func_lstat" = "yes" ; then # Do we need to declare lstat? - PAC_FUNC_NEEDS_DECL([#include <unistd.h>],lstat) + PAC_FUNC_NEEDS_DECL([#include <unistd.h> + #include <sys/stat.h>],lstat) fi AC_CHECK_FUNCS(readlink) if test "$ac_cv_func_readlink" = "yes" ; then _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0