Re: [OMPI users] mpi_init waits 64 seconds if vpn is connected

2013-03-26 Thread Jeff Squyres (jsquyres)
On Mar 21, 2013, at 9:52 PM, David A. Boger wrote: > If I add "-mca oob_tcp_if_exclude cscotun0", then the corresponding address > for that vpn interface no longer shows up in contact.txt, but the problem > remains. I also add "-mca btl ^cscotun0 -mca btl_tcp_if_exclude cscotun0" > with no eff

Re: [OMPI users] mpi_init waits 64 seconds if vpn is connected

2013-03-22 Thread Ralph Castain
Ah, yes - that pinpoints the problem. It looks like your vpn is indeed interfering with connections. I suspect it must be some kind of vpn/Ubuntu configuration issue as I have the same experience on my Mac laptop that you report (i.e., no issue). I'd suggest googling the Ubuntu site (or just in

Re: [OMPI users] mpi_init waits 64 seconds if vpn is connected

2013-03-22 Thread David A. Boger
Following up on your TCP remark, I found that during the delay, netstat -tnp shows tcp0 1 192.168.1.3:56343 192.168.1.3:47830 SYN_SENT 24191/mpi_hello and that while the vpn is connected, I am unable to ping 192.168.1.3 (the machine I am on). On the other hand, on the

Re: [OMPI users] mpi_init waits 64 seconds if vpn is connected

2013-03-22 Thread David A. Boger
Thanks Ralph. I have a Mac OS X 10.6.8 laptop where I can run open-mpi 1.2.8 and open-mpi 1.6.4 with the vpn connected without any problem, even without having to exclude the vpn interface, so you're probably right -- the existence of the vpn interface alone doesn't explain the problem. Neverthele

Re: [OMPI users] mpi_init waits 64 seconds if vpn is connected

2013-03-22 Thread Ralph Castain
The process is hanging trying to open a TCP connection back to mpirun. I would have thought that excluding the vpn interface would help, but it could be that there is still some interference from the vpn software itself - as you probably know, vpn generally tries to restrict connections. I don'