[safranyikf]

Dear All,


I am very interesting in CFD simulations and I would like to use OpenFoam. I have tried to install OpenFoam 4.1 on Ubuntu 20.04 LTS. These steps were followed and these instructions were considered as well, however I faced a problem but I do not understand what can be the mistake (I am not an experienced Ubuntu user).

I got follwong error messages in Terminal after an hour of compiling:

.1/applications/bin/linux64GccDPInt32Opt/yPlusRAS
/usr/bin/ld: cannot find -lfoam
collect2: error: ld returned 1 exit status
make[3]: *** [/home/feri/foam/foam-extend-4.1/wmake/Makefile:160:  /home/feri/foam/foam-extend-4.1/applications/bin/linux64GccDPInt32Opt/yPlusRAS]  Error 1
make[2]: *** [/home/feri/foam/foam-extend-4.1/wmake/MakefileApps:39: yPlusRAS] Error 2
make[2]: Target 'application' not remade because of errors.
make[1]: *** [/home/feri/foam/foam-extend-4.1/wmake/MakefileApps:39: wall] Error 2
make[1]: Target 'application' not remade because of errors.
make: *** [/home/feri/foam/foam-extend-4.1/wmake/MakefileApps:39: postProcessing] Error 2
make: Target 'application' not remade because of errors.

What should I do to solve the problem?


update: The problem was solved with a fresh reinstall. blockMesh and simpleFoam are working but paraFoam throws the following error:

feri@ubuntu:~/foam/feri-4.1/run/pitzDaily$ paraFoam -vtk
Created temporary 'pitzDaily.foam'
--------------------------------------------------------------------------
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)
[ubuntu:535647] 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!

What should I do?
Thanks in advance, Feri

[safranyikf]

Hi,


following a fresh reinstall the blockMesh and simpleFoam is working, however paraFoam throws the following error:

 paraFoam -vtk
Created temporary 'pitzDaily.foam'
--------------------------------------------------------------------------
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)
[ubuntu:535647] 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!

How can I solve this issue?