|
[Sponsors] |
Parallel fluent process exiting before reading the mesh file |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
May 15, 2019, 14:40 |
Parallel fluent process exiting before reading the mesh file
|
#1 |
New Member
Sri Harsha Maddila
Join Date: Mar 2018
Posts: 10
Rep Power: 8 |
Here's the log:
Reading "C:/Users/mssharsha5/Desktop/Tet Meshes/Inner_53.msh"... Buffering for file scan... 5652239 nodes, binary. 155582 nodes, binary. 64993374 mixed interior faces, zone 1, binary. 16614 mixed interior faces, zone 2, binary. 12664 mixed interior faces, zone 3, binary. 3714 mixed interior faces, zone 4, binary. 19054 mixed interior faces, zone 5, binary. 2584 mixed velocity-inlet faces, zone 9, binary. 56386 triangular wall faces, zone 10, binary. 9508 triangular wall faces, zone 11, binary. 68335 triangular wall faces, zone 12, binary. 37755 triangular wall faces, zone 13, binary. 1164 mixed pressure-outlet faces, zone 14, binary. 96485 triangular wall faces, zone 15, binary. 38399 triangular wall faces, zone 16, binary. 32370213 mixed cells, zone 6, binary. Building... mesh auto partitioning mesh by Metis (fast) Checking.... Current memory used: 1071709788 bytes Maximum memory used: 1071709788 bytes ***Memory allocation failed for CreateCoarserGraph: cadjncy. Requested size: 68811968 bytes Current memory used: 1077339704 bytes Maximum memory used: 1077339704 bytes ***Memory allocation failed for CreateCoarserGraph: cadjncy. Requested size: 69692592 bytes ================================================== ============================ Node 2: Process 6372: Received signal SIGABRT. ================================================== ============================ Current memory used: 1095207976 bytes Maximum memory used: 1095207976 bytes ***Memory allocation failed for CreateCoarserGraph: cadjncy. Requested size: 69342072 bytes ================================================== ============================ Node 7: Process 812: Received signal SIGABRT. ================================================== ============================ ================================================== ============================ Node 6: Process 3440: Received signal SIGABRT. ================================================== ============================ Current memory used: 1096927024 bytes Maximum memory used: 1096927024 bytes ***Memory allocation failed for CreateCoarserGraph: cadjncy. Requested size: 69205552 bytes ================================================== ============================ Node 3: Process 652: Received signal SIGABRT. ================================================== ============================ Current memory used: 1078498344 bytes Maximum memory used: 1078498344 bytes ***Memory allocation failed for CreateCoarserGraph: cadjncy. Requested size: 69189128 bytes Current memory used: 1110259152 bytes Maximum memory used: 1110259152 bytes ***Memory allocation failed for CreateCoarserGraph: cadjncy. Requested size: 69537912 bytes Current memory used: 1082809236 bytes Maximum memory used: 1082809236 bytes ***Memory allocation failed for CreateCoarserGraph: cadjncy. Requested size: 69443160 bytes ================================================== ============================ Node 1: Process 3640: Received signal SIGABRT. ================================================== ============================ Current memory used: 1120340920 bytes Maximum memory used: 1120340920 bytes ***Memory allocation failed for CreateCoarserGraph: cadjncy. Requested size: 69704624 bytes ================================================== ============================ Node 5: Process 2928: Received signal SIGABRT. ================================================== ============================ ================================================== ============================ Node 0: Process 4668: Received signal SIGABRT. ================================================== ============================ ================================================== ============================ Node 4: Process 6000: Received signal SIGABRT. ================================================== ============================ MPI Application rank 0 exited before MPI_Finalize() with status 2 The fl process could not be started. So I have installed Ansys 18.2 on a Google Cloud instance in the hopes of completing my project simulations faster. This VM has 8 cores (Xeon CPU @2.3 GHz) and has 32 GB RAM. I have made the mesh files locally on my personal laptop so that I only need to open Fluent in the VM and not waste money. But when I opened parallel Fluent with 8, 6 or 4 processes (3D, Double-precision) and tried to read the .msh file they all crashed with the same error as logged above. Is there any way to get past this error and continue with the simulation. A very quick reply would be appreciated as I have my exams coming up too...Thank you for y'all time. EDIT: I have now started the meshing process from scratch on the VM via Workbench and the same error is hown in Fluent. An other error log Workbench shows is this: Ansys.Fluent.Cortex.CortexCommandFailedException: An error occured in FLUENT while applying case and settings informatins. An error occured in FLUENT while applying case and settings informatins. at Ansys.Fluent.Cortex.CortexCommunicator.SendMessage (String msg, String msgKey, String errorMessage, Boolean waitForReply) at Ansys.Fluent.FluentCommunicator.UpdateSetupInfo(Di ctionary`2 info) at Ansys.Fluent.Data.SetupData.ReadCaseModelInfo(IFul lContext context) Does this help anyone understand what is going on? Please help guys... Last edited by harsha2398; May 17, 2019 at 12:26. Reason: Update |
|
December 28, 2020, 02:04 |
|
#2 |
Member
Join Date: Apr 2020
Posts: 76
Rep Power: 6 |
Hello
Were you able to resolve this? I am having a similar crisis. Thanks |
|
December 28, 2020, 07:28 |
|
#3 |
Senior Member
Alexander
Join Date: Apr 2013
Posts: 2,363
Rep Power: 34 |
not enough RAM memory
make a new mesh with less number of finite volumes
__________________
best regards ****************************** press LIKE if this message was helpful |
|
December 29, 2020, 01:58 |
|
#4 |
Member
Join Date: Apr 2020
Posts: 76
Rep Power: 6 |
Thanks
I'll test that out |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Custom Thermophysical Properties | wsmith02 | OpenFOAM | 4 | June 1, 2023 15:30 |
how to calculate mass flow rate on patches and summation of that during the run? | immortality | OpenFOAM Post-Processing | 104 | February 16, 2021 09:46 |
[OpenFOAM] Annoying issue of automatic "Rescale to Data Range " with paraFoam/paraview 3.12 | keepfit | ParaView | 60 | September 18, 2013 04:23 |
"parabolicVelocity" in OpenFoam 2.1.0 ? | sawyer86 | OpenFOAM Running, Solving & CFD | 21 | February 7, 2012 12:44 |
DecomposePar links against liblamso0 with OpenMPI | jens_klostermann | OpenFOAM Bugs | 11 | June 28, 2007 18:51 |