[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: job is killed



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.

Reply to: