[mpich-discuss] Usage of MPICH_PORT_RANGE has no impact

[Kenneth Raffenetti]

On 09/18/2015 06:19 AM, Mark Bonnekessel wrote:
>     root at pi1:/mnt/docker# mpiexec -f machines  -env MPIEXC_PORT_RANGE
>     10000:10100 -n 2 ./mpi-hello
>     [proxy:0:1 at pi2] HYDU_sock_connect (utils/sock/sock.c:172): unable to
>     connect from "pi2" to "pi1" (Connection refused)
>     [proxy:0:1 at 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 at mpich.org
To manage subscription options or unsubscribe:
https://lists.mpich.org/mailman/listinfo/discuss