ZABBIX Upgrade 6.0 to 6.2 fail

[guy56]

Hi,

I need your help: after upgraded my zabbix zerver, i have an error message which say 'Zabbix database version does not match current requirements. Your database version: 6000000. Required version: 6020000'

1. I tried to restart only zabbix-server then the server
2. I checked in my /var/log/zabbix/zabbix-server.log --> empty
3. I tried to update dbversion to 6020000 as marked but after that i have a blank page
4. Migrate data from old history tables to new ones

What can i do more?thx

For informations:
OS: DEBIAN 11
MariadDB: 10.9.2-MariaDB-1:10.9.2+maria~deb11
PHP 7.4.30
zabbix-frontend-php est déjà la version la plus récente (1:6.2.1-1+debian11).
zabbix-server-mysql est déjà la version la plus récente (1:6.2.1-1+debian11)

In /etc/zabbix/zabbix_server.conf i checked:
DBUser=root
DBPassword= it's OK
AllowUnsupportedDBVersions=1

[LenR]

You will have to figure out why the zabbix server didn't start. At first startup it will upgrade the database from 6000000 to 6020000. The frontend won't go past that check until you do.

[tim.mooney]

[*]I tried to update dbversion to 6020000 as marked but after that i have a blank page

Never do that. You should change it back to what it was.

As LenR mentioned, the very first time you start a new version of the zabbix-server process, it connects to its database and looks at that database field. So if you install the software for Zabbix 6.2.2 and it starts up and it sees 6000000 in the dbversion field, that's what tells zabbix-server that it needs to perform any necessary database schema changes. Assuming all those schema changes succeed, the last thing it will do is update dbversion to 6020000, to signal that it has successfully finished the necessary schema modifications to your older database, to essentially make the database the correct format for 6.2.x.

The schema changes the server tries to make can fail, but when they do, there's generally some SQL messages in zabbix_server.log that point at some database issue that needs to be fixed before the schema upgrade could be retried.