Ad Widget

Collapse

Zabbix 6.4 and 7.0 history_uint table keeps corrupting

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Alois007
    Junior Member
    • Jul 2024
    • 3

    #1

    Zabbix 6.4 and 7.0 history_uint table keeps corrupting

    It took about one week. I drop the table and recreate and after one week web gui starts displaying these errors:
    • Error in query [SELECT * FROM history_uint h WHERE h.itemid='56467' AND h.clock>1722149731 ORDER BY h.clock DESC,h.ns DESC LIMIT 1] [Index for table 'history_uint' is corrupt; try to repair it] [zabbix.php:22 → require_once() → ZBase->run() → ZBase->processRequest() → ZBase->processResponseFinal() → CView->getOutput() → include() → CObject->addItem() → unpack_object() → Widgets\Problems\Includes\WidgetProblems->toString() → Widgets\Problems\Includes\WidgetProblems->build() → Widgets\Problems\Includes\WidgetProblems->addProblemsToTable() → CMacrosResolverHelper::resolveTriggerOpdata() → CMacrosResolverHelper::resolveTriggerDescriptions( ) → CMacrosResolver->resolveTriggerDescriptions() → CMacrosResolverGeneral->getItemMacros() → CHistoryManager->getLastValues() → CHistoryManager->getLastValuesFromSqlWithPk() → DBselect() → trigger_error() in include/db.inc.php:248]
    It happened even on clean install. Table is irreparable I must drop it and recreate it. There is plenty of free space.
    It never happened on 6.0 LTS but it happens on 6.4 LTS and 7.0. 7.0 was upgrade but 6.4 LTS is clean install.
  • Alois007
    Junior Member
    • Jul 2024
    • 3

    #2
    A little more information, the table seems to have zero size and zero rows. And if I want to truncate it says: Got error 194 "Tablespace is missing for a table" from storage engine InnoDB. I must drop it and recreate it. SQL engine is mariadb Ver 15.1 Distrib 10.11.6-MariaDB, atm it's the latest version.
    I hope someone could help to solve it. Thanks in advance.

    Comment

    • Alois007
      Junior Member
      • Jul 2024
      • 3

      #3
      Yesterday new corruption I've never seen before. It's history table. It seems it could be data corruption but it's a virtual machine. Also there would be a lot of another users reporting troubles with MariaDB. I think it's trying to save some kind of malformed data and it corrupts the table.

      Comment

      • 9Elfer
        Junior Member
        • Oct 2024
        • 1

        #4
        Did you ever find a solution for this?
        I have the same or similar issue: A fresh zabbix 7.0.4 installation with mariadb 10.11.9 backend, and a few hours after having added the first host this problem starts.
        I started all over again twice, and the same happens every time.

        Comment

        • Thuso
          Junior Member
          • Oct 2024
          • 1

          #5
          Hi am having the same error did you get a solution for this?

          Comment

          Working...