View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0001242OpenFOAMBugpublic2014-03-27 13:352014-05-12 15:13
Reporteruser879Assigned Touser2 
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
PlatformLinuxOSUbuntuOS Version10.04
Summary0001242: Function Object "cloudInfo" leads to a crash in MPI mode
DescriptionUnfortunately the Function Object "cloudInfo" seems to wotk only with non decomposed cases. When calling the Function Object "cloudInfo" for post processing with "ExecFlowFunctionObjects" OF seems to get stuck on the following line:

Time = 0.0005
    Reading phi
    Reading U
    Reading p
No finite volume options present

Selecting thermodynamics package
{
    type hePsiThermo;
    mixture reactingMixture;
    transport sutherland;
    thermo janaf;
    energy sensibleEnthalpy;
    equationOfState perfectGas;
    specie specie;
}

Selecting chemistryReader chemkinReader
Reading CHEMKIN thermo data in new file format
Additional InformationError in MPI mode for decomposed cases:

faceSource cuttingplane_average output:
    areaAverage(sampledSurface) for p = 99991.3
    areaAverage(sampledSurface) for U = (7.71105e-05 -6.53393e-06 20.1689)
    areaAverage(sampledSurface) for T = 280.929
    areaAverage(sampledSurface) for rho = 1.23573
    areaAverage(sampledSurface) for C7H16 = 5.37203e-98

[philipp-Home:3137] *** An error occurred in MPI_Recv
[philipp-Home:3137] *** on communicator MPI_COMM_WORLD
[philipp-Home:3137] *** MPI_ERR_TRUNCATE: message truncated
[philipp-Home:3137] *** MPI_ERRORS_ARE_FATAL: your MPI job will now abort
--------------------------------------------------------------------------
mpirun has exited due to process rank 0 with PID 3137 on
node philipp-Home 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).
TagsNo tags attached.

Activities

user2

2014-05-12 15:13

  ~0003054

Thanks for the report - fixed by commit 8772bd4

Issue History

Date Modified Username Field Change
2014-03-27 13:35 user879 New Issue
2014-05-12 15:13 user2 Note Added: 0003054
2014-05-12 15:13 user2 Status new => resolved
2014-05-12 15:13 user2 Fixed in Version => 2.3.x
2014-05-12 15:13 user2 Resolution open => fixed
2014-05-12 15:13 user2 Assigned To => user2