You got that error because the orted is looking for its rank on the cmd line and not finding it.
> On May 14, 2018, at 12:37 PM, Max Mellette <wmell...@ucsd.edu> wrote: > > Hi Gus, > > Thanks for the suggestions. The correct version of openmpi seems to be > getting picked up; I also prepended .bashrc with the installation path like > you suggested, but it didn't seemed to help: > > user@b09-30:~$ cat .bashrc > export > PATH=/home/user/openmpi_install/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin > export LD_LIBRARY_PATH=/home/user/openmpi_install/lib > user@b09-30:~$ which mpicc > /home/user/openmpi_install/bin/mpicc > user@b09-30:~$ /usr/bin/ssh -x b09-32 orted > [b09-32:204536] [[INVALID],INVALID] ORTE_ERROR_LOG: Not found in file > ess_env_module.c at line 147 > [b09-32:204536] [[INVALID],INVALID] ORTE_ERROR_LOG: Bad parameter in file > util/session_dir.c at line 106 > [b09-32:204536] [[INVALID],INVALID] ORTE_ERROR_LOG: Bad parameter in file > util/session_dir.c at line 345 > [b09-32:204536] [[INVALID],INVALID] ORTE_ERROR_LOG: Bad parameter in file > base/ess_base_std_orted.c at line 270 > -------------------------------------------------------------------------- > It looks like orte_init failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during orte_init; some of which are due to configuration or > environment problems. This failure appears to be an internal failure; > here's some additional information (which may only be relevant to an > Open MPI developer): > > orte_session_dir failed > --> Returned value Bad parameter (-5) instead of ORTE_SUCCESS > -------------------------------------------------------------------------- > > Thanks, > Max > > > On Mon, May 14, 2018 at 11:41 AM, Gus Correa <g...@ldeo.columbia.edu > <mailto:g...@ldeo.columbia.edu>> wrote: > Hi Max > > Just in case, as environment mix often happens. > Could it be that you are inadvertently picking another > installation of OpenMPI, perhaps installed from packages > in /usr , or /usr/local? > That's easy to check with 'which mpiexec' or > 'which mpicc', for instance. > > Have you tried to prepend (as opposed to append) OpenMPI > to your PATH? Say: > > export > PATH='/home/user/openmpi_install/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin' > > I hope this helps, > Gus Correa > > _______________________________________________ > users mailing list > users@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/users
_______________________________________________ users mailing list users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/users
