|
[Sponsors] |
![]() |
![]() |
#1 |
New Member
Huanhuan
Join Date: May 2019
Location: Hong Kong
Posts: 2
Rep Power: 0 ![]() |
Hi everyone,
I use 40 cores to run a case and everything is normal. However, when I only enlarge the domain in blockMeshDict, it shows the below error. I didn't use the snapyhexmesh and I only used blockMesh. Mesh is ok. Any comments is welcome. [0] #0 Foam::error: ![]() A process has executed an operation involving a call to the "fork()" system call to create a child process. Open MPI is currently operating in a condition that could result in memory corruption or other system errors; your job may hang, crash, or produce silent data corruption. The use of fork() (or system() or other calls that create child processes) is strongly discouraged. The process that invoked fork was: Local host: [[9653,1],0] (PID 9534) If you are *absolutely sure* that your application will successfully and correctly survive a call to fork(), you may disable this warning by setting the mpi_warn_on_fork MCA parameter to 0. -------------------------------------------------------------------------- at ??:? [0] #1 Foam::sigSegv::sigHandler(int) at ??:? [0] #2 ? in "/lib64/libc.so.6" [0] #3 Foam::mapDistributeBase::mapDistributeBase(Foam::L ist<long> const&, Foam::List<long> const&) at ??:? [0] #4 Foam::mapDistribute::mapDistribute(Foam::List<long > const&, Foam::List<long> const&) at ??:? [0] #5 Foam::mappedPatchBase::calcMapping() const at ??:? [0] #6 void Foam::mappedPatchBase::distribute<double>(Foam::Li st<double>&) const at ??:? [0] #7 Foam::mappedPatchFieldBase<double>::mappedField() const at ??:? [0] #8 Foam::mappedFieldFvPatchField<double>::updateCoeff s() at ??:? [0] #9 Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh>::Boundary::evaluate() at ??:? [0] #10 Foam::LESModels::WALE<Foam::IncompressibleTurbulen ceModel<Foam::transportModel> >::correctNut() at ??:? [0] #11 ? at ??:? [0] #12 __libc_start_main in "/lib64/libc.so.6" [0] #13 ? at ??:? [hhnode-ib-53:09534] *** Process received signal *** [hhnode-ib-53:09534] Signal: Segmentation fault (11) [hhnode-ib-53:09534] Signal code: (-6) [hhnode-ib-53:09534] Failing at address: 0x78d0000253e [hhnode-ib-53:09534] [ 0] /lib64/libc.so.6(+0x363b0)[0x7f93687753b0] [hhnode-ib-53:09534] [ 1] /lib64/libc.so.6(gsignal+0x37)[0x7f9368775337] [hhnode-ib-53:09534] [ 2] /lib64/libc.so.6(+0x363b0)[0x7f93687753b0] Thanks! |
|
![]() |
![]() |
![]() |
![]() |
#2 |
New Member
Roithamer
Join Date: Feb 2021
Posts: 7
Rep Power: 5 ![]() |
This error happens when you send intertwined process to processor cores. From this point of view, domain enlarge causing that error makes sense. In your case OpenFOAM probably can not decompose the case properly according to your processor cores. Did you try disable this warning just like written in error message or manipulate decomposing options such as number of processor ?
|
|
![]() |
![]() |
![]() |
![]() |
#3 |
New Member
Huanhuan
Join Date: May 2019
Location: Hong Kong
Posts: 2
Rep Power: 0 ![]() |
Thank you for your reply.
The problem has been solved. It is not decomposed issue. It is actually the BC problem. Changing it to the Cyclic one solved this problem. |
|
![]() |
![]() |
![]() |
Tags |
mesh 3d, parallel |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Getting Started with OpenFOAM | wyldckat | OpenFOAM | 26 | June 21, 2024 07:54 |
Map of the OpenFOAM Forum - Understanding where to post your questions! | wyldckat | OpenFOAM | 10 | September 2, 2021 06:29 |
Floating issue when running openfoam through grasshopper | Mark JIN | OpenFOAM | 1 | May 24, 2017 22:04 |
Issue installation OpenFOAM - libopen-rte.so.0 | Voyage_gui | OpenFOAM | 1 | August 12, 2011 04:46 |
Modified OpenFOAM Forum Structure and New Mailing-List | pete | Site News & Announcements | 0 | June 29, 2009 06:56 |