node_exporter failing uname collector

Apo

I wanted to try node_exporter to monitor my pfsense instance. So far it's been working, but I get flooded with those logs:

2023-01-25 09:46:01.770888+01:00	node_exporter	4152	ts=2023-01-25T08:46:01.770Z caller=collector.go:169 level=error msg="collector failed" name=uname duration_seconds=4.4184e-05 err="cannot allocate memory"

The machine reports 11GB of free RAM so this shouldn't be an issue.

stephenw10

How is it configured? How did you install it? What version?

Apo

@stephenw10 I installed it through Package Manager, package version 0.18.1_3 (node_exporter 1.3.1_6). Running on pfSense 23.01-BETA (amd64).

stephenw10

Ah, OK. How do you have it configured, with the default options?

If you unselect meminfo does that stop the error?

Apo

@stephenw10 I just have a minimal set of collectors enabled since I'm also using telegraf to export more pfsense specific metrics. I can stop the error by adding --no-collector.uname to the extra flags. But would be nice to have the uname metrics too.

stephenw10

But which collectors do you have enabled? To reproduce this we need the configuration details.

Apo

@stephenw10 I have enabled:

boottime
cpu
loadavg
meminfo

(disabling meminfo does not help btw)