update from 7.0 to 7.01 timescale wrong version detected

[neorejdv76]

After updating my ubuntu 22.04 system from zabbix 7.0 to 7.01 i am getting the error in the front-end:
2.12.2 Error! Unable to start Zabbix server. Unsupported timescaledb database server version. Must be at least 2.13.0

In zabbix-server log:
1851:20240725:131934.052 TimescaleDB version 21202 is not officially supported. Recommended version is at least TimescaleDB Community Edition 2.13.0.
1851:20240725:131934.060 Zabbix Server stopped. Zabbix 7.0.1 (revision 0543fbe4af6) zz0.q4qmqosdrgzz

sudo dpkg-query --list | grep -i timescale
ii timescaledb-2-loader-postgresql-14 2.15.3~ubuntu22.04 amd64 The loader for TimescaleDB to load individual versions.
ii timescaledb-2-postgresql-14 2.15.3~ubuntu22.04 amd64 An open-source time-series database based on PostgreSQL, as an extension.
ii timescaledb-toolkit-postgresql-14 1:1.18.0~ubuntu22.04 amd64 Library of analytical hyperfunctions, time-series pipelining, and other SQL utilities, compatible with TimescaleDB and PostgreSQL
ii timescaledb-tools 0.15.0~ubuntu22.04 amd64 A suite of tools that can be used with TimescaleDB. zz0.yjasei5msszz

So the correct version is installed of timescaledb, but zabbix-server does not agree and finds that the system is running on a lower version.

Is this a bug? and is there a work around for it?

before the update i was using timescaledb version 2.15.3 and zabbix 7.0 without any problems.

[neorejdv76]

today tried to update from 7.0 to 7.02, with the same error:
587851:20240731:081109.869 using configuration file: /etc/zabbix/zabbix_server.conf
587851:20240731:081109.896 TimescaleDB version 21202 is not officially supported. Recommended version is at least TimescaleDB Community Edition 2.13.0.
587851:20240731:081109.902 Zabbix Server stopped. Zabbix 7.0.2 (revision d1b0c3308ce).

Nobody seen this error?

[Markku]

No exact knowledge about TimescaleDB, but https://www.zabbix.com/documentation...nding-software says:

Make sure to install TimescaleDB Community Edition, which supports compression.

Is that TSDB of yours this "Community Edition"?

Markku

[neorejdv76]

Yes it is the Community Edition. The server has been running since zabbix7 alpha just file with this version of timescaledb. Never had any problems with it, and every update went ok. Until from official 7.0 to either 7.01 or 7.02.

[Markku]

In the release notes 7.0.1 added "soft minimal version" requirement 2.13, yeah. So apparently your TSDB was recognized as 2.12 all the time, if you said it wasn't upgraded at this point.

If it worked in 7.0.0, you can try "AllowUnsupportedDB" or whatever the configuration directive is in Zabbix server, if that helps.

If you are still able to test 7.0.0 with it, increase the server's debug level, it should then print out the TSDB version at start.

Markku

[neorejdv76]

I think a did not make it clear what was going on.

My timescaledb version is 2.15.3. That has not changed since te upgrade from 7.0 beta to 7.0 official. There where no problems with the zabbix server at al everything worked fine.
After updating to 7.01 or 7.02 without getting any new updates for postgressql or timescaledb zabbix is detecting 2.12.2 as the installed timescaledb version. I have 2.15.3 what should be fine, and worked with zabbix 7.0.

I have seem in de postgres log:
2024-07-31 11:54:56.386 CEST [782] LOG: TimescaleDB background worker launcher connected to shared catalogs
2024-07-31 11:54:58.682 CEST [839] zabbix@zabbix LOG: could not receive data from client: Connection reset by peer
2024-07-31 11:55:08.784 CEST [934] zabbix@zabbix LOG: could not receive data from client: Connection reset by peer
2024-07-31 11:55:21.024 CEST [956] zabbix@zabbix LOG: could not receive data from client: Connection reset by peer
2024-07-31 11:55:33.277 CEST [966] zabbix@zabbix LOG: could not receive data from client: Connection reset by peer
2024-07-31 11:55:45.527 CEST [972] zabbix@zabbix LOG: could not receive data from client: Connection reset by peer
2024-07-31 11:55:57.791 CEST [978] zabbix@zabbix LOG: could not receive data from client: Connection reset by peer

So this means that zabbix-server is not able to connect to the datebase. And since it cannot connect to the database, it assumes that version 2.12.2 is installed?
this is the output in zabbix_server.log on debug level 4

