Problmes after updating Zabbix 4.0.2

[CassiosRPG7]

Hi,

I am migrating from zabbix 3.4 to zabbix 4.0.2 and I have an error when selecting the database, attached screenshots below.

I have reviewed similar errors but in my case I do not see suggestions to remove columns from tables or something like that, I receive suggestions.


Thank you

[Atsushi]

The current database seems to have already been upgraded to the database for zabbix-4.2.0alpha1.
There is no way to automatically return to the database for Zabbix 4.0.2 from this state automatically.

Please upgrade from the database before the upgrade.
If there is no database before the upgrade, please manually return it or consider rebuilding the database for 4.0.2.

[dimir]

Yes, looks like you installed zabbix-4.2.0alpha1. What were the procedures you went through to upgrade zabbix? Did you use Zabbix packages? Which zabbix-release package you have installed now (rpm: rpm -qa | grep zabbix-release; deb: dpkg -l 'zabbix-release*')?

[CassiosRPG7]

Thanks for the answers.

That's right, first I tried to install that version of zabbix, I copied this repository https://github.com/zabbix/zabbix-docker and made a pull of this version: docker-compose_v3_alpine_pgsql_local.yaml which installed zabbix-4.2.0alpha1 but I couldn't use it due to a problem with zabbix-server.

Basically zabbix-server was looking for the postgres container even though I had already edited the zabbix.conf.php with my database configuration, this caused me to have the zabbix-web working with the old information but the zabbix-server couldn't work, that's why I couldn't continue with that installation because I had problems with the docker file.

Then I tried to install zabbix following this guide https://www.zabbix.com/documentation.../debian_ubuntu and I have that new problem, in that case I would like to know how to rebuilding my database to be compatible with zabbix 4.0.2 (any script or something that could fix it).

I am using alpine linux as a base system

[dimir]

If you just drop "content_type" column from "media_type" table you can use it with 4.0.2 . As I understood you use postgres, so you need to connect to your database and perform the following operations:

ALTER TABLE media_type DROP COLUMN content_type CASCADE;
UPDATE dbversion set mandatory=4000000,optional=4000003;

and you should be able to go with 4.0.2 .

[CassiosRPG7]

Hi,

I did what you suggested and it worked, BUT... I have the following errors on the front-end.

help haha

[dimir]

Which frontend version are you running? Please see the footer in frontend, it should say

Zabbix 4.0.2. © 2001–2018, Zabbix SIA

[CassiosRPG7]

Yes, the same one.

[CassiosRPG7]

Hi,

I managed to fix it by returning to a database backup of zabbix version 3.4, then running the script that recommended dimir and then installing zabbix 4.0.2 using docker hub: https://hub.docker.com/u/zabbix/

Thanks for the answers, that's settled.

[pkvsnz]

Hi!

I'm upgrade from 3.4 to 4.0.2 and have fronted problem

And in log - many errors
zabbix_server [29980]: ERROR [file:lld_item.c,line:856] Something impossible has just happened.
29980:20181211:133913.996 backtrace is not available for this platform
zabbix_server [29980]: ERROR [file:lld_item.c,line:856] Something impossible has just happened.
29980:20181211:133913.997 backtrace is not available for this platform