Ad Widget

Collapse

Zabbix 3.2.0 3 digit clipping

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • nail
    Member
    • Jun 2012
    • 32

    #1

    Zabbix 3.2.0 3 digit clipping

    Hi all!

    After updating server from 3.0.0 to 3.2.0 some(around 60%) of 'database monitor' values only have 3 digits in latest data instead of their usual values (ex. 147 instead of 1474275391)
    Changing value type from unsigned to float did nothing.
    Tried to create new item - same results.
    Doing the same request using isql returns correct result.

    Probably it's database corruption, but not sure where to look.
  • nail
    Member
    • Jun 2012
    • 32

    #2
    tried another database check, using "Type of information: Text"
    isql output: 2016-09-19 05:42:49
    in Zabbix: 2016-09-19 05:4

    Comment

    • nail
      Member
      • Jun 2012
      • 32

      #3
      Debug=4 got me this:
      Code:
       64292:20160919:130638.106 In activate_host() hostid:10121 itemid:56048 type:11
       64462:20160919:130638.119 query [txnlev:1] [insert into history (itemid,clock,ns,value) values (56048,1474279598,104855809,147.000000);
       64462:20160919:130638.120 In zbx_vc_add_value() itemid:56048 value_type:0 timestamp:1474279598.104855809
      upd:
      Code:
      SELECT UNIX_TIMESTAMP()
      returns correct value
      but
      Code:
      SELECT MAX(t.ts) FROM db1.table1 t
      limits to 3 digits


      Code:
      CAST(t.ts AS SIGNED)
      this somehow worked.

      Still it's quite interesting that new Zabbix started cropping results from 'INT' MySQL fields to just 3 digits.
      tested on BIGINT - works fine without CAST.
      Is this possible a bug?

      https://support.zabbix.com/browse/ZBX-11213 - more info on ODBC problem here
      Last edited by nail; 19-09-2016, 14:49. Reason: found workaround + link

      Comment

      • e-coder
        Junior Member
        • Sep 2016
        • 8

        #4
        Can Confirm this Bug.

        Here SQL Values are cut down to 3 Digits.

        Comment

        • glebs.ivanovskis
          Senior Member
          • Jul 2015
          • 237

          #5
          Known issue, please follow ZBX-11213.

          Comment

          Working...