2990:20240731:121050.741 using configuration file: /etc/zabbix/zabbix_server.conf
2990:20240731:121050.741 In zbx_load_modules()
2990:20240731:121050.741 End of zbx_load_modules():SUCCEED
2990:20240731:121050.741 In zbx_ipc_service_start() service:rtc
2990:20240731:121050.741 In zbx_ipc_socket_open()
2990:20240731:121050.741 End of zbx_ipc_socket_open():FAIL
2990:20240731:121050.741 End of zbx_ipc_service_start():SUCCEED
2990:20240731:121050.741 In zbx_db_connect() flag:0
2990:20240731:121050.757 query without transaction detected
2990:20240731:121050.757 query [txnlev:0] [set escape_string_warning to off]
2990:20240731:121050.760 query without transaction detected
2990:20240731:121050.760 query [txnlev:0] [set extra_float_digits to 3]
2990:20240731:121050.760 query [txnlev:0] [show standard_conforming_strings]
2990:20240731:121050.760 End of zbx_db_connect():0
2990:20240731:121050.760 In zbx_db_get_database_type()
2990:20240731:121050.760 query [txnlev:0] [select userid from users limit 1]
2990:20240731:121050.761 there is at least 1 record in "users" table
2990:20240731:121050.761 End of zbx_db_get_database_type():ZBX_DB_SERVER
2990:20240731:121050.761 In zbx_init_database_cache()
2990:20240731:121050.761 In zbx_shmem_create() param:'HistoryCacheSize' size:16777216
2990:20240731:121050.761 valid user addresses: [0x7f6a72cb1170, 0x7f6a73cb0ff0] total size: 16776832
2990:20240731:121050.761 End of zbx_shmem_create()
2990:20240731:121050.761 In zbx_shmem_create() param:'HistoryIndexCacheSize' size:4194304
2990:20240731:121050.761 valid user addresses: [0x7f6a728b1180, 0x7f6a72cb0ff0] total size: 4193904
2990:20240731:121050.761 End of zbx_shmem_create()
2990:20240731:121050.761 In init_trend_cache()
2990:20240731:121050.761 In zbx_shmem_required_size() size:0 chunks_num:1 descr:'trend cache' param:'TrendCacheSize'
2990:20240731:121050.761 End of zbx_shmem_required_size() size:422
2990:20240731:121050.761 In zbx_shmem_create() param:'TrendCacheSize' size:4194304
2990:20240731:121050.761 valid user addresses: [0x7f6a724b1170, 0x7f6a728b0ff0] total size: 4193920
2990:20240731:121050.761 End of zbx_shmem_create()
2990:20240731:121050.761 End of init_trend_cache()
2990:20240731:121050.761 End of zbx_init_database_cache()
2990:20240731:121050.761 query [txnlev:0] [select pg_encoding_to_char(encoding) from pg_database where datname='zabbix']
2990:20240731:121050.762 query [txnlev:0] [select oid from pg_namespace where nspname='public']
2990:20240731:121050.762 query [txnlev:0] [select count(*) from pg_attribute as a left join pg_class as c on c.relfilenode=a.attrelid left join pg_collation as l on l.oid=a.attcollation where atttypid in (25,1043) and c.relnamespace=2200 and c.relam=0 and l.collname<>'default']
2990:20240731:121050.763 query [txnlev:0] [show client_encoding]
2990:20240731:121050.764 query [txnlev:0] [show server_encoding]
2990:20240731:121050.764 In zbx_dbms_version_info_extract()
2990:20240731:121050.764 End of zbx_dbms_version_info_extract() version:140012
2990:20240731:121050.764 In zbx_db_check_extension()
2990:20240731:121050.764 query [txnlev:0] [select 1 from information_schema.columns where table_name='config' and column_name='db_extension' and table_schema='public']
2990:20240731:121050.768 query [txnlev:0] [select db_extension from config]
2990:20240731:121050.768 query [txnlev:0] [select extversion from pg_extension where extname = 'timescaledb']
2990:20240731:121050.768 TimescaleDB version: [21202]
2990:20240731:121050.768 TimescaleDB version 21202 is not officially supported. Recommended version is at least TimescaleDB Community Edition 2.13.0.
2990:20240731:121050.769 End of zbx_db_check_extension():FAIL
2990:20240731:121050.769 query [txnlev:0] [select 1 from information_schema.columns where table_name='config' and column_name='dbversion_status' and table_schema='public']
2990:20240731:121050.771 query [txnlev:0] [select 1 from information_schema.table_constraints where table_name='history' and constraint_type='PRIMARY KEY' and constraint_schema='public']
2990:20240731:121050.772 In zbx_db_flush_version_requirements()
2990:20240731:121050.772 query without transaction detected
2990:20240731:121050.773 query [txnlev:0] [update config set dbversion_status='[{"database":"PostgreSQL","current_version":"14. 12" ,"min_version":"10.9","max_version":"16.x","his tor y_pk":1,"min_supported_version":"13.0","flag":0},{ "database":"timescaledb","current_version":"2. 12.2 ","min_version":"2.0.1","max_version":"2.15"," min_ supported_version":"2.13.0","flag":4,"extension_er r_code":5,"compression_availability":false,"compre ssed_chunks_history":0,"compressed_chunks_trends": 0}]']
2990:20240731:121050.775 End of zbx_db_flush_version_requirements()
2990:20240731:121050.775 Zabbix Server stopped. Zabbix 7.0.2 (revision d1b0c3308ce).

[Markku]

Yes, I got that, and still your database announces version "21202":

2990:20240731:121050.768 query [txnlev:0] [select extversion from pg_extension where extname = 'timescaledb']
2990:20240731:121050.768 TimescaleDB version: [21202]

I don't know how TSDB works, can you just update that value yourself, or what can be done. But, as mentioned, since you have already used the database with 7.0.0 successfully, you should be able to use this to get it running again (even though the underlying problem of incorrect version information in the database is still there):

https://www.zabbix.com/documentation/current/en/manual/appendix/config/zabbix_server#allowunsupporteddbversions

Markku

[Markku]

For example:

https://docs.timescale.com/self-hosted/latest/upgrades/minor-upgrade/

So as I take it, if you have at some point earlier upgraded TimescaleDB from 2.12 to 2.15, that kind of command is needed (in addition to upgrading the packages).

But again, I haven't ever administrated TSDB.

Markku