CFD Online Logo CFD Online URL
Home > Forums > OpenFOAM Bugs

foam-extend-3.0 ggi linearUpwind

Register Blogs Members List Search Today's Posts Mark Forums Read

LinkBack Thread Tools Display Modes
Old   January 19, 2014, 15:52
Default foam-extend-3.0 ggi linearUpwind
New Member
Join Date: Feb 2010
Posts: 26
Rep Power: 7
Pekka is on a distinguished road

I faced problem when the linearUpwind div scheme and ggi interface is used. Error message refers to the to mpi failure.
[0] error in IOstream "IOstream" for operation operator>>(Istream&, List<T>&) : reading first token
[0] file: IOstream at line 0.
[0]     From function IOstream::fatalCheck(const char*) const
[0]     in file db/IOstreams/IOstreams/IOstream.C at line 108.
FOAM parallel run exiting
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).
Error occur when the ggi pair is divided to multiple cpus. If ggi pair is on the same cpu then model works fine. Error can be repeat, for example, tutorial case "turboPassageRotating" by changing the div scheme from
div(phi,U)      Gauss upwind;
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.

Pekka is offline   Reply With Quote

Old   January 24, 2014, 04:44
Senior Member
Join Date: Mar 2009
Location: Sindelfingen, Germany
Posts: 583
Blog Entries: 5
Rep Power: 13
elvis is on a distinguished road
if I am not mistaken there is a Mantis BugTracker
elvis is offline   Reply With Quote


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

Similar Threads
Thread Thread Starter Forum Replies Last Post
error message with modeling a cube with a hold at the center hsingtzu OpenFOAM Native Meshers: blockMesh 2 March 14, 2012 10:56
mesh airfoil NACA0012 anand_30 OpenFOAM Meshing & Mesh Conversion 12 December 12, 2011 05:16
BlockMesh FOAM warning gaottino OpenFOAM Native Meshers: blockMesh 7 July 19, 2010 14:11
Axisymmetrical mesh Rasmus Gjesing (Gjesing) OpenFOAM Native Meshers: blockMesh 10 April 2, 2007 14:00
Import gmsh msh to Foam adorean Open Source Meshers: Gmsh, Netgen, CGNS, ... 24 April 27, 2005 08:19

All times are GMT -4. The time now is 13:32.