Ad Widget

Collapse

v1.6.1 Table conversion bug.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • wakko
    Junior Member
    • Dec 2008
    • 19

    #1

    v1.6.1 Table conversion bug.

    I've just started working a new job, and I've inherited a zabbix installation.

    As a part of finishing the deployment, I'm in the process of converting a node from node=0 to node=2. My database is around 9.5GB, so it's taking around 4 hours to convert.

    After conversion, there's a problem. All of my graphs are blank. After digging around in the database, I've verified that all of the data is still there, but the ID numbers have been inconsistently converted. Some of the tables have been converted to ID=ID+200200000000000 and some of the tables have been converted to ID=ID+200000000000000.

    Obviously, this is going to cause problems with the relationships, when itemid is 200200000000100 in one table and 200000000000100 in another table.

    I've done conversions before with version 1.4.6 and not had this problem, so I suspect this is a new issue with 1.6.x.
  • wakko
    Junior Member
    • Dec 2008
    • 19

    #2
    I've done an audit of each table. Here are the mis-converted tables and the rows that are using the 200000000000000 node modulus. The rest of the tables are using the 200200000000000 modulus for their *id columns.

    Table | Columns
    --------------------
    acknowledges | acknowledgeid, userid, eventid
    alerts | alertid, actionid, eventid, userid
    auditlog | auditid, userid
    events | eventid, objectid
    history | itemid
    history_str | itemid
    history_uint | itemid
    ids | nextid
    sessions | userid
    trends | itemid
    trends_uint | itemid

    Comment

    Working...