CFD Online Discussion Forums

CFD Online Discussion Forums (https://www.cfd-online.com/Forums/)
-   OpenFOAM Running, Solving & CFD (https://www.cfd-online.com/Forums/openfoam-solving/)
-   -   mpirun error(signall 9(killed)) (https://www.cfd-online.com/Forums/openfoam-solving/111374-mpirun-error-signall-9-killed.html)

dark lancer January 5, 2013 07:07

mpirun error(signall 9(killed))
 
hi
I run my case in parallel with dsmc on the notebook It's work but when I run on my pc , see this error:
I am appreciate for any help.
\*---------------------------------------------------------------------------*/
Build : 2.1.1-221db2718bbb
Exec : dsmcInitialise -parallel
Date : Dec 26 2012
Time : 11:40:09
Host : "172-15-2-166"
PID : 4427
Case : /home/moosaie/OpenFOAM/moosaie-2.1.1/run/tutorials/discreteMethods/dsmcFoam/hemispherical
nProcs : 4
Slaves :
3
(
"172-15-2-166.4428"
"172-15-2-166.4429"
"172-15-2-166.4430"

)

Pstream initialized with:
floatTransfer : 0
nProcsSimpleSum : 0
commsType : nonBlocking
fileModificationChecking : Monitoring run-time modified files using timeStampMaster
allowSystemOperations : Disallowing user-supplied system call operations

// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time

Create mesh for time = 0

Initialising dsmc for Time = 0


Constructing constant properties for
Air

Initialising particles
--------------------------------------------------------------------------
mpirun noticed that process rank 2 with PID 4429 on node 172-15-2-166 exited on signal 9 (Killed).
--------------------------------------------------------------------------

dark lancer January 5, 2013 08:07

this the log.dsmcfoam file:
Quote:

Build : 2.1.1-221db2718bbb
Exec : dsmcFoam -parallel
Date : Dec 26 2012
Time : 11:40:56
Host : "172-15-2-166"
PID : 4438
Case : /home/moosaie/OpenFOAM/moosaie-2.1.1/run/tutorials/discreteMethods/dsmcFoam/hemispherical
nProcs : 4
Slaves :
3
(
"172-15-2-166.4439"
"172-15-2-166.4440"
"172-15-2-166.4441"
)

Pstream initialized with:
floatTransfer : 0
nProcsSimpleSum : 0
commsType : nonBlocking
fileModificationChecking : Monitoring run-time modified files using timeStampMaster
allowSystemOperations : Disallowing user-supplied system call operations

// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time

Create mesh for time = 0


Constructing dsmcCloud
Selecting BinaryCollisionModel VariableHardSphere
Selecting WallInteractionModel MaxwellianThermal
Selecting InflowBoundaryModel FreeStream

Constructing constant properties for
Air

Starting time loop

Reading/calculating field rhoNMean

Reading/calculating field rhoMMean

Reading/calculating field dsmcRhoNMean

Reading/calculating field momentumMean

Reading/calculating field linearKEMean

Reading/calculating field internalEMean

Reading/calculating field iDofMean

Reading/calculating field qMean

Reading/calculating field fDMean

fieldAverage: starting averaging at time 0

Time = 1e-06

--------------------------------------------------------------------------
mpirun noticed that process rank 0 with PID 4438 on node 172-15-2-166 exited on signal 9 (Killed).
--------------------------------------------------------------------------

dark lancer January 6, 2013 05:12

nobody can help me!!!???

odin February 6, 2014 05:44

exited on signal 9 (Killed)
 
"If your job received a KILL signal (#9), it probably comes from the batch system on these machines. Your job needed more resources than what you asked for, or more than is available on the machine (memory,..."

http://forum.abinit.org/viewtopic.php?f=14&t=95

Rasmusiwersen May 19, 2021 03:34

Quote:

Originally Posted by odin (Post 473709)
"If your job received a KILL signal (#9), it probably comes from the batch system on these machines. Your job needed more resources than what you asked for, or more than is available on the machine (memory,..."

http://forum.abinit.org/viewtopic.php?f=14&t=95

Yes, increasing the amount of RAM did the trick for me. I am running OpenFOAM2012 on Virtual box, and increasing the guest RAM got me moving form this error.... to another unfortunately... but that is for another post to fix.

breznak December 18, 2023 09:11

sorry wrong post


All times are GMT -4. The time now is 15:30.