Ad Widget

Collapse

the 3.2 bad history

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ghislain
    Senior Member
    • Jun 2005
    • 160

    #1

    the 3.2 bad history

    hi,

    we were running a happy 3.0 version and as upgrades went on, someone mistakenly updated to 3.2. Since then this is a real nigthmare for our install, trigger stay on even if all the data and the trigger calculation show it is off, delta calculated value do not update anymore even if logs show that the server got everything right and do not give any errors... the system is therefor completly unusable as data are not correct and triggers are false everywhere I tried to reinstall a fresh install and the same problem showed up just importing templates and host.

    I tried to return to 3.0 but i cannot import the templates as it refuse the 3.2 ones so i am struck on 3.2.

    Anyone encountered similar problems and how to solve them ?


    regards,
    Ghislain.
    Regards,
    Ghislain.
  • gbiondi
    Member
    • Nov 2016
    • 75

    #2
    Hi,

    I run 3.2 version and have 'some little problem' but I'm fresh zabbix-user for test.. in production enviroment use opennms..
    My question is: "V3.0 is more stable from last version V3.2 ? "

    All the best.

    GB

    Comment

    • kloczek
      Senior Member
      • Jun 2006
      • 1771

      #3
      Originally posted by gbiondi
      My question is: "V3.0 is more stable from last version V3.2 ? "
      Both are stable. Both are without any known major issues.
      http://uk.linkedin.com/pub/tomasz-k%...zko/6/940/430/
      https://kloczek.wordpress.com/
      zapish - Zabbix API SHell binding https://github.com/kloczek/zapish
      My zabbix templates https://github.com/kloczek/zabbix-templates

      Comment

      • ghislain
        Senior Member
        • Jun 2005
        • 160

        #4
        well i would say 3.0 has never let me down and work very well. For 3.2 perhaps this is the fact this was an upgrade but we have a lot of issues on all metric that are based on delta not recorded "as is".
        Regards,
        Ghislain.

        Comment

        • Atsushi
          Senior Member
          • Aug 2013
          • 2028

          #5
          The history of events that occurred is recorded.

          Please do the following operation.

          1. Monitoring -> Problem
          2. Select "History" at Show
          3. Press "Apply" button
          4. Select history renge (7d, 14d, 1m...)

          Comment

          • ghislain
            Senior Member
            • Jun 2005
            • 160

            #6
            i dont know what you mean, this post is about issues in 3.2 on triggers that do not ends even when data are ok and items that fails because they are using delta and not "as is" storage. Issues i had not in 3.0.

            This is still going on for me. The fantom triggers is under control as i found on the net a sql request that seems to correct it but still my delta per second items are not working correctly.

            Still not been able to fix it. The problem is

            trapper, delta per second int item ( network BP)
            i send the data, sent ok 0 fail
            in the server log i see the data arriving and no error.

            The non delta are ok. The delta items sent this way are not seeing any new data.

            regards,
            Ghislain.
            Regards,
            Ghislain.

            Comment

            • ghislain
              Senior Member
              • Jun 2005
              • 160

              #7
              3.2.2 corrected my issues i am back to 3.0 goodness
              Regards,
              Ghislain.

              Comment

              Working...