Ilya Mashchenko

@Woart hey. There appears to be an issue with a proc.plugin collector causing crashes. Can you help us to find which one? - open `netdata.conf`. - search for the `[plugin:proc]`...

@Woart can you try disabling `[plugin:proc]` modules one by one and find the one that is causing Netdata to crash?

@Woart, any chance you can install from source to get the coredump? ``` sudo apt-get install systemd-coredump git clone --recursive https://github.com/netdata/netdata # install required packages for building from the source...

This should be fixed in tomorrow's nightly version. Can you guys test it?

@thiagoftsm, excuse me, what exactly are you going to consider? @nodiscc is saying that he followed https://learn.netdata.cloud/docs/collecting-metrics/ebpf/ebpf-socket and get ``` ebpf.plugin[649749]: Does not have a configuration file inside `/etc/netdata/ebpf.d.conf. It...

@nodiscc > ebpf.plugin[649749]: Does not have a configuration file inside `/etc/netdata/ebpf.d.conf. It will try to load stock file. Expected because it is a different file. The ebpf plugin has modules...

Hey, @withinboredom. > approximately ^ 100's of thousands of times until the node - How did you come to this conclusion? - Can you show `lsof` output with a lot...

The simplest form: - download file(s) from the community repo - move them to appropriate directories - restart Netdata A bash script will do for this case.

@netdata/agent-sre this PR has 17 failed CI checks (and 6 in progress at the moment, maybe there will be more failed), is that expected? Asking because you've approved it.

@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...