Jan, It looks like mpiexec is not respecting all the aliases for that environment variable. Can you use MPIR_CVAR_CH3_PORT_RANGE to set the port range for now? We’ll add MPICH_PORT_RANGE as an alias for it in the next release. FWIW, use the README.envvar for the environment variable names. They should contain the correct information. Aliases are only maintained for backward compatibility. — Pavan On Apr 23, 2014, at 10:06 PM, Jan Balewski <[email protected]> wrote:

On Apr 23, 2014, at 5:32 PM, Kenneth Raffenetti <[email protected]> wrote:

...

You can control the port range that mpich will use. See this item in the FAQ

http://wiki.mpich.org/mpich/index.php/Frequently_Asked_Questions#Q:_How_do_I...

Hi, Thanks, but somehow setting of MPICH_PORT_RANGE variable on the master VM does not propagate. mpiexec still tries to open the port 34781 which is out of the range set by export MPICH_PORT_RANGE=10000:10100

I'm missing sth - not sure what? Jan

-------- [cosy11@oswrk210 mpich-3.1]$ echo $MPICH_PORT_RANGE 10000:10100

[cosy11@oswrk210 mpich-3.1]$ mpiexec -f machinefile2 -n 4 ./examples/cpi [proxy:0:[email protected]] HYDU_sock_connect (utils/sock/sock.c:172): unable to connect from "oswrk207.lns.mit.edu" to "198.125.163.210" (Connection timed out) [proxy:0:[email protected]] main (pm/pmiserv/pmip.c:189): unable to connect to server 198.125.163.210 at port 34781 (check for firewalls!)

_______________________________________________ discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss