[Tomjugj]

After typing "SU2_CFD thermalbath.cfg", the terminal returned:

--------------------------------------------------------------------------
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)
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!

My .bashrc file has following added:

export PATH=/home/jugj/doc/mpich-4.0.2/mpich-install/bin:$PATH
export LD_LIBRARY_PATH=/home/jugj/doc/mpich-4.0.2/mpich-install/lib:$LD_LIBRARY_PATH
export CPATH=/home/jugj/doc/mpich-4.0.2/mpich-install/include:$CPATH

export SU2_RUN=/usr/local/bin
export SU2_HOME=/home/jugj/SU2/su2code-SU2-1fe5981
export PATH=$PATH:$SU2_RUN
export PYTHONPATH=$PYTHONPATH:$SU2_RUN
export MPP_DATA_DIRECTORY=$SU2_HOME/subprojects/Mutationpp/data
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$SU2_HOME/build/subprojects/Mutationpp:$LD_LIBRARY_PATH

export MPICC=mpicc
export MPICXX=mpicxx
export MPIF90=mpif90

Anyone can give any suggestion?

[bigfootedrockmidget]

did you compile SU2 with the meson options:

-Dwith-mpi=enabled -Dcustom-mpi=true -Dextra-deps=mpich

And when you run meson, did you see that the compiler was using the mpich compiler, something like this:

C compiler for the host machine: /usr/bin/mpicc.mpich (gcc 11.4.0 "gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0") 
C linker for the host machine: /usr/bin/mpicc.mpich ld.bfd 2.38 
C++ compiler for the host machine: /usr/bin/mpicxx.mpich (gcc 11.4.0 "g++ (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0") 
C++ linker for the host machine: /usr/bin/mpicxx.mpich ld.bfd 2.38

In my case, I also have:

$echo $MPICC

 /usr/bin/mpicc.mpich
$

[So my guess is that you are not actually compiling with the mpich compiler.]

[Tomjugj]

Thank you so much! I finally run the testcase normally!
After reconfiguration with:
-Dextra-deps=mpich
the terminal returned: ERROR: Dependency "mpich" not found, tried pkgconfig and cmake
So i sudo apt-get install libmpich-dev, and problem solved.
Again, thank you so much for your reply!