|
[Sponsors] |
January 19, 2014, 15:52 |
foam-extend-3.0 ggi linearUpwind
|
#1 |
New Member
Join Date: Feb 2010
Posts: 28
Rep Power: 16 |
Hi,
I faced problem when the linearUpwind div scheme and ggi interface is used. Error message refers to the to mpi failure. Code:
[0] [0] [0] --> FOAM FATAL IO ERROR: [0] error in IOstream "IOstream" for operation operator>>(Istream&, List<T>&) : reading first token [0] [0] file: IOstream at line 0. [0] [0] From function IOstream::fatalCheck(const char*) const [0] in file db/IOstreams/IOstreams/IOstream.C at line 108. [0] FOAM parallel run exiting [0] -------------------------------------------------------------------------- MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD with errorcode 1. NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes. You may or may not see output from other processes, depending on exactly when Open MPI kills them. -------------------------------------------------------------------------- [Kone3:18215] *** An error occurred in MPI_Recv [Kone3:18215] *** on communicator MPI_COMM_WORLD [Kone3:18215] *** MPI_ERR_TRUNCATE: message truncated [Kone3:18215] *** MPI_ERRORS_ARE_FATAL: your MPI job will now abort -------------------------------------------------------------------------- mpirun has exited due to process rank 2 with PID 18215 on node Kone3 exiting improperly. There are two reasons this could occur: 1. this process did not call "init" before exiting, but others in the job did. This can cause a job to hang indefinitely while it waits for all processes to call "init". By rule, if one process calls "init", then ALL processes must call "init" prior to termination. 2. this process called "init", but exited without calling "finalize". By rule, all processes that call "init" MUST call "finalize" prior to exiting or it will be considered an "abnormal termination" This may have caused other processes in the application to be terminated by signals sent by mpirun (as reported here). -------------------------------------------------------------------------- Code:
div(phi,U) Gauss upwind; Code:
div(phi,U) Gauss linearUpwind Gauss linear; Similar models works fine also using "Gauss linear;" div scheme. Whether this is true bug or user error? All ideas and comments are welcomed to solving this problem. BR/Pekka |
|
January 24, 2014, 04:44 |
|
#2 |
Senior Member
|
Hi,
if I am not mistaken there is a Mantis BugTracker http://sourceforge.net/apps/mantisbt.../main_page.php |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[Other] mesh airfoil NACA0012 | anand_30 | OpenFOAM Meshing & Mesh Conversion | 13 | March 7, 2022 18:22 |
[blockMesh] error message with modeling a cube with a hold at the center | hsingtzu | OpenFOAM Meshing & Mesh Conversion | 2 | March 14, 2012 10:56 |
[blockMesh] BlockMesh FOAM warning | gaottino | OpenFOAM Meshing & Mesh Conversion | 7 | July 19, 2010 15:11 |
[blockMesh] Axisymmetrical mesh | Rasmus Gjesing (Gjesing) | OpenFOAM Meshing & Mesh Conversion | 10 | April 2, 2007 15:00 |
[Gmsh] Import gmsh msh to Foam | adorean | OpenFOAM Meshing & Mesh Conversion | 24 | April 27, 2005 09:19 |