Ad Widget

Collapse

schema patch for 64bit systems

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ProTON
    Member
    • Oct 2005
    • 77

    #1

    schema patch for 64bit systems

    I had problems on 64bit systems where values kept hitting maximum double(16,4). This patch solves them.

    I know that Zabbix developers doesn't break schema in bug fix releases, but this definetely has to go into 1.4.

    Chears.
    Attached Files
  • Alexei
    Founder, CEO
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Sep 2004
    • 5654

    #2
    I beliebe there is no need to patch table history. If you want to keep large numbers, use Unsigned 64bit integers instead, they are stored in history_uint.
    Alexei Vladishev
    Creator of Zabbix, Product manager
    New York | Tokyo | Riga
    My Twitter

    Comment

    • Alexei
      Founder, CEO
      Zabbix Certified Trainer
      Zabbix Certified SpecialistZabbix Certified Professional
      • Sep 2004
      • 5654

      #3
      In 1.4 items.prevorgvalue is defined as varchar(255)
      Alexei Vladishev
      Creator of Zabbix, Product manager
      New York | Tokyo | Riga
      My Twitter

      Comment

      • djinn_fr22
        Member
        • Jan 2007
        • 54

        #4
        I got the same problem.
        I got network data reaching high number.

        I tried the solution to store data in integer 64 bit, but there is something else going on.

        When I look in the table history_uint, I got that:

        SELECT h.value, h.clock FROM history_uint h where h.itemid=17866 order by h.clock desc;

        2348257434605, 1170694697
        2348257370663, 1170694666
        2348257304602, 1170694636
        2348257263554, 1170694619

        That is exactly what I got from ifconfig. So it seems to work.
        But when I choose "delta by second", I got:

        48152085762, 1170694817
        44941944659, 1170694789
        40856289719, 1170694759
        122568863315, 1170694726

        There is a bug with delta.

        My item is configured like
        Numeric (Integer 64)
        Delta (speed per second)

        I don't know where that come from.
        I am running 1.1.5 on RHAS 4.4 64bits.

        I am going to try the patch from proton with a float item.

        Comment

        • AdrianS
          Junior Member
          • Mar 2007
          • 12

          #5
          I have probably the same problem - numbers stored "as is" are correct
          2007.Mar.07 12:49:18 63279809413405
          2007.Mar.07 12:48:18 63279682990677
          2007.Mar.07 12:47:18 63279557762021
          2007.Mar.07 12:46:18 63279433388306
          2007.Mar.07 12:45:18 63279313801042
          2007.Mar.07 12:44:19 63279189466125
          2007.Mar.07 12:44:13 63279179207051
          etc.

          When I try to use delta (speed per second) zabbix is getting crazy.
          2007.Mar.07 13:00:18 1055613040735
          2007.Mar.07 12:59:19 1021000914344
          2007.Mar.07 12:58:18 1038015536477
          2007.Mar.07 12:57:18 2965753270572
          2007.Mar.07 12:56:57 1596942917348

          While you can easily check that this numbers should be around
          100000 - 3000000

          It seems that there is something wrong with delta calculation or large numbers in zabbix server routines are stored in wrong manner.
          When I look in database (items) "prevorgvalue" is 999999999999.9999 - but it should be ok since my numbers are smaller then double(16,4) - right?
          Any ideas what can be done to solve this problem? (i'll keep trying on my own )


          update:
          After increasing "prevorgvalue" in "items" to double(24,4) it's better but still not ok.

          ps. tested with 1.1.4 and 1.1.6 (debian builds)

          Regards
          --
          Adrian Siemieniak
          Last edited by AdrianS; 07-03-2007, 14:19.

          Comment

          • medic
            Member
            • Feb 2007
            • 58

            #6
            this is known and fixed in current svn version

            Comment

            Working...