Re: [OMPI users] MPI_Comm_accept() / MPI_Comm_connect() fail between two different machines

I will happily test any patch you send me to fix this problem. Thanks, Martin -Original Message- From: users [mailto:users-boun...@open-mpi.org] On Behalf Of Ralph Castain Sent: July 13, 2015 22:55 To: Open MPI Users Subject: Re: [OMPI users] MPI_Comm_accept() / MPI_Comm_connect() fail b

Re: [OMPI users] MPI_Comm_accept() / MPI_Comm_connect() fail between two different machines

This seems to fix the problem when using your example on my cluster - please let me know if it solves things for you oob.diff Description: Binary data > On Jul 14, 2015, at 6:08 AM, Audet, Martin > wrote: > > I will happily test any patch you send me to fix this problem. > > Thanks, > >

Re: [OMPI users] MPI_Comm_accept() / MPI_Comm_connect() fail between two different machines

Yes, this patch applied over OpenMPI 1.8.6 solves my problem. Attached are the new output files for the server and the client when started with "--mca oob_base_verbose 100". Will this patch be included in 1.8.7 ? Thanks again, Martin Audet From: users [

Re: [OMPI users] MPI_Comm_accept() / MPI_Comm_connect() fail between two different machines

Kewl - thanks for the assist! Yes, I’ll add it now - waiting for one other problem to be resolved (patch is in the oven), then expect to release tomorrow barring any other problems. > On Jul 14, 2015, at 9:18 AM, Audet, Martin > wrote: > > Yes, this patch applied over OpenMPI 1.8.6 solves my

Re: [OMPI users] OpenMPI 1.8.6, CentOS 6.3, too many slots = crash

Ralph, Do you think the 1.8.7 release will solve the problems w/our heterogeneous cluster? Bill L. From: users [users-boun...@open-mpi.org] on behalf of Ralph Castain [r...@open-mpi.org] Sent: Tuesday, July 07, 2015 8:59 PM To: Open MPI Users Subject: Re: [OMPI

Re: [OMPI users] OpenMPI 1.8.6, CentOS 6.3, too many slots = crash

Can you give it a try? I’m skeptical, but it might work. The rc is out on the web site: http://www.open-mpi.org/software/ompi/v1.8/ > On Jul 14, 2015, at 11:17 AM, Lane, William wrote: > > Ralph, > > Do you think the 1.8.7 release will solve the