Unable to upgrade raspberry pi 4 from 6.4 to 7.0

XMLWordPrintable

    • Type: Incident report
    • Resolution: Commercial support required
    • Priority: Trivial
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Environment:
      Current
      hw: raspberrypi
      os: bullseys (11)
      sw:6.4
      DB: postgress
      fe:apache

      Steps to reproduce:

      I did a fresh install of bookwork (12) raspberrypi lite (no desktop) on a pi 4.  I had to move to bookworm as there is no binary release available for bullseye (11) for Zabbix 7.

      I completed all of the step here up to 2c

      I did NOT run the database initialization process and instead restored my backup

      psql -U zabbix -d zabbix < /backup/usr/local/backup/20240731-120020.sql

      I skipped this step

      zcat /usr/share/zabbix-sql-scripts/postgresql/server.sql.gz | sudo -u zabbix psql zabbix

      After completing the remaining steps I navigated to the zabbix in a browser and entered the requested information to connect to the database. The UI complains that the database does not meet the minimal requirements (7.0). 

      Result:
      Unable to migrate from 6.4 on Bullseye to 7.0 on bookworm.

       

      $ psql -U zabbix
      Password for user zabbix:
      psql (15.7 (Debian 15.7-0+deb12u1))
      Type "help" for help.
      zabbix=> \dt
      zabbix=> select * from dbversion
      zabbix-> ;
       dbversionid | mandatory | optional
      ------------------------------
                 1 |   6040000 |  6040026
      (1 row)
      zabbix=> \dt
      zabbix=> \dt
      zabbix=> select * from dbversion
      ;
       dbversionid | mandatory | optional
      ------------------------------
                 1 |   6040000 |  6040026
      

       

      Expected:

      I'm likely not doing this right and I'm not sure how to upgrade. The binary packages are not available on bullseye so I can upgrade from 6.4 to 7.0 on bullseye. I need a way of migrating the schema in 6.4 to 7.0. I assume that's what this process does. 

      https://www.zabbix.com/documentation/current/en/manual/installation/upgrade/packages/debian_ubuntu

      but when I look at the packages installed on bookworm, a few of them are not version 7.0

      $ dpkg -l zabbix*
      Desired=Unknown/Install/Remove/Purge/Hold
      
      Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend   / Err?=(none)/Reinst-required (Status,Err: uppercase=bad)   / Name Version Architecture Description
      +++=========================================================================================================================
      ii zabbix-agent 1:6.0.14+dfsg-1+b1 arm64 network monitoring solution - agent
      ii zabbix-apache-conf 1:7.0.2-1+debian12 all Zabbix network monitoring solution - apache configuration for front-end
      ii zabbix-frontend-php 1:7.0.2-1+debian12 all Zabbix network monitoring solution - PHP front-end
      un zabbix-nginx-conf <none> <none> (no description available)
      un zabbix-proxy-mysql <none> <none> (no description available)
      un zabbix-proxy-pgsql <none> <none> (no description available)
      un zabbix-proxy-sqlite3 <none> <none> (no description available)
      ii zabbix-release 1:7.0-2+debian12 all Zabbix official repository configuration
      un zabbix-sender <none> <none> (no description available)
      un zabbix-server-mysql <none> <none> (no description available)
      ii zabbix-server-pgsql 1:6.0.14+dfsg-1+b1 arm64 network monitoring solution - server (using PostgreSQL)
      ii zabbix-sql-scripts 1:7.0.2-1+debian12 all Zabbix network monitoring solution - sql-scripts    

      I'm not sure if that's expected or not. It's not clear to me when/how the schema get updated in postgress.

      I've also asked in the forums if anyone else as successfully upgraded to 7.0 from 6.4 on debian.

            Assignee:
            Zabbix Support Team
            Reporter:
            John Wheeler
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: