zabbix-frontend-php update error

[radicsf]

Hello,

I am using zabbix in debian server:

x@y:~$ cat /etc/debian_version
8.9

x@y:~$ uname -a
Linux tedej-zbx 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux

Zabbix version is 3.4.3

x@y:~# zabbix_server --version
zabbix_server (Zabbix) 3.4.3
Revision 73588 17 October 2017, compilation time: Oct 17 2017 21:05:48

Today I upgraded the packages but apt upgrade gives me an error when trying to upgrade zabbix-frontend-php:

radicsf@tedej-zbx:~$ sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up zabbix-frontend-php (1:3.4.3-1+jessie) ...
/var/lib/dpkg/info/zabbix-frontend-php.postinst: 11: /var/lib/dpkg/info/zabbix-f                                                                                                                                   rontend-php.postinst: Syntax error: "then" unexpected (expecting "done")
dpkg: error processing package zabbix-frontend-php (--configure):
 subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
 zabbix-frontend-php
E: Sub-process /usr/bin/dpkg returned an error code (1)

Can I do something about this problem?

[denilsongv2]

I had the same problem

When accessing the web interface, the following error message is displayed:



When accessing again the error does not appear, but a display error occurs in the interface:



Can anyone help?

[Atsushi]

Hi denilsongv2,

The first database error may not have been processed by the database upgrade of the Zabbix server.
Depending on the version, the database upgrade process may take time.
You can not access from the new version of the Web frontend until the upgrade process is complete.

The display may be resolved by clearing the browser's cache.

[denilsongv2]

Solved problem

Hi Atsushi,

Your tip: "The display may be resolved by clearing the browser's cache." it worked out.

Thank you very much! Restoring backup was becoming the only option