Bug description
Follow-up to #23046 / #23047. The driver-580 XML temperature parser issue reported in #23046 is resolved in v2.10.4 — confirmed, thanks.
However, on the same host a separate problem remains: the daemon-managed nvidia_smi collector now delivers GPU metrics only intermittently. The nvidia_smi.gpu_temperature context flaps between N nodes and 0, so GPU data is mostly missing from charts and Cloud.
A standalone debug run collects correctly every time (sudo -u netdata .../go.d.plugin -d -m nvidia_smi -> SET 'temperature' = 32), but the running agent usually exposes nothing (curl -s http://localhost:19999/api/v1/allmetrics | grep -ic nvidia -> 0), even though the go.d.plugin and 'nvidia-smi -q -x -l 5' processes are alive. AMD sensors.gpu hosts are steady, so it's specific to nvidia_smi. Tried restart and loop_mode: no — no change. Env: NVIDIA RTX PRO 6000 Blackwell, driver 580.95.05, netdata v2.10.4, Debian 13.
Expected behavior
The daemon-managed nvidia_smi collector should deliver GPU metrics (temperature, fan, power) reliably on every collection cycle — the same way the standalone debug run does — so the charts and the nvidia_smi.gpu_temperature context stay continuously populated instead of
flapping between N nodes and 0.
Steps to reproduce
- Host with an NVIDIA RTX PRO 6000 Blackwell (driver 580.95.05, CUDA 13.0) running netdata v2.10.4 on Debian 13.
- Run the collector standalone in debug — it collects fine, as root and as the netdata user:
sudo -u netdata /usr/libexec/netdata/plugins.d/go.d.plugin -d -m nvidia_smi
-> emits: SET 'temperature' = 32 (plus fan/power/utilization charts)
- Confirm nvidia-smi works for the netdata user:
sudo -u netdata nvidia-smi --query-gpu=temperature.gpu --format=csv,noheader -> 32
- Now watch what the running daemon actually exposes over ~60s:
for i in 1 2 3 4 5 6; do date +%T; curl -s http://localhost:19999/api/v1/allmetrics | grep -ic nvidia; sleep 10; done
-> mostly 0, only occasionally non-zero (go.d.plugin and 'nvidia-smi -q -x -l 5' are alive the whole time)
- In Netdata Cloud, the nvidia_smi.gpu_temperature context flaps between N nodes and 0; GPU charts are mostly empty.
Installation method
from git
System info
uname -a; grep -HvE "^#|URL" /etc/*release
Linux jai1 6.12.48+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.48-1 (2025-09-20) x86_64 GNU/Linux
/etc/os-release:PRETTY_NAME="Debian GNU/Linux 13 (trixie)"
/etc/os-release:NAME="Debian GNU/Linux"
/etc/os-release:VERSION_ID="13"
/etc/os-release:VERSION="13 (trixie)"
/etc/os-release:VERSION_CODENAME=trixie
/etc/os-release:DEBIAN_VERSION_FULL=13.1
/etc/os-release:ID=debian
cat /etc/os-release
uname -a
PRETTY_NAME="Debian GNU/Linux 13 (trixie)"
NAME="Debian GNU/Linux"
VERSION_ID="13"
VERSION="13 (trixie)"
VERSION_CODENAME=trixie
DEBIAN_VERSION_FULL=13.1
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
uname -r
6.12.48+deb13-amd64
BUG_REPORT_URL="https://bugs.debian.org/"
Linux jai1 6.12.48+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.48-1 (2025-09-20) x86_64 GNU/Linux
Netdata build info
netdata -W buildinfo
time=2026-07-20T23:03:20.543-07:00 comm=netdata source=daemon level=notice errno="2, No such file or directory" tid=145911 msg="CONFIG: cannot load user config '/etc/netdata/stream.conf'. Will try stock config."
Packaging:
Netdata Version ____________________________________________ : v2.10.4
Installation Type __________________________________________ : binpkg-deb
Package Architecture _______________________________________ : x86_64
Package Distro _____________________________________________ : debian 13
Configure Options __________________________________________ : cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_C_STANDARD=11 -DCMAKE_CXX_STANDARD=17 -DBUILD_SHARED_LIBS=OFF -DCMAKE_C_FLAGS=' -fexceptions -fno-omit-frame-pointer -funwind-tables -fasynchronous-unwind-tables' -DCMAKE_CXX_FLAGS=' -fexceptions -fno-omit-frame-pointer -funwind-tables -fasynchronous-unwind-tables' -DCMAKE_COMPILE_DEFINITIONS='_GNU_SOURCE' -DCMAKE_EXE_LINKER_FLAGS=' -fexceptions -rdynamic' -DCMAKE_SHARED_LINKER_FLAGS=''
Default Directories:
User Configurations ________________________________________ : /etc/netdata
Stock Configurations _______________________________________ : /usr/lib/netdata/conf.d
Ephemeral Databases (metrics data, metadata) _______________ : /var/cache/netdata
Permanent Databases ________________________________________ : /var/lib/netdata
Plugins ____________________________________________________ : /usr/libexec/netdata/plugins.d
Static Web Files ___________________________________________ : /usr/share/netdata/web
Log Files __________________________________________________ : /var/log/netdata
Lock Files _________________________________________________ : /var/lib/netdata/lock
Home _______________________________________________________ : /var/lib/netdata
Operating System:
Kernel _____________________________________________________ : Linux
Kernel Version _____________________________________________ : 6.12.48+deb13-amd64
Operating System ___________________________________________ : Debian GNU/Linux
Operating System ID ________________________________________ : debian
Operating System ID Like ___________________________________ : unknown
Operating System Version ___________________________________ : 13 (trixie)
Operating System Version ID ________________________________ : none
Detection __________________________________________________ : /etc/os-release
Hardware:
CPU Cores __________________________________________________ : 64
CPU Frequency ______________________________________________ : 3800000000
RAM Bytes __________________________________________________ : 134745366528
Disk Capacity ______________________________________________ : 4000797868032
CPU Architecture ___________________________________________ : x86_64
Virtualization Technology __________________________________ : none
Virtualization Detection ___________________________________ : systemd-detect-virt
Container:
Container __________________________________________________ : none
Container Detection ________________________________________ : systemd-detect-virt
Container Orchestrator _____________________________________ : none
Container Operating System _________________________________ : none
Container Operating System ID ______________________________ : none
Container Operating System ID Like _________________________ : none
Container Operating System Version _________________________ : none
Container Operating System Version ID ______________________ : none
Container Operating System Detection _______________________ : none
Features:
Built For __________________________________________________ : Linux
Netdata Cloud ______________________________________________ : YES
Health (trigger alerts and send notifications) _____________ : YES
Streaming (stream metrics to parent Netdata servers) _______ : YES
Back-filling (of higher database tiers) ____________________ : YES
Replication (fill the gaps of parent Netdata servers) ______ : YES
Streaming and Replication Compression ______________________ : YES (zstd lz4 gzip brotli)
Contexts (index all active and archived metrics) ___________ : YES
Tiering (multiple dbs with different metrics resolution) ___ : YES (5)
Machine Learning ___________________________________________ : YES
Memory Allocator ___________________________________________ : system
Database Engines:
dbengine (compression) _____________________________________ : YES (zstd lz4)
alloc ______________________________________________________ : YES
ram ________________________________________________________ : YES
none _______________________________________________________ : YES
Connectivity Capabilities:
ACLK (Agent-Cloud Link: MQTT over WebSockets over TLS) _____ : YES
static (Netdata internal web server) _______________________ : YES
WebRTC (experimental) ______________________________________ : NO
Native HTTPS (TLS Support) _________________________________ : YES
TLS Host Verification ______________________________________ : YES
Libraries:
LZ4 (extremely fast lossless compression algorithm) ________ : YES
ZSTD (fast, lossless compression algorithm) ________________ : YES
zlib (lossless data-compression library) ___________________ : YES
Brotli (generic-purpose lossless compression algorithm) ____ : YES
protobuf (platform-neutral data serialization protocol) ____ : YES (system)
OpenSSL (cryptography) _____________________________________ : YES
libdatachannel (stand-alone WebRTC data channels) __________ : NO
JSON-C (lightweight JSON manipulation) _____________________ : YES
libcap (Linux capabilities system operations) ______________ : YES
libcrypto (cryptographic functions) ________________________ : YES
libyaml (library for parsing and emitting YAML) ____________ : YES
libmnl (library for working with netfilter) ________________ : YES
stacktraces (library for getting stack traces) _____________ : libbacktrace (mmap, threads, data)
Plugins:
apps (monitor processes) ___________________________________ : YES
cgroups (monitor containers and VMs) _______________________ : YES
cgroup-network (associate interfaces to CGROUPS) ___________ : YES
proc (monitor Linux systems) _______________________________ : YES
tc (monitor Linux network QoS) _____________________________ : YES
diskspace (monitor Linux mount points) _____________________ : YES
freebsd (monitor FreeBSD systems) __________________________ : NO
macos (monitor MacOS systems) ______________________________ : NO
windows (monitor Windows systems) __________________________ : NO
statsd (collect custom application metrics) ________________ : YES
timex (check system clock synchronization) _________________ : YES
idlejitter (check system latency and jitter) _______________ : YES
bash (support shell data collection jobs - charts.d) _______ : YES
debugfs (kernel debugging metrics) _________________________ : YES
cups (monitor printers and print jobs) _____________________ : YES
ebpf (monitor system calls) ________________________________ : YES
freeipmi (monitor enterprise server H/W) ___________________ : YES
network-viewer (monitor TCP/UDP IPv4/6 sockets) ____________ : YES
systemd-journal (monitor journal logs) _____________________ : YES
windows-events (monitor Windows events) ____________________ : NO
nfacct (gather netfilter accounting) _______________________ : YES
perf (collect kernel performance events) ___________________ : YES
slabinfo (monitor kernel object caching) ___________________ : YES
Xen ________________________________________________________ : YES
Xen VBD Error Tracking _____________________________________ : NO
Exporters:
AWS Kinesis ________________________________________________ : NO
GCP PubSub _________________________________________________ : NO
MongoDB ____________________________________________________ : YES
Prometheus (OpenMetrics) Exporter __________________________ : YES
Prometheus Remote Write ____________________________________ : YES
Graphite ___________________________________________________ : YES
Graphite HTTP / HTTPS ______________________________________ : YES
JSON _______________________________________________________ : YES
JSON HTTP / HTTPS __________________________________________ : YES
OpenTSDB ___________________________________________________ : YES
OpenTSDB HTTP / HTTPS ______________________________________ : YES
All Metrics API ____________________________________________ : YES
Shell (use metrics in shell scripts) _______________________ : YES
Debug/Developer Features:
Trace All Netdata Allocations (with charts) ________________ : NO
Developer Mode (more runtime checks, slower) _______________ : NO
Runtime Information:
Profile ____________________________________________________ : standalone
Stream Parent (accept data from Children) __________________ : NO
Stream Child (send data to a Parent) _______________________ : NO
Total System Memory ________________________________________ : 134745366528
Available System Memory ____________________________________ : 116383567872Additional info
That last line ("happy to provide logs / run diagnostics") is worth including — it makes maintainers more likely to engage and tells them
you can reproduce on demand. Everything else just consolidates what's already in the description so a triager gets the full picture at a
glance.
Bug description
Follow-up to #23046 / #23047. The driver-580 XML temperature parser issue reported in #23046 is resolved in v2.10.4 — confirmed, thanks.
However, on the same host a separate problem remains: the daemon-managed nvidia_smi collector now delivers GPU metrics only intermittently. The nvidia_smi.gpu_temperature context flaps between N nodes and 0, so GPU data is mostly missing from charts and Cloud.
A standalone debug run collects correctly every time (sudo -u netdata .../go.d.plugin -d -m nvidia_smi -> SET 'temperature' = 32), but the running agent usually exposes nothing (curl -s http://localhost:19999/api/v1/allmetrics | grep -ic nvidia -> 0), even though the go.d.plugin and 'nvidia-smi -q -x -l 5' processes are alive. AMD sensors.gpu hosts are steady, so it's specific to nvidia_smi. Tried restart and loop_mode: no — no change. Env: NVIDIA RTX PRO 6000 Blackwell, driver 580.95.05, netdata v2.10.4, Debian 13.
Expected behavior
The daemon-managed nvidia_smi collector should deliver GPU metrics (temperature, fan, power) reliably on every collection cycle — the same way the standalone debug run does — so the charts and the nvidia_smi.gpu_temperature context stay continuously populated instead of
flapping between N nodes and 0.
Steps to reproduce
sudo -u netdata /usr/libexec/netdata/plugins.d/go.d.plugin -d -m nvidia_smi
-> emits: SET 'temperature' = 32 (plus fan/power/utilization charts)
sudo -u netdata nvidia-smi --query-gpu=temperature.gpu --format=csv,noheader -> 32
for i in 1 2 3 4 5 6; do date +%T; curl -s http://localhost:19999/api/v1/allmetrics | grep -ic nvidia; sleep 10; done
-> mostly 0, only occasionally non-zero (go.d.plugin and 'nvidia-smi -q -x -l 5' are alive the whole time)
Installation method
from git
System info
Netdata build info
Additional info
That last line ("happy to provide logs / run diagnostics") is worth including — it makes maintainers more likely to engage and tells them
you can reproduce on demand. Everything else just consolidates what's already in the description so a triager gets the full picture at a
glance.