title: OpenMPI PMIX error: BAD-PARAM in file pmix_esh.c occured in MPI_Init
body: <p>I am running a Fortran code using <code>gfortran</code> (version 6.3.0) compiler and <code>OpenMPI</code> (version 3.0.0), on a Ubuntu 17.04 system. </p>
  
  <p>Typing <code>make clean</code> and <code>make</code> seems working ok. But once I type <code>make run</code> in the terminal, I got the following message: </p>
  
  <pre><code>[woodpecker-Aspire-TC-705:17583] PMIX ERROR: BAD-PARAM in file dstore/pmix_esh.c at line 1005
  *** An error occurred in MPI_Init
  *** on a NULL communicator
  *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort,
  ***    and potentially your MPI job)
  [woodpecker-Aspire-TC-705:17583] Local abort before MPI_INIT completed 
  completed successfully, but am not able to aggregate error messages, and not 
  able to guarantee that all other processes were killed!
  
  -------------------------------------------------------
  Primary job  terminated normally, but 1 process returned
  a non-zero exit code.. Per user-direction, the job has been aborted.
  -------------------------------------------------------
  *** An error occurred in MPI_Init
  *** on a NULL communicator
  *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort,
  ***    and potentially your MPI job)
  [woodpecker-Aspire-TC-705:17586] Local abort before MPI_INIT completed 
  completed successfully, but am not able to aggregate error messages, and not 
  able to guarantee that all other processes were killed!
  --------------------------------------------------------------------------
  mpirun detected that one or more processes exited with non-zero status, thus 
  causing the job to be terminated. The first process to do so was:
  
   Process name: [[53958,1],0]
   Exit code:    1
  </code></pre>
  
  <p>I saw similar discussions on Github <a href="https://github.com/open-mpi/ompi/issues/2897" rel="nofollow noreferrer">https://github.com/open-mpi/ompi/issues/2897</a> without understanding how to resolve the issue.</p>
  
  <p>Any thoughts?</p>