Issue with TimescaleDB integration: "function set_integer_now_func(...) does not exist" despite hypertables present

XMLWordPrintable

    • Type: Problem report
    • Resolution: Commercial support required
    • Priority: Trivial
    • None
    • Affects Version/s: 7.2.7, 7.2.8
    • Component/s: None
    • None

      Hello,

      We've followed the official Zabbix documentation to install and configure TimescaleDB:
      👉 https://www.zabbix.com/documentation/current/en/manual/appendix/install/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:

       

      SELECT * FROM timescaledb_information.hypertables; 

      Result:

       

      hypertable_schema | hypertable_name | ...
      -------------------+-----------------+--------
      zabbix             | history         | ...
      zabbix             | history_uint    | ...
      zabbix             | history_log     | ...
      zabbix             | history_text    | ...
      zabbix             | history_str     | ...
      zabbix             | history_bin     | ...
      ...
      (9 rows) 

      Environment:

      • TimescaleDB: 2.19.2
      • PostgreSQL: 17
      • Zabbix: 7.2.7 before TimescaleDB install, upgraded to 7.2.8 afterward

      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.

       

       

            Assignee:
            Zabbix Support Team
            Reporter:
            Simon D.
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: