Upgrade zabbix server from 4.4.1 to 4.4.5

[GeorgeKup]

Zabbix server and database are on different servers. When upgrading the zabbix server according to instructions from version 4.4.1 to version 4.4.5 (stopping the zabbix server, updating packages, starting the zabbix server), the database should be updated, which should be visible in / var / log / zabbix / zabbix_server. log. However, in the specified log (possibly due to the large number of entries), I did not notice entries about updating the database. At the same time, version 4.4.5 is displayed in the web interface and data continues to flow into the database. The question is - when switching from version 4.4.1 to version 4.4.5, should the database be updated or is it updated in case of more serious updates, for example, when switching from 4.2 to 4.4? If so, is it possible to somehow check with a command or something else that the corresponding database structure corresponds to the zabbix server and web interface 4.4.5.

[Atsushi]

From 4.4.1 to 4.4.5, there is no change in the structure of the database.
Since the database stores the database for which version of Zabbix, if the web front end is of a different major version, it will fail and cannot be used. Different major versions refer to combinations such as 4.2 and 4.4. 4.4.1 and 4.4.5 have the same 4.4 major version.

[tnyabasa]

I just wanted to check, I upgraded my Zabbix from 4.41 to 4.4.8 but when I login to my GUI it is still showing 4.4.1. How do I go about updating my Frontend

[root@ctczabbix ~]# zabbix_server --version

zabbix_server (Zabbix) 4.4.8

Revision 3d7663fd7c 27 April 2020, compilation time: Apr 27 2020 10:22:10




Copyright (C) 2020 Zabbix SIA

License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl.html>.

This is free software: you are free to change and redistribute it according to

the license. There is NO WARRANTY, to the extent permitted by law.




This product includes software developed by the OpenSSL Project

for use in the OpenSSL Toolkit (http://www.openssl.org/).




Compiled with OpenSSL 1.0.1e-fips 11 Feb 2013

Running with OpenSSL 1.0.1e-fips 11 Feb 2013

[Atsushi]

If you are building your environment with packages, make sure that the packages for web frontend are updated.
If the package is updated, try restarting the web server or PHP-FPM.