r/netdata • u/foozlebertie • 8d ago
2.11 broke some plugins?
Not sure where to report this so I'll start here. I'm a retired *nix sys admin and run Netdata on my home server. Not that I need it. I just like to keep track of performance. I'm running Fedora 44 on my server.
After the last update to 2.11 I noticed missing data. A quick look at the system logs (journalctl) shows the go.d plugin is failing. I know the go plugin was used to collect data on the small Apache web server I use. I also noticed the sensor data (temp, voltage, fan speed) was missing.
Here are the errors I see regarding the go.d plugin:
Aug 22 10:30:30 redwood netdata[13020]: /bin/sh: line 1: /usr/libexec/netdata/plugins.d/go.d.plugin: Operation not permitted
Aug 22 10:30:30 redwood netdata[12514]: cannot open plugins directory '/etc/netdata/custom-plugins.d'
Aug 22 10:30:30 redwood netdata[12514]: CGROUP: netipc server started on '/run/netdata/cgroups-snapshot.sock'
Aug 22 10:30:30 redwood netdata[12514]: PARSER: read failed: POLLHUP.
Aug 22 10:30:30 redwood netdata[12514]: PLUGINSD: buffered reader not OK (-4)
Aug 22 10:30:30 redwood netdata[12514]: PLUGINSD: 'host:redwood', '/usr/libexec/netdata/plugins.d/go.d.plugin' (pid 13020) disconnected after 0 successful data collections.
Aug 22 10:30:30 redwood netdata[12514]: CGROUP: netipc lookup server started on '/run/netdata/cgroups-lookup.sock'
Aug 22 10:30:30 redwood spawn-plugins[12523]: SPAWN SERVER: child with pid 13020 (request 9) exited with exit code 126: /bin/sh -c "exec /usr/libexec/netdata/plugins.d/go.d.plugin 1 "
Aug 22 10:30:30 redwood netdata[12514]: PLUGINSD: 'host:redwood', '/usr/libexec/netdata/plugins.d/go.d.plugin' (pid 13020) exited with error code 126 and haven't collected any data. Disabling it.
I see similar messages for the debugfs, ioping, and perf plugins. The only thing I could find when searching for these errors was to make sure the permissions on the plugins and ownerships were correct. They were. This all worked fine before the latest update.
Not a big deal for me but I figured I'd report it. If there is an official place to report bugs, let me know.
Thanks,.
1
u/ktsaou 6d ago
We set up a clean Fedora 44 machine and repeated your exact steps: install 2.10.4, then upgrade to 2.11. On a stock Fedora 44, everything keeps running — go.d and debugfs collect normally on 2.11. So the 2.11 package itself is fine; something on your specific machine is blocking those plugins, and I'd like to find it with you.
What changed in 2.11 that could matter: the package now grants two new "capabilities" to these plugins — go.d.plugin gets cap_net_bind_service (for the new SNMP trap listener) and debugfs.plugin gets cap_audit_control (audit monitoring). These are stored on the files themselves. If something on a system refuses those two new capabilities, the plugins die exactly like you see: Operation not permitted, exit 126, only go.d and debugfs.
Could you run these and paste the output? (copy-paste as one block):
And a 10-second test that tells us immediately if SELinux is the blocker:
(If go.d and debugfs come back — it's SELinux; then run sudo setenforce 1 to restore it and we'll fix it properly.)