-
Problem report
-
Resolution: Unresolved
-
Trivial
-
6.0.41rc1, 7.0.14rc1, 7.2.8rc1, 7.4.0rc1 (master)
-
None
-
S25-W22/23
-
0.25
Steps to reproduce:
- Configure Zabbix with TimescaleDB and compression on (default). The log level should be 3 - warnings (the default one).
- I observed this at Zabbix 6.0 and 7.0 with TimescaleDB 2.20. It might be related to TimescaleDB version, but I have not checked it.
- Run Zabbix server once.
- Stop Zabbix server
- Run Zabbix server again.
- Open zabbix_server.log file.
Result:
There are no problems in zabbix_server.log during the first run of the server.
There are errors in zabbix_server.log during the second run and consequent runs when Zabbix server enables compression on housekeeper process start.
56296:20250527:162129.019 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR: columnstore policy already exists for hypertable or continuous aggregate "history"
HINT: Set option "if_not_exists" to true to avoid error.
[select add_compression_policy('history', integer '612000')]
56296:20250527:162129.019 failed to add compression policy to table 'history'
56312:20250527:162129.020 server #28 started [trapper #2]
56296:20250527:162129.051 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR: columnstore policy already exists for hypertable or continuous aggregate "history_uint"
HINT: Set option "if_not_exists" to true to avoid error.
[select add_compression_policy('history_uint', integer '612000')]
56296:20250527:162129.059 failed to add compression policy to table 'history_uint'
56296:20250527:162129.080 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR: columnstore policy already exists for hypertable or continuous aggregate "history_str"
HINT: Set option "if_not_exists" to true to avoid error.
[select add_compression_policy('history_str', integer '612000')]
56296:20250527:162129.080 failed to add compression policy to table 'history_str'
56296:20250527:162129.092 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR: columnstore policy already exists for hypertable or continuous aggregate "history_text"
HINT: Set option "if_not_exists" to true to avoid error.
[select add_compression_policy('history_text', integer '612000')]
56296:20250527:162129.093 failed to add compression policy to table 'history_text'
56296:20250527:162129.099 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR: columnstore policy already exists for hypertable or continuous aggregate "history_log"
HINT: Set option "if_not_exists" to true to avoid error.
[select add_compression_policy('history_log', integer '612000')]
56296:20250527:162129.106 failed to add compression policy to table 'history_log'
56296:20250527:162129.138 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR: columnstore policy already exists for hypertable or continuous aggregate "trends"
HINT: Set option "if_not_exists" to true to avoid error.
[select add_compression_policy('trends', integer '612000')]
56296:20250527:162129.138 failed to add compression policy to table 'trends'
56296:20250527:162129.150 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR: columnstore policy already exists for hypertable or continuous aggregate "trends_uint"
HINT: Set option "if_not_exists" to true to avoid error.
[select add_compression_policy('trends_uint', integer '612000')]
56296:20250527:162129.150 failed to add compression policy to table 'trends_uint'
Expected:
There errors above are not present in zabbix_server.log anymore.
- related to
-
ZBXNEXT-10018 Add TimescaleDB 2.20.x support
-
- In Progress
-
-
-
- Manual Test Failed
-
- mentioned in
-
Page Loading...
