Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-25429

problems with importing metrics with use of trapper items and proxy group

XMLWordPrintable

    • Icon: Problem report Problem report
    • Resolution: Unresolved
    • Icon: Minor Minor
    • 7.0.6rc1, 7.2.0alpha2 (master)
    • 7.0.4
    • Proxy (P), Server (S)
    • None
    • Zabbix Server 7.0.4 on Oracle 8.10 (nginx + postgresql 15), 4x 7.0.4 proxies on CentOS9 and 4x 7.0.4 Agents on CentOS9
    • S24-W44/45

      Hello Team,
      Steps to reproduce:
      0. configure whole "backend", create proxy group, add proxies etc...
      1. After configuring Zabbix "backend" add 4 new hosts with use of template "Linux by zabbix agent"
      2. While creating those new hosts assign proxy group as "monitored by"
      3. after creating create new Zabbix trapper item on one of hosts, copy that item to rest of hosts
      4. create txt file with correct pattern, my file looks like that:

      agent5.local this.is.test.key 1729229100 6722345
      agent5.local this.is.test.key 1729229100 6722345
      agent5.local this.is.test.key 1729229100 6722345
      agent5.local this.is.test.item.two 1729229100 6722345
      agent4.local this.is.test.item.two 1729229100 6722345
      agent3.local this.is.test.item.two 1729229100 6722345
      agent2.local this.is.test.item.two 1729229100 6722345

      5. try to upload that file using zabbix_sender (zabbix_sender is being ran from Zabbix Server machine) with: 

      zabbix_sender -c /etc/zabbix/zabbix_agentd.conf -z 127.0.0.1 -T -i file.txt

      In a result we would get:

      Response from "192.168.99.59:10051": "processed: 95; failed: 155; total: 250; seconds spent: 0.001844" 
      Response from "192.168.99.57:10051": "processed: 64; failed: 186; total: 250; seconds spent: 0.001066" 
      Response from "192.168.99.57:10051": "processed: 65; failed: 185; total: 250; seconds spent: 0.001011" 
      Response from "192.168.99.57:10051": "processed: 65; failed: 185; total: 250; seconds spent: 0.000993" 
      Response from "192.168.99.60:10051": "processed: 97; failed: 153; total: 250; seconds spent: 0.001850"

      And inside zabbix server log:

      1976:20241022:100117.396 skipped 1 duplicates 1976:20241022:100117.397 [Z3008] query failed due to primary key constraint: [0] PGRES_FATAL_ERROR:ERROR: duplicate key value violates unique constraint "history_uint_pkey" DETAIL: Key (itemid, clock, ns)=(48068, 1729229100, 241) already exists.
      1976:20241022:100117.397 skipped 1 duplicates 1976:20241022:100117.398 [Z3008] query failed due to primary key constraint: [0] PGRES_FATAL_ERROR:ERROR: duplicate key value violates unique constraint "history_uint_pkey" DETAIL: Key (itemid, clock, ns)=(48068, 1729229100, 244) already exists.
      1976:20241022:100117.398 skipped 1 duplicates 1976:20241022:100117.398 [Z3008] query failed due to primary key constraint: [0] PGRES_FATAL_ERROR:ERROR: duplicate key value violates unique constraint "history_uint_pkey" DETAIL: Key (itemid, clock, ns)=(48068, 1729229100, 246) already exists.

       tested on 7.0.4 - if there is a need for more details, I can provide them

            wiper Andris Zeila
            tgrzechulski Tomasz Grzechulski
            Team A
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: