zabbix-agent get wrong memory values in Linux Containers

XMLWordPrintable

    • Type: Problem report
    • Resolution: Won't fix
    • Priority: Trivial
    • 5.2 (plan)
    • Affects Version/s: 4.0.24, 5.0.3, 5.2 (plan)
    • Component/s: Agent (G)
    • None
    • Environment:
      Linux Container on proxmox
    • Sprint 68 (Sep 2020), Sprint 69 (Oct 2020)
    • 3

      The the zabbix-agent get the wrong memory values in a Linux Container which is limited with cgroup.
      It seems that the zabbix-agent report the memory values of the host system and not from the container. So it is useless for triggers.
      top in the container shows the correct values.
      also /proc/meminfo shows the correct values.

      A Simple workaround is to detect if you are in a lcx-container (/proc/1/environ) and do not use this values in the trigger.

            Assignee:
            Michael Veksler
            Reporter:
            Falk Hackenberger
            Team C
            Votes:
            11 Vote for this issue
            Watchers:
            19 Start watching this issue

              Created:
              Updated:
              Resolved: