No mem data on pfsense

[darox]

I'm running telegraf on my pfsense to query data and send it to an influxdb, but for some reason the mem data is not available in influxdb.

Is this a known bug or is mem not supported on pfsense?

[darox]

Log output:

2018-02-04T18:49:00Z E! Error in plugin [inputs.netstat]: error getting net connections info: exec: "lsof": executable file not found in $PATH
2018-02-04T18:49:00Z E! Error in plugin [inputs.mem]: error getting virtual memory info: cannot allocate memory

[danielnelson]

This should work on freebsd, though I do not have a pfsense machine currently. Perhaps you can increase the amount of memory available by modifying a system setting? You might be able to get a better answer at the InfluxData Community site or from the pfsense community.

[W0CHP]

FYI @danielnelson I am able to reproduce this issue on both a pristine installation of both FreeBSD-11.1-p8-RELEASE and pfSense-2.4.3 (11.1-p7-RELEASE). Both servers possess 4GB RAM.

Telegraph 1.4x and 1.3x on these machines do not exhibit this plugin [inputs.mem] issue, oddly.

[darox]

So the problem is, that Telegraf is running on an old version?

[W0CHP]

@darox I am not sure what is causing the issue.

Telegraf 1.5x on 2x amd64 FreeBSD-11.1-RELEASE machines exhibit this error getting virtual memory info: cannot allocate memory issue; yielding no memory data written to InfluxDB.

Telegraf 1.4x and 1.3x on the same 2 machines, do not exhibit this issue; and I can query memory data points just fine.

[danielnelson]

Can you test with the latest 1.6 release candidate?

https://community.influxdata.com/t/telegraf-v1-6-0-rc2/4601

[W0CHP]

@danielnelson Finally got 1.6.0-rc3 built.

Unfortunately I am still seeing the same issues on two machines (one is a pristine installation):

[2.4.3-RELEASE][root@foo]/root: 2018-04-09T21:54:16Z I! Starting Telegraf v1.6.0-rc3
2018-04-09T21:54:16Z I! Loaded outputs: influxdb
2018-04-09T21:54:16Z I! Loaded inputs: inputs.cpu inputs.diskio inputs.mem inputs.pf inputs.swap inputs.system inputs.disk inputs.kernel inputs.net inputs.processes
2018-04-09T21:54:16Z I! Tags enabled: host=redacted
2018-04-09T21:54:16Z I! Agent Config: Interval:10s, Quiet:false, Hostname:"foo", Flush Interval:10s 
2018-04-09T21:54:20Z E! Error in plugin [inputs.mem]: error getting virtual memory info: cannot allocate memory
2018-04-09T21:54:30Z E! Error in plugin [inputs.mem]: error getting virtual memory info: cannot allocate memory

As a result, no [inputs.mem] plugin/input measurements are being written to InfluxDB.

[danielnelson]

Since you are setup to compile, can you try running this program:

package main

import (
        "fmt"

        "github.com/shirou/gopsutil/mem"
)

func main() {
        stats, err := mem.VirtualMemory()
        if err != nil {
                fmt.Println(err)
        }
        fmt.Println(stats)
}

Just save it to your telegraf directory as mem.go and run with go run mem.go. I expect it will print the same error but this should be a good minimal program so we can open a bug report with gopsutil.

[danielnelson]

Actually, digging deeper I wonder if this could have been fixed in golang.org/x/sys/. Can you first try this change to the Godeps file:

diff --git a/Godeps b/Godeps
index 7c504a0b..0715fbd7 100644
--- a/Godeps
+++ b/Godeps
@@ -84,7 +84,7 @@ github.com/yuin/gopher-lua 66c871e454fcf10251c61bf8eff02d0978cae75a
 github.com/zensqlmonitor/go-mssqldb ffe5510c6fa5e15e6d983210ab501c815b56b363
 golang.org/x/crypto dc137beb6cce2043eb6b5f223ab8bf51c32459f4
 golang.org/x/net f2499483f923065a842d38eb4c7f1927e6fc6e6d
-golang.org/x/sys 739734461d1c916b6c72a63d7efda2b27edb369f
+golang.org/x/sys 76c138986e66b22cbf82122ac886457fb5226957
 golang.org/x/text 506f9d5c962f284575e88337e7d9296d27e729d3
 gopkg.in/asn1-ber.v1 4e86f4367175e39f69d9358a5f17b4dda270378d
 gopkg.in/fatih/pool.v2 6e328e67893eb46323ad06f0e92cb9536babbabc

After you change this run:

gdm restore
make telegraf

[W0CHP]

@danielnelson Cool that's a good idea. Here's the output:

[root@foo] telegraf-1.6.0-rc3/src/github.com/influxdata/telegraf]# go run mem.go
cannot allocate memory
<nil>