Ad Widget

Collapse

mysql db patch reports no errors, zabbix_server.log says otherwise!

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • jeenam
    Member
    • Oct 2007
    • 43

    #1

    mysql db patch reports no errors, zabbix_server.log says otherwise!

    This thread is actually related to this post:



    The reason I'm reposting is because the topic of that post is probably misleading. The issue at hand here is the mysql db upgrade patch.

    Our server was upgraded from v1.4.4 to v1.6 last evening and the mysql patch installed without reporting any errors. The mysql server version is 4.1.7.

    Here are examples of the errors we're seeing:

    2405:20080925:011430 Query failed: [insert into alerts (alertid,actionid,triggerid,userid,clock,mediatype id,sendto,subject,message,status,retries) values (17613,7,17927,12,1222319670,1,'[email protected]',' High : OFF : Bind cingular-tx-2 on boise has not sent data for over 2 hours: boise **ZABBIX ALERT **','Device: boise
    When: 2008.09.25 01:14:30
    Trigger: Bind cingular-tx-2 on boise has not sent data for over 2 hours
    Trigger Key: cingular-tx-2-mtOut60
    Value: 0.016667',0,0)] Unknown column 'triggerid' in 'field list' [1054]

    2420:20080925:011530 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

    2420:20080925:011530 Query failed:Unknown column 'curr.fieldname' in 'where clause' [1054]
  • Alexei
    Founder, CEO
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Sep 2004
    • 5654

    #2
    I am absolutely sure you are running 1.4 server, not 1.6!
    Alexei Vladishev
    Creator of Zabbix, Product manager
    New York | Tokyo | Riga
    My Twitter

    Comment

    • jeenam
      Member
      • Oct 2007
      • 43

      #3
      Alexei,

      You are my personal hero. Turns out the person who set up the server put the binaries in some crazy locations and they were being called from a customized startup script in /etc/init.d/.

      Thank you for your help.

      Comment

      Working...