Re: [OMPI users] "failed to create queue pair" problem, but settings appear OK

2016-06-16 Thread Nathan Hjelm
s, tho I don’t question > that we were running out of QPs. > > --john > > > From: users [mailto:users-boun...@open-mpi.org] On Behalf Of Nathan Hjelm > Sent: Wednesday, June 15, 2016 2:43 PM > To: Open MPI Users > Subject: EXT: Re: [OMPI users] "failed to create queue

Re: [OMPI users] "failed to create queue pair" problem, but settings appear OK

2016-06-15 Thread Gus Correa
12288 Other suggestions welcome. Hitting a brick wall here. Thanks! --john -Original Message- From: users [mailto:users-boun...@open-mpi.org] On Behalf Of Gus Correa Sent: Wednesday, June 15, 2016 1:39 PM To: Open MPI Users Subject: EXT: Re: [OMPI users] "failed to create queue pa

Re: [OMPI users] "failed to create queue pair" problem, but settings appear OK

2016-06-15 Thread Nathan Hjelm
[mailto:users-boun...@open-mpi.org] On Behalf Of Gus Correa Sent: Wednesday, June 15, 2016 1:39 PM To: Open MPI Users Subject: EXT: Re: [OMPI users] "failed to create queue pair" problem, but settings appear OK Hi John 1) For diagnostic, you could check the actual "per process&qu

Re: [OMPI users] "failed to create queue pair" problem, but settings appear OK

2016-06-15 Thread Nathan Hjelm
...@open-mpi.org] On Behalf Of Gus Correa Sent: Wednesday, June 15, 2016 1:39 PM To: Open MPI Users Subject: EXT: Re: [OMPI users] "failed to create queue pair" problem, but settings appear OK Hi John 1) For diagnostic, you could check the actual "per process" limits on the

Re: [OMPI users] "failed to create queue pair" problem, but settings appear OK

2016-06-15 Thread Sasso, John (GE Power, Non-GE)
On Behalf Of Gus Correa Sent: Wednesday, June 15, 2016 1:39 PM To: Open MPI Users Subject: EXT: Re: [OMPI users] "failed to create queue pair" problem, but settings appear OK Hi John 1) For diagnostic, you could check the actual "per process" limits on the nodes while that

Re: [OMPI users] "failed to create queue pair" problem, but settings appear OK

2016-06-15 Thread Gus Correa
Hi John 1) For diagnostic, you could check the actual "per process" limits on the nodes while that big job is running: cat /proc/$PID/limits 2) If you're using a resource manager to launch the job, the resource manager daemon/deamons (local to the nodes) may have to to set the memlock and oth