upgrade from 3.4 to 4.0 failure

[tealsteam]

Hi All,

Thanks to everyone for your help over the years, this is my first time posting here,

I have issues updating from 3.4 to 4.0


OS: Centos 7,
Build: Zabbix-server-mysql 3.4.5

I tried upgrading to 4.0, Following the upgrade guide for packages on redhat/centos, I put in the new rpm for 4.0 did the upgrade and it told me it couldn't find 3.4.15...

I uninstalled the rpm, reinstalled the 3.4 rpm upgraded to 3.4.15, i have switched back to the 4.0 rpm tried to upgrade now its telling me i am up to date.


[root@dragonet ~]# rpm -Uvh https://repo.zabbix.com/zabbix/4.0/r...el7.noarch.rpm
Retrieving https://repo.zabbix.com/zabbix/4.0/r...el7.noarch.rpm
Preparing... ################################# [100%]
package zabbix-release-4.0-1.el7.noarch is already installed

[root@dragonet ~]# sudo yum upgrade zabbix-server-mysql-4.0.0
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirror.freethought-internet.co.uk
* epel: mirror.neostrada.nl
* extras: mirror.econdc.com
* updates: mirror.econdc.com
No Match for argument: zabbix-server-mysql-4.0.0
No package zabbix-server-mysql-4.0.0 available.
No packages marked for update

[root@dragonet ~]# sudo yum upgrade zabbix-server-mysql
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirror.freethought-internet.co.uk
* epel: ams.edge.kernel.org
* extras: mirror.econdc.com
* updates: mirror.econdc.com
No packages marked for update

[root@dragonet ~]# rpm -qa | grep zabbix
zabbix-agent-3.4.15-1.el7.x86_64
zabbix-server-mysql-3.4.15-1.el7.x86_64
zabbix-release-4.0-1.el7.noarch
zabbix-web-3.4.15-1.el7.noarch
zabbix-web-mysql-3.4.15-1.el7.noarch

[tealsteam]

I have resolved this issue doing "yum clean all"

Although, i have now been sat with "The frontend does not match Zabbix database. Current database version (mandatory/optional): 3050001/3050001. Required mandatory version: 4000000. Contact your system administrator." for about an hour

logs are showing the below over and over,

Dec 6 16:16:53 dragonet systemd: zabbix-server.service: control process exited, code=exited status=1
Dec 6 16:16:53 dragonet systemd: Unit zabbix-server.service entered failed state.
Dec 6 16:16:53 dragonet systemd: zabbix-server.service failed.
Dec 6 16:17:03 dragonet systemd: zabbix-server.service holdoff time over, scheduling restart.
Dec 6 16:17:03 dragonet systemd: Stopped Zabbix Server.
Dec 6 16:17:03 dragonet systemd: Starting Zabbix Server...
Dec 6 16:17:03 dragonet systemd: PID file /run/zabbix/zabbix_server.pid not readable (yet?) after start.
Dec 6 16:17:03 dragonet systemd: Started Zabbix Server.
Dec 6 16:17:03 dragonet systemd: zabbix-server.service: main process exited, code=exited, status=1/FAILURE
Dec 6 16:17:03 dragonet kill: Usage:
Dec 6 16:17:03 dragonet kill: kill [options] <pid|name> [...]
Dec 6 16:17:03 dragonet kill: Options:
Dec 6 16:17:03 dragonet kill: -a, --all do not restrict the name-to-pid conversion to processes
Dec 6 16:17:03 dragonet kill: with the same uid as the present process
Dec 6 16:17:03 dragonet kill: -s, --signal <sig> send specified signal
Dec 6 16:17:03 dragonet kill: -q, --queue <sig> use sigqueue(2) rather than kill(2)
Dec 6 16:17:03 dragonet kill: -p, --pid print pids without signaling them
Dec 6 16:17:03 dragonet kill: -l, --list [=<signal>] list signal names, or convert one to a name
Dec 6 16:17:03 dragonet kill: -L, --table list signal names and numbers
Dec 6 16:17:03 dragonet kill: -h, --help display this help and exit
Dec 6 16:17:03 dragonet kill: -V, --version output version information and exit
Dec 6 16:17:03 dragonet kill: For more details see kill(1).
Dec 6 16:17:03 dragonet systemd: zabbix-server.service: control process exited, code=exited status=1
Dec 6 16:17:03 dragonet systemd: Unit zabbix-server.service entered failed state.
Dec 6 16:17:03 dragonet systemd: zabbix-server.service failed.

[tealsteam]

Please close my useles thread, it has already been answered here, just took too long for me to find,

https://www.zabbix.com/forum/zabbix-troubleshooting-and-problems/366568-upgrade-problems-and-troubleshooting-from-3-4-15-to-4-0-repository-and-database