Proxies configuration permanent update with PGSQL + TimescaleDB

[alexis-pit]

Hi,

I had issue on Zabbix 7.0 with server and proxies logs spammed by "sending configuration data to proxy...". The same thing as this post : https://www.zabbix.com/forum/zabbix-...to-all-proxies
So I was happy when the 7.0.5 released this fix : https://support.zabbix.com/browse/ZBXNEXT-9397
I tested it on our test server, upgrade from Zabbix 7.0.4 to 7.0.5, based on MariaDB 10.11. And it's work perfectly, no more logs, only when config changes are made so proxy config update is required.

But when our production server based on PostgreSQL 16.5 + TimescaleDB 2.17.2 was upgraded, the proxies still get their configuration updated every 10 seconds (As defined in config file) even if no change was made.

I created a third server (clone of the production one), so it's not a full fresh server install but on this server i created a new database on the same PGSQL server, imported the schema from zabbix scripts. Added a single proxy via the WebUI, no host assigned to it. This is working fine, no proxy config update when it's not required.

When I enable TimescaleDB with these commands :

echo "CREATE EXTENSION IF NOT EXISTS timescaledb CASCADE;" | sudo -u postgres psql zabbix
cat /usr/share/zabbix-sql-scripts/postgresql/timescaledb/schema.sql | sudo -u zabbix psql zabbix

The proxies config sending comme back and logs are spammed again.
When I disable timescale with :

update config set db_extension=''";

It's stop instantly sending config.

Is something wrong in my setup ? Or is this a bug ?

Regards,

[alexis-pit]

Hi,

Nobody else encounter this issue ? Ofcourse, it has not impact on production, so it's not urgent, but I would like to know if we are alone in this situation.
If I think it's Zabbix bug, how can I report it ?

Thks,

[cyber]

https://support.zabbix.com/projects/ZBX is the place to report such things.