Uploaded image for project: 'ZABBIX FEATURE REQUESTS'
  1. ZABBIX FEATURE REQUESTS
  2. ZBXNEXT-5334

Huge memory use on proxy docker container restart

    XMLWordPrintable

Details

    • Change Request
    • Status: Closed
    • Trivial
    • Resolution: Duplicate
    • 4.2.4
    • None
    • Proxy (P)
    • Centos7

    Description

      Hello,

      When you create a container using this image: zabbix-proxy-sqlite3:centos-4.2.4 and you want to restart the container. Each process of the zabbix_proxy use 1% of the memory and we can reach 6Go used whereas on the fist launch it use 2Go approximately.

      Environnement:

      Docker:
      Client:
      Version: 18.06.1-ce
      API version: 1.38
      Go version: go1.10.3
      Git commit: e68fc7a
      Built: Tue Aug 21 17:23:03 2018
      OS/Arch: linux/amd64
      Experimental: false

      Server:
      Engine:
      Version: 18.06.1-ce
      API version: 1.38 (minimum version 1.12)
      Go version: go1.10.3
      Git commit: e68fc7a
      Built: Tue Aug 21 17:25:29 2018
      OS/Arch: linux/amd64
      Experimental: false

      Environnement variables (/etc/zabbix/docker/env.list):

      ZBX_HOSTNAME=zabbix-proxy
      ZBX_SERVER_HOST=XXX.XX.XX.XXX
      ZBX_TIMEOUT=30
      ZBX_CACHESIZE=1G
      ZBX_SERVER_PORT=10051
      ZBX_HISTORYCACHESIZE=300M
      ZBX_HISTORYINDEXCACHESIZE=1G
      ZBX_STARTDBSYNCERS=10
      ZBX_STARTDISCOVERERS=10
      ZBX_CONFIGFREQUENCY=1200
      ZBX_LOGSLOWQUERIES=3000
      ZBX_STARTTRAPPERS=20
      ZBX_STARTPOLLERS=10
      ZBX_STARTPOLLERSUNREACHABLE=10
      ZBX_STARTPINGERS=10
      ZBX_TLSCONNECT=psk
      ZBX_TLSPSKFILE=zabbix_proxy.psk
      ZBX_TLSPSKIDENTITY=PSK

      Command to start the container:

      Unable to find source-code formatter for language: bash. Available languages are: actionscript, html, java, javascript, none, sql, xhtml, xml/usr/bin/docker run --log-driver syslog --log-opt syslog-address=udp://127.0.0.1:514 --log-opt tag={{.DaemonName}}-{{.Name}}-{{.ID}} --name zabbix-proxy --mount type=tmpfs,destination=/var/lib/database,tmpfs-mode=777 --env-file /etc/zabbix/docker/env.list -p 10051:10051 -v /etc/zabbix/docker:/var/lib/zabbix/enc zabbix/zabbix-proxy-sqlite3:centos-4.2.4

      When I want to restart the container with the command below:
      docker restart zabbix-proxy

      The zabbix_proxy processes use too much memory and the container is OOM kill (approx: 4Go used instead of 2Go on the first launch)

      The problem doesn't appear when I use the option "--rm" in the docker run command line.

      I have also try with docker-compose. No problem with the "docker-compose up -d" and the "docker-compose down" and  "docker-compose up -d" but the problem is identical with "docker-compose up -d" and "docker-compose restart".

      I think the zabbix_proxy doesn't clean correctly its memory.

      Thanks

      Attachments

        Issue Links

          Activity

            People

              wiper Andris Zeila
              OSC_monitoring Outscale Monitoring Team
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: