|
[Sponsors] |
OpenFOAM 2.0.0. and 2.0.1 doesn't work in parallel mode |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
September 9, 2011, 05:39 |
OpenFOAM 2.0.0. and 2.0.1 doesn't work in parallel mode
|
#1 |
New Member
Roman Voronov
Join Date: May 2010
Location: Russia
Posts: 13
Rep Power: 16 |
Hi all! Help me please! When I try to run pisoFoam in parallel with
Code:
mpirun - np 4 pisoFoam -parallel Code:
Build : 2.0.0-a317a4e7cd55 Exec : interFoam -parallel Date : Sep 09 2011 Time : 15:24:24 Host : 5101-5 PID : 27833 Case : /home/roman/OpenFOAM/roman-2.0.1/run/damBreak nProcs : 4 Slaves : 3 ( 5101-5.27834 5101-5.27835 5101-5.27836 ) Pstream initialized with: floatTransfer : 0 nProcsSimpleSum : 0 commsType : nonBlocking [0] [0] [0] --> FOAM FATAL IO ERROR: [0] ill defined primitiveEntry starting at keyword 'slaves' on line 0 and ending at line 3 [0] [0] file: IStringStream.sourceFile at line 3. [0] [0] From function primitiveEntry::readEntry(const dictionary&, Istream&) [0] in file db/dictionary/primitiveEntry/primitiveEntryIO.C at line 165. [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. -------------------------------------------------------------------------- -------------------------------------------------------------------------- mpirun has exited due to process rank 0 with PID 27833 on node 5101-5 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). -------------------------------------------------------------------------- Tell me please what does it mean? Everything worked fine until I reinstalled Linux |
|
September 12, 2011, 03:53 |
|
#2 |
Senior Member
Roman Thiele
Join Date: Aug 2009
Location: Eindhoven, NL
Posts: 374
Rep Power: 21 |
did you decompose the mesh before running it in parallel?
__________________
~roman |
|
September 12, 2011, 10:38 |
|
#3 |
New Member
Roman Voronov
Join Date: May 2010
Location: Russia
Posts: 13
Rep Power: 16 |
of course. The number of "parts" corresponds to number of processor cores.
PS. I try to run OpenFOAM on older version of Linux, and I got the same error. Although it worked fine in august of this year. Last edited by rv82; September 28, 2011 at 04:25. |
|
October 3, 2011, 11:47 |
|
#4 |
New Member
Roman Voronov
Join Date: May 2010
Location: Russia
Posts: 13
Rep Power: 16 |
Problem was found! Thanks to developers of OpenFOAM.
OpenFOAM doesn't like the name of my machine -- 5101-5. I have changed this name to a5101_5 and OpenFOAM started successfully! |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
SpalartAllmaras wall function in OpenFOAM 2.0.1 | moser_r | OpenFOAM Running, Solving & CFD | 4 | September 18, 2013 18:37 |