dieselEngineFoam_parallel crash at SOI
 

Hi everyone
Has anyone experienced that the case crash just at start of injection with the error ...

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

Running on just one processors works fine but when running parallel computations, ranging from 2 to 64 cores, it just crashed right away.
The mesh is fine, the time step is fine, the fields looks fine and I've even tried using different decomposition methods, simple and scotch.

Hopefully someone knows how to fix this problem
Regards
Rickard

Which OF version are you using?

This report may interest you; http://www.openfoam.org/mantisbt/view.php?id=577 , though it applies to 2.1.x, which do not have the diesel* solvers anymore.

K

Hej Kalle
Thanks for the reply, but for some reason Im using the 2.0.x just for this last case. I am moving over to 2.1.x, hopefully I wont have this problem anymore.

I have never had this problem before and I have run successfully many times before...this problem however I cant resolve.

I see now that the 1.7.1 version is working.

Rickard

As you can guess from the report, there are similar issues in 2.1.x (git pulled today).
Let's await the developers.