 |
 |
 |
|
|
|
[Sponsors] | ||||
February 18, 2021, 19:59
|
fluent error
|
#1 |
|
New Member
HOJUN YU
Join Date: Jul 2020
Posts: 24
Rep Power: 5  |
hi all
I using linux / fluent perallel / UDF next number 160/161 is server name The following error occurred while using the front. fluent_mpi.17.2.0: Rank 0:39: MPI_Waitall: 863: IBV connection to 60 (pid 24800) on channel 0 is broken. ibv_poll_cq(): bad status 12 fluent_mpi.17.2.0: Rank 0:34: MPI_Waitall: 863: IBV connection to 56 (pid 24796) on channel 0 is broken. ibv_poll_cq(): bad status 12 fluent_mpi.17.2.0: Rank 0:36: MPI_Waitall: 863: IBV connection to 56 (pid 24796) on channel 0 is broken. ibv_poll_cq(): bad status 12 fluent_mpi.17.2.0: Rank 0:38: MPI_Waitall: 863: IBV connection to 56 (pid 24796) on channel 0 is broken. ibv_poll_cq(): bad status 12 fluent_mpi.17.2.0: Rank 0:34: MPI_Waitall: self 160 peer 161i (rank: 56) fluent_mpi.17.2.0: Rank 0:36: MPI_Waitall: self 160 peer 161i (rank: 56) fluent_mpi.17.2.0: Rank 0:38: MPI_Waitall: self 160 peer 161i (rank: 56) fluent_mpi.17.2.0: Rank 0:36: MPI_Waitall: error message: transport retry exceeded error fluent_mpi.17.2.0: Rank 0:38: MPI_Waitall: error message: transport retry exceeded error fluent_mpi.17.2.0: Rank 0:34: MPI_Waitall: error message: transport retry exceeded error fluent_mpi.17.2.0: Rank 0:38: MPI_Waitall: Internal MPI error fluent_mpi.17.2.0: Rank 0:39: MPI_Waitall: self 160 peer 161i (rank: 60) fluent_mpi.17.2.0: Rank 0:36: MPI_Waitall: Internal MPI error fluent_mpi.17.2.0: Rank 0:34: MPI_Waitall: Internal MPI error fluent_mpi.17.2.0: Rank 0:39: MPI_Waitall: error message: transport retry exceeded error fluent_mpi.17.2.0: Rank 0:39: MPI_Waitall: Internal MPI error MPI Application rank 34 exited before MPI_Finalize() with status 16 ================================================== ============================ ================================================== ============================ Node 42: Process 31387: Received signal SIGTERM. Node 41: Process 31386: Received signal SIGTERM. Node 47: Process 31392: Received signal SIGTERM. ================================================== ============================ ================================================== ============================ Node 35: Process 31380: Received signal SIGTERM. Node 40: Process 31385: Received signal SIGTERM. ================================================== ============================ Node 44: Process 31389: Received signal SIGTERM. ================================================== ============================ Node 32: Process 31377: Received signal SIGTERM. ================================================== ============================ Node 43: Process 31388: Received signal SIGTERM. ================================================== ============================ ================================================== ============================ Node 46: Process 31391: Received signal SIGTERM. Node 45: Process 31390: Received signal SIGTERM. Node 33: Process 31378: Received signal SIGTERM. ================================================== ============================ ================================================== ============================ Node 37: Process 31382: Received signal SIGTERM. help me thank you |
|
|
|
|
 |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| [blockMesh] blockMesh with double grading. | spwater | OpenFOAM Meshing & Mesh Conversion | 92 | January 12, 2019 09:00 |
| ParaView for OF-1.6-ext | Chrisi1984 | OpenFOAM Installation | 0 | December 31, 2010 06:42 |
| [swak4Foam] groovyBC: problems compiling: "flex: not found" and "undefined reference to ..." | sega | OpenFOAM Community Contributions | 12 | February 17, 2010 09:30 |
| Installation OF1.5-dev | ttdtud | OpenFOAM Installation | 46 | May 5, 2009 02:32 |
| error while compiling the USER Sub routine | CFD user | CFX | 3 | November 25, 2002 15:16 |
Linear Mode
