[Bug]: Running netdata increases oom_kill about netdata HOT 7 CLOSED

@hugovalente-pm I don't think it was a Netdata bug or we can do something about it. If processes are killed by the oom killer, dmesg (or /var/log/{messages,syslog}) should contain information about which processes are being killed.

from netdata.

Hey @dev-zero quick question, do you use streaming with TLS?

from netdata.

@tkatsoulas no, without TLS. And I've also tried without streaming, but the problem remained. So I think it is independent of the streaming configuration. I've also tried to narrow it down to some plugins, to no avail.

from netdata.

@dev-zero could you please update to v1.45 and try it again. There have been a tone of bug fixes since 1.44.3.

from netdata.

@hugovalente-pm thanks for the update
@ilyam8 unfortunately that's not true: looking at the Linux source code shows that if a process already exiting when being selected for killing due to OOM, no kernel message will be generated. This for example involves cases where a process in a control group is exhausting memory in an allocation, would be killed, but due to failing to allocate memory is already terminating.

from netdata.

the issue is still present, @ilyam8 can you please reopen the issue?

from netdata.

unfortunately that's not true: looking at the Linux source code shows that if a process already exiting when being selected for killing due to OOM, no kernel message will be generated.

Source?

I don't think OOM kills more than 2 thousand processes every minute, and it doesn't produce any messages, so it's impossible to keep track of what those thousands of processes are.

Can you confirm that you have thousands of processes killed every minute? Is it happening?

from netdata.