Ad Widget

Collapse

Do not upgrade to Zabbix 6.0.15

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Atsushi
    Senior Member
    • Aug 2013
    • 2028

    #1

    Do not upgrade to Zabbix 6.0.15

    I noticed a report from a Japanese user and tried it, and there is a problem that the value of the item cannot be obtained in 6.0.15.
    I've also posted a bug report.

  • BiMW
    Junior Member
    • Jun 2018
    • 23

    #2
    to late

    Comment

    • Spoonman
      Member
      • Aug 2013
      • 45

      #3
      Too late indeed, I'm already running 6.0.15......

      Comment

      • max_bz
        Junior Member
        Zabbix Certified SpecialistZabbix Certified Professional
        • Mar 2023
        • 17

        #4
        Originally posted by Spoonman
        Too late indeed, I'm already running 6.0.15......
        You can downgrade back to 6.0.14
        Changing minor versions is possible without compatibility problems, as far as I know.
        Code:
        sudo yum -y downgrade zabbix-*[6.0.14-release1.el9]
        This solves the problem, the metrics reappear.

        The error occurs in metrics that use the "changes per second" preprocessing rule.
        I think version 6.0.16 with a fix for this bug will be quite soon.​

        Comment


        • jekahawk
          jekahawk commented
          Editing a comment
          On Ubuntu apt-cache does not allow you to rollback to a previous version of the package. There are no previous packages in the cache. Or is there any solution for it in Ubuntu?
      • markuman
        Junior Member
        • Mar 2023
        • 5

        #5
        On Ubuntu apt-cache does not allow you to rollback to a previous version of the package. There are no previous packages in the cache. Or is there any solution for it in Ubuntu?
        Theoretically it would be possible with `sudo apt-get install zabbix-server-mysql=6.0.14`, but unfortunately, their repo software contains only the latest version: See https://support.zabbix.com/browse/ZBX-19947​

        Theoretically you can do

        Code:
        sudo apt download --print-uris zabbix-server-mysql # change the minor version and wget it
        sudo systemctl stop zabbix-server
        sudo apt remove zabbix-server-mysql
        sudo dpkg -i zabbix-server-mysql_6.0.14-1+ubuntu22.04_arm64.debzabbix-server-mysql_6.0.14
        sudo systemctl start zabbix-server
        Last edited by markuman; 04-04-2023, 21:21.

        Comment

        • nikira
          Junior Member
          • Jul 2021
          • 2

          #6
          Also the interface speed monitoring in 6.0.15 doesn't work, even after I clean install zabbix 6.0.15 doesn't monitor its own interfaces either.

          Comment

          • lizza
            Junior Member
            • Apr 2023
            • 1

            #7
            You can downgrade back to 6.0.14. Changing minor versions is possible without compatibility problems.​

            Comment

            • georgeMyName
              Junior Member
              • Oct 2020
              • 13

              #8
              HI, how can I downgrade on Debian please? I am also affected. Do we know when 6.0.16 will be released?thx

              Comment

              • georgeMyName
                Junior Member
                • Oct 2020
                • 13

                #9
                I will reply to my post . I was able to downgrade by running:
                wget http://repo.zabbix.com/zabbix/6.0/de...an11_amd64.deb
                dpkg -i zabbix-server-mysql_6.0.14-1+debian11_amd64.deb
                apt update
                systemctl restart zabbix-server​

                When is planned release of 6.0.16 ?

                Comment

                • Atsushi
                  Senior Member
                  • Aug 2013
                  • 2028

                  #10
                  6.0.16 has been released. Please try to see if that solves the problem.
                  Explore the list of new features and improvements for every Zabbix release.

                  Comment

                  • ncrandell
                    Junior Member
                    • Apr 2023
                    • 1

                    #11
                    Upgrading to 6.0.16 solved this issue for me.

                    Comment

                    • georgeMyName
                      Junior Member
                      • Oct 2020
                      • 13

                      #12
                      Also, issue reslved by new version.

                      Comment

                      Working...