Hi there,
You did not provide much information for people to be able to respond
to your issue. Please provide more detail, and maybe people can help.
I will assume or VM is running Debian Bookworm?
Do you know now to inspect logs using journalctl?
I tried to follow this web site, but it did not work for me, maybe you
can get the commands to work?
https://www.baeldung.com/linux/what-killed-a-process
Maybe # journalctl -kq | grep -i "killed" would return some log
entries?
Can you find your job using?
# ps -aux
If so maybe you can look for it in the logs using journalctl _PID=pid
?
https://commandmasters.com/commands/journalctl-linux/
# journalctl _PID=pid
or maybe
# journalctl | grep -i "killed"
I wonder if the word "kill is used in the logs?
# journalctl _PID=pid | grep -i kill
George.
On Tuesday, 31-12-2024 at 18:18
henrik@privatembox.com wrote:
my job consumes a lot of memory (almost consumes all of the system
allowed ram).
when the job is running, it will have the chance to be killed.
I just got the reminder in terminal: Killed. and job exits.
who is killing my job? linux kernel, or VPS management program?
(I am using a 2 core, 8g RAM kvm vps).
Thank you.
<html>
<head>
<style type="text/css">
body,p,td,div,span{
font-size:13px; font-family:Arial, Helvetica, sans-serif;
};
body p{
margin:0px;
}
</style>
</head>
<body><div>Hi there,</div><div><br></div><div>You did not provide much information for people to be able to respond to your issue. Please provide more detail, and maybe people can help.<br></div><div><br></div><div>I will assume or VM is running Debian
Bookworm?</div><div><br></div><div>Do you know now to inspect logs using journalctl?</div><div><br></div><div>I tried to follow this web site, but it did not work for me, maybe you can get the commands to work?<br>
https://www.baeldung.com/linux/what-
killed-a-process</div><div><br></div><div>Maybe # journalctl -kq | grep -i "killed" would return some log entries?</div><div><br></div><div>Can you find your job using?<br></div><div># ps -aux <br></div><div><br></div><div>If so maybe you can look for it
in the logs using journalctl _PID=pid ?<br></div><div><br></div><div>
https://commandmasters.com/commands/journalctl-linux/</div><div># journalctl _PID=pid</div><div><br></div><div>or maybe</div><div># journalctl | grep -i "killed"<br></div><div><br></div>
<div>I wonder if the word "kill is used in the logs?<br># journalctl _PID=pid | grep -i kill</div><div><br></div><div><br></div><div>George.</div><div><br></div><br>On Tuesday, 31-12-2024 at 18:18
henrik@privatembox.com wrote:<br><blockquote style="
border:0;border-left: 2px solid #22437f; padding:0px; margin:0px; padding-left:5px; margin-left: 5px; ">my job consumes a lot of memory (almost consumes all of the system <br>
allowed ram).<br>
when the job is running, it will have the chance to be killed.<br>
I just got the reminder in terminal: Killed. and job exits.<br>
who is killing my job? linux kernel, or VPS management program?<br>
(I am using a 2 core, 8g RAM kvm vps).<br>
Thank you.</blockquote></body></html>
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)