[boonhow]

Hi everyone,


I am new to OpenFOAM and am going through the tutorial to learn about CFD



Would anyone be able to advise why I am unable to launch parafoam and open up the parafoam window? Currently I am using Virtual Box to run Ubuntu 16.04. I have checked that I have the latest parafoam, gcc and g++.



I followed the tutorial from the website https://cfd.direct/openfoam/user-guide/v6-cavity/

and encountered the following problem when i run parafoam &


bash-4.2$ paraFoam &
[1] 1135
bash-4.2$ Created temporary 'cavity.OpenFOAM'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-boon'
--------------------------------------------------------------------------
It looks like opal_init failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during opal_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):

opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS
--------------------------------------------------------------------------
--------------------------------------------------------------------------
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):

opal_init failed
--> Returned value Error (-1) instead of ORTE_SUCCESbash-4.2$ paraFoam &
[1] 1135
bash-4.2$ Created temporary 'cavity.OpenFOAM'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-boon'
--------------------------------------------------------------------------
It looks like opal_init failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during opal_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):

opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS
--------------------------------------------------------------------------
--------------------------------------------------------------------------
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):

opal_init failed
--> Returned value Error (-1) instead of ORTE_SUCCESS
--------------------------------------------------------------------------
--------------------------------------------------------------------------
It looks like MPI_INIT failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during MPI_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):

ompi_mpi_init: ompi_rte_init failed
--> Returned "Error" (-1) instead of "Success" (0)
--------------------------------------------------------------------------
*** 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)
[8437a05a32ed:1137] Local abort before MPI_INIT completed successfully; not able to aggregate error messages, and not able to guarantee that all other processes were killed!

[1]+ Done paraFoam
S


Below are further information which i think may be useful to identify the problem,


bash-4.2$ which mpirun
/opt/OpenFOAM/ThirdParty-v1806/platforms/linux64Gcc/openmpi-1.10.4/bin/mpirun



bash-4.2$ mpirun --help
--------------------------------------------------------------------------
It looks like opal_init failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during opal_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):

opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS







Many thanks in advance for the help!

[lin]

I encounter the same problem . I think there is something wrong with this docker image.

[pgh]

Hi,
See this
https://develop.openfoam.com/Develop.../971#note_7569

[safranyikf]

I have exactly the same issue, but I do not understand what should I do. Can anybody give me more detailed suggestion?


Thanks in advance, Feri

[x86_64leon]

Originally Posted by safranyikf

I have exactly the same issue, but I do not understand what should I do. Can anybody give me more detailed suggestion?


Thanks in advance, Feri

I also encountered the same issue ... using Paraview 5.10.1. How can we know where Paraview is getting his openmpi from ? Could this be due to conflicting versions of openmpi ?

Thanks in advance !!

[x86_64leon]

Originally Posted by x86_64leon

I also encountered the same issue ... using Paraview 5.10.1. How can we know where Paraview is getting his openmpi from ? Could this be due to conflicting versions of openmpi ?

Thanks in advance !!

Finally found the solution !!

I would like to share it here.

It consists in adding a LD_PRELOAD in front of the command paraview.

I did it through an alias :



alias paraview="LD_PRELOAD=$OPAL_LIBDIR/libmpi.so [path to paraview]/bin/paraview"


OPAL_LIBDIR is the openmpi installation directory containing openmpi shared libraries