I've been trying to migrate my Zabbix database to TimescaleDB's cloud offering. I migrated my roles to the new database, updated the zabbix users password to match what i was already using.
My current Zabbix info, which in theory from timescale/zabbix documentation should be compatible to upgrade to the same version on timescaleDB's cloud:
Zabbix 5.0.43 LTS
Postgres 13
Timescale 2.13
Timescale Cloud:
Postgres 16.4
Timescale 2.16.1
I did a live migration of my database with
This didnt migrate table permissions so i had to grant my zabbix account permissions to the tables again.
When i connected my Zabbix server to the database after migration, i could see history fine, but it was not able to write to the database.
I was seeing the following errors:
I verified on the database though, that timescale was preloaded.

I rolled back to my old database for now, as i did not have time to debug. I'm honestly not sure where to go from here though.
My current Zabbix info, which in theory from timescale/zabbix documentation should be compatible to upgrade to the same version on timescaleDB's cloud:
Zabbix 5.0.43 LTS
Postgres 13
Timescale 2.13
Timescale Cloud:
Postgres 16.4
Timescale 2.16.1
I did a live migration of my database with
Code:
PGPASSWORD='XXXXXXXX' pg_dump -U svc_username -h zabbix-db-master -p 5432 -d zabbix-master | PGPASSWORD='XXXXXXXXX' psql -U tsdbadmin -h XXXX.cloud.timescale.com -p 31928 -d tsdb
When i connected my Zabbix server to the database after migration, i could see history fine, but it was not able to write to the database.
I was seeing the following errors:
Code:
zabbix_server [7853]: ERROR [file and function: <lld_item.c,lld_item_application_prototypes_get>, revision:daec4429367, line:4224] Something impossible has just happened.
Code:
7881:20240914:080956.911 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR: invalid INSERT on the root table of hypertable "history" HINT: Make sure the TimescaleDB extension has been preloaded.
I verified on the database though, that timescale was preloaded.
I rolled back to my old database for now, as i did not have time to debug. I'm honestly not sure where to go from here though.