Ad Widget

Collapse

Zabbix Proxy Docker container sqlite3

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • FrK3v
    Junior Member
    • Apr 2018
    • 8

    #1

    Zabbix Proxy Docker container sqlite3

    Hello guys !

    I have a problem with this image zabbix-proxy-sqlite3 present on the docker hub (tag: centos-4.2.4).

    I run the container with the following parameters:

    Instance in the cloud:
    2 vCores and 4Go RAM

    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:
    /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" but the problem is identical with "docker-compose up -d" and "docker-compose restart"

    Do you know why the zabbix_proxy processes use a lot of memory on the restart ?




    Thanks for your help !

    Kévin
    Last edited by FrK3v; 23-07-2019, 18:32.
  • FrK3v
    Junior Member
    • Apr 2018
    • 8

    #2
    I will post an image later.

    Before: https://osu.eu-west-2.outscale.com/k...re_restart.png
    After: https://osu.eu-west-2.outscale.com/k...er_restart.png
    Last edited by FrK3v; 24-07-2019, 09:40.

    Comment

    • FrK3v
      Junior Member
      • Apr 2018
      • 8

      #3

      I'm the only one with this problem?

      Comment

      Working...