Upgrade Zabbix server 6.2.4 to 6.2.5

[brontocore]

For those of you who try to upgrade zabbix server installed on ubuntu 22.04.1 from jammy repo, you might end up with a log message like : [Z3005] query failed: [1419] You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable) [create trigger hosts_name_upper_insert
before insert on hosts for each row set new.name_upper=upper(new.name)] . In my VMWare lab, I tried to set the variable with no luck. Finally gave DBA admin rights to the zabbix database account and the migration worked. Removed the DBA admin right afterwards.
For the dev team: after this error line, the server enter in an endless loop trying to upgrade the database.
Hope this can help

[berthold]

Hi,

after updating proxy from 6.2.4 to 6.2.5 in the proxy log the following appears multiple times:

received configuration data from server at "--------- IP --------", datalen 85890
[Z3005] query failed: [1054] Unknown column 'regexpid' in 'field list' [update hstgrp set regexpid=concat('#',groupid) where groupid=5]
failed to update local proxy configuration copy: database error

The following zabbix packages are installed:
zabbix-agent2/unbekannt,now 1:6.2.5-1+debian11 amd64 [installiert]
zabbix-proxy-mysql/unbekannt,now 1:6.2.5-1+debian11 amd64 [installiert]
zabbix-release/unbekannt,now 1:6.2-4+debian11 all [installiert]

[derli1988]

I'm also having the same issue.

[Markku]

The Zabbix 6.2.5 upgrade notes in https://www.zabbix.com/documentation...rade_notes_625 says:

This version has the following server-proxy compatibility issues:

• Zabbix server 6.2.5 will not work with a Zabbix proxy below/above 6.2.5;
• Zabbix proxy 6.2.5 will not work with a Zabbix server below/above 6.2.5.

The latest version is 6.2.6.

Markku

[Markku]

And this response was for the berthold issue

[derli1988]

Here's how I fixed the issue

I've added these 3 lines into MySQL initiation file

disable_log_bin
log_bin_trust_function_creators=1
skip-log-bin

I then restart mysql, and then zabbix-proxy

[jomorton]

I'm fairly new to zabbix, created a new proxy yesterday and its updated to latest but our server was an older version, I'm getting repettitve errors that the local proxy configuration can't be updated.

326412:20221215:014625.850 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR: column "regexpid" of relation "hstgrp" does not exist
LINE 1: update hstgrp set regexpid='#'||groupid where groupid=5
^
[update hstgrp set regexpid='#'||groupid where groupid=5]
326412:20221215:014625.851 failed to update local proxy configuration copy: database error <--Failure


I saw there was a recent bug report so I updated the server and all of my proxy's to the latest versions available.

However for this 1 particular proxy which was installed on the latest stuff I'm still getting the above error.

Environment is running on RHEL 7 with postgresql 14 on both the proxy and main database server.
zabbix_server (Zabbix) 6.2.6
zabbix_proxy (Zabbix) 6.2.5


I also will note that I a jamming hosts in with ansible currently and we do have a large setup we are trying to undertake with around 5k monitored hosts so not sure if the massive adds may be attributing to the problem.

I can drop the database and recreate and it does seem to update however it seems that after a certain amount of time it eventually will regenerate the error.

Any help will be appreciated.

[Markku]

zabbix_server (Zabbix) 6.2.6
zabbix_proxy (Zabbix) 6.2.5

See https://www.zabbix.com/forum/zabbix-...721#post455721

Markku

[jomorton]

See https://www.zabbix.com/forum/zabbix-...721#post455721

Markku

Ahh ok. That's some strict versioning there. I downgraded the new proxy to 6.2.4 to see if that will help. At this point the server is at 6.2.6 and I don't have a backup to restore back to 6.2.3 which is where it started. I read in the bug report that someone updated to version 6.2.6 of the server and it fixed it but that's not the case for me.

https://support.zabbix.com/browse/ZBX-21995

"@Vladislavs Sokurenko, after an upgrade of Zabbix-server to 6.2.6 and restarting the zabbix-server, the error was gone. Thanks for the quick response."

What is odd is that I have 4 proxys 3 of the them began life at version 6.2.3 and were updated to 6.2.5 and they don't seem to have the same issue as the new proxy that was installed directly at 6.2.5. And once the server was updated to the latest 6.2.6 they all still seem perfectly fine. Weird.

[jomorton]

The downgrade seems to have worked. Not getting the db errors any longer.

[Markku]

[...] were updated to 6.2.5 and they don't seem to have the same issue [...]

Note that upgrading the proxy or server does not necessarily restart the processes automatically but it has to be done manually. Don't know how it went in your case but just saying.

Markku