Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    node_exporter failing uname collector

    Scheduled Pinned Locked Moved
    Plus 23.01 Development Snapshots (Retired)
    2
    7
    947
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      Apo
      last edited by

      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.

      1 Reply Last reply Reply Quote 1
      • stephenw10S stephenw10 moved this topic from General pfSense Questions on
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

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

        A 1 Reply Last reply Reply Quote 0
        • A
          Apo @stephenw10
          last edited by

          @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).

          1 Reply Last reply Reply Quote 0
          • stephenw10S stephenw10 moved this topic from Off-Topic & Non-Support Discussion on
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

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

            If you unselect meminfo does that stop the error?

            A 1 Reply Last reply Reply Quote 0
            • A
              Apo @stephenw10
              last edited by

              @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.

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

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

                A 1 Reply Last reply Reply Quote 0
                • A
                  Apo @stephenw10
                  last edited by Apo

                  @stephenw10 I have enabled:

                  • boottime
                  • cpu
                  • loadavg
                  • meminfo

                  (disabling meminfo does not help btw)

                  1 Reply Last reply Reply Quote 1
                  • E emmdee referenced this topic on
                  • First post
                    Last post