KILLED BY SIGNAL: 9 (Killed) during NpT simulation

Queries about input and output files, running specific calculations, etc.


Moderators: Global Moderator, Moderator

Locked
Message
Author
kai_oshiro
Newbie
Newbie
Posts: 19
Joined: Mon Apr 18, 2022 7:05 am

KILLED BY SIGNAL: 9 (Killed) during NpT simulation

#1 Post by kai_oshiro » Wed Jul 12, 2023 6:45 am

Dear developers,

I encountered the following error when I switched from NVT simulation to NpT simulation.

===================================================================================
= BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
= RANK 0 PID 3276411 RUNNING AT ccc126
= KILLED BY SIGNAL: 9 (Killed)
===================================================================================

I think this error is related to insufficient memory, but I don't know why the calculation crashes only for the NpT simulation.

Is there any way to avoid running out of memory?

Best regards,
Kai
You do not have the required permissions to view the files attached to this post.

jonathan_lahnsteiner2
Global Moderator
Global Moderator
Posts: 215
Joined: Fri Jul 01, 2022 2:17 pm

Re: KILLED BY SIGNAL: 9 (Killed) during NpT simulation

#2 Post by jonathan_lahnsteiner2 » Wed Jul 12, 2023 7:48 am

Dear kai_oshiro,

Signal 9 is sent by the Linux operating system to kill your job. This is usually not caused by the vasp code itself.
You can find some information about the sigkill command on this page:
https://komodor.com/learn/what-is-sigki ... ontainers/

I also checked your input files and they seem to be correct for what you want to do.
When running your job I checked the memory consumption. I am running on 8 cores and the
total amount is 2.5GB.
I would try to rerun the job and check if the error occurs again. Maybe you reached some time limit in your job scheduler.

If the error is still occurring please contact us again.


All the best Jonathan

kai_oshiro
Newbie
Newbie
Posts: 19
Joined: Mon Apr 18, 2022 7:05 am

Re: KILLED BY SIGNAL: 9 (Killed) during NpT simulation

#3 Post by kai_oshiro » Thu Jul 20, 2023 7:42 am

Dear jonathan_lahnsteiner,

Thank you for the detailed reply.

I tried on different settings and sorted it out.

I usually employ a combination of MPI and OpenMP to conserve memory usage because I use a computer whose memory is limited to 1.875GB/core, and the limitation sometimes causes problems in my calculations.

However, I changed those settings to the standard MPI with NCORE again, and my calculation ran correctly now.

Sorry for the trouble.

Best regards,
Kai

Locked