Ad Widget

Collapse

(Timescaledb) ERROR: "history_bin" is not a hypertable

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • dedisoft
    Junior Member
    • Dec 2013
    • 18

    #1

    (Timescaledb) ERROR: "history_bin" is not a hypertable

    Hello,

    We've followed the official Zabbix documentation to install and configure TimescaleDB: https://www.zabbix.com/documentation...ll/timescaledb

    However, after installation, Zabbix logs show repeated errors like this:

    [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR: function set_integer_now_func(unknown, unknown, boolean) does not exist
    LINE 1: select set_integer_now_func('history', 'zbx_ts_unix_now', tr...
    ^
    HINT: No function matches the given name and argument types. You might need to add explicit type casts.
    [select set_integer_now_func('history', 'zbx_ts_unix_now', true)]
    ...
    Table "history" is not a hypertable. Execute TimescaleDB configuration step as described in Zabbix documentation to upgrade schema.
    This happens for multiple history tables: history, history_uint, history_log, history_text, history_str, history_bin. But when we check in PostgreSQL, these tables are hypertables:

    Code:
    select hypertable_schema || '.' || hypertable_name as hypertable, hypertable_size(hypertable_schema || '.' || hypertable_name) as hypertable_size, pg_size_pretty(hypertable_size(hypertable_schema || '.' || hypertable_name)) as hypertable_pretty_size from timescaledb_information.hypertables order by hypertable_size desc;​
    Result:

    hypertable | hypertable_size | hypertable_pretty_size
    ---------------------+-----------------+------------------------
    zabbix.history | 79622627328 | 74 GB
    zabbix.history_uint | 73899040768 | 69 GB
    zabbix.history_text | 30351433728 | 28 GB
    zabbix.trends_uint | 7447232512 | 7102 MB
    zabbix.trends | 5805072384 | 5536 MB
    zabbix.history_log | 959733760 | 915 MB
    zabbix.history_str | 567238656 | 541 MB
    zabbix.auditlog | 117137408 | 112 MB
    zabbix.history_bin | 24576 | 24 kB
    (9 rows)
    Is this a compatibility issue (e.g., Timescale 2.19.2 with PostgreSQL 17 not fully supported), or are we missing an additional step not mentioned in the Zabbix documentation?

    Thanks in advance for your help.

    Environment:
    • TimescaleDB: 2.19.2
    • PostgreSQL: 17
    • Zabbix: 7.2.7 before TimescaleDB install, upgraded to 7.2.8 afterward
    Last edited by dedisoft; 20-06-2025, 14:54.
Working...