Ad Widget

Collapse

1.4.5 to 1.6 - DB errors

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Queuer
    Junior Member
    • Jun 2008
    • 3

    #1

    1.4.5 to 1.6 - DB errors

    Hey all, just migrated from 1.4.5 to 1.6 and everything seems to work fine, but i keep getting these 2 errors on the log file:

    Code:
     22554:20081006:164559 Query::select curr.nodeid,curr.tablename,curr.recordid from node_cksum curr left join node_cksum prev on curr.tablename=prev.tablename and curr.recordid=prev.recordid and curr.fieldname=prev.fieldname and curr.nodeid=prev.nodeid and curr.cksumtype<>prev.cksumtype where prev.cksumid is null and curr.cksumtype=0
     22554:20081006:164559 Query failed:Unknown column 'prev.cksumid' in 'where clause' [1054]
    Code:
     22554:20081006:164349 Query::select curr.nodeid,curr.tablename,curr.recordid from node_cksum prev, node_cksum curr where curr.tablename=prev.tablename and curr.recordid=prev.recordid and curr.fieldname=prev.fieldname and curr.nodeid=prev.nodeid and curr.cksum<>prev.cksum and curr.cksumtype=1 and prev.cksumtype=0
     22554:20081006:164349 Query failed:Unknown column 'curr.fieldname' in 'where clause' [1054]
    Is this ok ? I mean, if everything runs fine even with that error I should not worry right ? Maybe I should fix it ? (how....)

    More info:
    OS - Redhat EL 4.0
    DB - MySQL Ver 14.12 Distrib 5.0.51a

    Thx.
  • bbrendon
    Senior Member
    • Sep 2005
    • 870

    #2
    Check the sql file for 1.6 and make sure your table that has a prev.cksumid column matches.
    Unofficial Zabbix Expert
    Blog, Corporate Site

    Comment

    • Queuer
      Junior Member
      • Jun 2008
      • 3

      #3
      well, created both fields on the node_cksum table and no more errors... but the table is still empty:

      Code:
      mysql> select * from node_cksum;
      Empty set (0.00 sec)
      What does this table do ? Im afraid something is not right...

      Comment

      • Alexei
        Founder, CEO
        Zabbix Certified Trainer
        Zabbix Certified SpecialistZabbix Certified Professional
        • Sep 2004
        • 5654

        #4
        Run ZABBIX 1.6, not old 1.4.x! This will fix your problem.
        Alexei Vladishev
        Creator of Zabbix, Product manager
        New York | Tokyo | Riga
        My Twitter

        Comment

        • flexguy
          Junior Member
          • Sep 2008
          • 19

          #5
          upgrade from 1.5.4 to 1.6

          Had similar problems when upgrading from 1.5.4 to 1.6. My lesson: do not ugrade from beta to stable, your DB does not like it.

          Comment

          Working...