# Ebpf.plugin error logged

**URL:** https://community.netdata.cloud/t/ebpf-plugin-error-logged/1388
**Category:** Help
**Tags:** agent, collectors
**Created:** [June 1, 2021, 8:14am UTC](https://community.netdata.cloud/t/ebpf-plugin-error-logged/1388 "2021-06-01T08:14:23Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![kinsham](https://avatars.discourse-cdn.com/v4/letter/k/7cd45c/32.png) [@kinsham](https://community.netdata.cloud/u/kinsham)
#### Post date: [June 1, 2021, 8:14am UTC](https://community.netdata.cloud/t/ebpf-plugin-error-logged/1388/1 "2021-06-01T08:14:23Z")

</div>

I see the error below show up in syslog occasionally. It is true that the file mentioned does not exist at the location given. It does however exist at /usr/lib/netdata/conf.d/

Jun 1 08:49:58 homeserver ebpf.plugin: Cannot load the ebpf configuration file (null)  
Jun 1 08:49:58 homeserver ebpf.plugin: PROCFILE: Cannot open file '/etc/netdata/apps\_groups.conf

Should I copy/move the file to the expected location?

Cheers  
CW

---

<div class="post-metadata">

### Author: ![Thiago\_Marques\_0](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/thiago_marques_0/32/281_2.png) [@Thiago\_Marques\_0](https://community.netdata.cloud/u/Thiago_Marques_0)
#### Post date: [June 3, 2021, 12:15pm UTC](https://community.netdata.cloud/t/ebpf-plugin-error-logged/1388/2 "2021-06-03T12:15:48Z")

</div>

Hello @kinsham ,

We had a discussion few days ago in our github related to this [issue](https://github.com/netdata/netdata/issues/11151#issuecomment-842183252).

To parse the files that the error is reporting, we are using our the same functions we use to parse the `proc` files, it is already in our horizon to bring a change in our plugin to convert this error in a simple `info` message.

It is not necessary to copy the file as you said, because Netdata will use the internal defaults.

Best regards!

---

<div class="post-metadata">

### Author: ![ilyam8](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ilyam8/32/134_2.png) [@ilyam8](https://community.netdata.cloud/u/ilyam8)
#### Post date: [June 8, 2021, 7:19pm UTC](https://community.netdata.cloud/t/ebpf-plugin-error-logged/1388/3 "2021-06-08T19:19:40Z")

</div>

@kinsham

TL;DR

It is not error level message, but info (or even debug). All is ok, nothing to worry about.

We are aware of the problem, but it is not that easy to fix (to change severity level of the mesage) as it may look. We will fix it anyway.

---

<div class="post-metadata">

### Author: ![NotCoolKiwi](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/notcoolkiwi/32/1613_2.png) [@NotCoolKiwi](https://community.netdata.cloud/u/NotCoolKiwi)
#### Post date: [March 13, 2022, 6:42pm UTC](https://community.netdata.cloud/t/ebpf-plugin-error-logged/1388/4 "2022-03-13T18:42:05Z")

</div>

Is this being worked on? I’m still getting the message as an error.

---

<div class="post-metadata">

### Author: ![ilyam8](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ilyam8/32/134_2.png) [@ilyam8](https://community.netdata.cloud/u/ilyam8)
#### Post date: [March 13, 2022, 7:06pm UTC](https://community.netdata.cloud/t/ebpf-plugin-error-logged/1388/5 "2022-03-13T19:06:26Z")

</div>

Hi, @NotCoolKiwi. This has not been fixed yet. This issue is almost the same as [[static systemd services] =\> PROCFILE: Cannot open file '/sys/fs/cgroup/blkio/system.slice/.... · Issue #11397 · netdata/netdata · GitHub](https://github.com/netdata/netdata/issues/11397). I suggest you [open a bug report](https://github.com/netdata/netdata/issues/new?assignees=&labels=bug%2Cneeds+triage&template=BUG_REPORT.yml&title=%5BBug%5D%3A+) in the netdata/netdata repository.

@Thiago_Marques_0 I think that is extremely easy to fix, we just need to pass `PROCFILE_FLAG_NO_ERROR_ON_FILE_IO` flag to [procfile\_open](https://github.com/netdata/netdata/blob/cda2fe06df0969cdf9c878b6c368fa19e1346898/collectors/ebpf.plugin/ebpf_apps.c#L278) when loading user configuration file.

---

<div class="post-metadata">

### Author: ![ilyam8](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ilyam8/32/134_2.png) [@ilyam8](https://community.netdata.cloud/u/ilyam8)
#### Post date: [March 13, 2022, 8:41pm UTC](https://community.netdata.cloud/t/ebpf-plugin-error-logged/1388/6 "2022-03-13T20:41:53Z")

</div>

@kinsham we’ve discussed the issue internally and decided to just fix it - no need to open a bug report. Will be fixed next week.

---

<div class="post-metadata">

### Author: ![Thiago\_Marques\_0](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/thiago_marques_0/32/281_2.png) [@Thiago\_Marques\_0](https://community.netdata.cloud/u/Thiago_Marques_0)
#### Post date: [March 13, 2022, 10:28pm UTC](https://community.netdata.cloud/t/ebpf-plugin-error-logged/1388/7 "2022-03-13T22:28:01Z")

</div>

Hello guys,

The PR [Remove unecessary error report for proc and sys files by thiagoftsm · Pull Request #12385 · netdata/netdata · GitHub](https://github.com/netdata/netdata/pull/12385) will fix this issue and it will create the basis to fix analogous issues as soon it ismerged.

Best regards,

Thiago

---

<div class="post-metadata">

### Author: ![NotCoolKiwi](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/notcoolkiwi/32/1613_2.png) [@NotCoolKiwi](https://community.netdata.cloud/u/NotCoolKiwi)
#### Post date: [March 14, 2022, 12:14am UTC](https://community.netdata.cloud/t/ebpf-plugin-error-logged/1388/8 "2022-03-14T00:14:16Z")

</div>

Thank you so much for the fast fix and replies!

---

<div class="post-metadata">

### Author: ![Thiago\_Marques\_0](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/thiago_marques_0/32/281_2.png) [@Thiago\_Marques\_0](https://community.netdata.cloud/u/Thiago_Marques_0)
#### Post date: [March 14, 2022, 2:41pm UTC](https://community.netdata.cloud/t/ebpf-plugin-error-logged/1388/9 "2022-03-14T14:41:54Z")

</div>

Hello,

PR was merged, so next nightly release will have the issue fixed, and we will work during the week to fix the issue for other collectors.

Best regards!
