Results 1 to 7 of 7

Thread: [SOLVED] database integrity check shows errors

  1. #1
    alto is offline Special Member
    Join Date
    Feb 2007
    Location
    Ireland
    Posts
    125
    Rep Power
    8

    Question [SOLVED] database integrity check shows errors

    Should I be concerned about this and what do I need to do?

    This is the email I received and below the output of running mysqlcheck manually

    Database errors found.
    /opt/zimbra/mysql/bin/mysqlcheck --defaults-file=/opt/zimbra/conf/my.cnf -S /opt/zimbra/db/mysql.sock -A -C -s -u root --password=*************
    backup.shared_blob_digest
    warning : 1 client is using or hasn't closed the table properly
    error : Can't read key from filepos: 4228096
    Error : Incorrect key file for table './backup/shared_blob_digest.MYI'; try to repair it
    error : Corrupt
    zimbra.jiveID
    warning : 1 client is using or hasn't closed the table properly
    zimbra.jiveOffline
    warning : 1 client is using or hasn't closed the table properly
    zimbra.jiveUserProp
    warning : 1 client is using or hasn't closed the table properly

    Manually:

    [root@mail ~]$ /opt/zimbra/mysql/bin/mysqlcheck --defaults-file=/opt/zimbra/conf/my.cnf -S /opt/zimbra/db/mysql.sock -A -C -s -u root --password=********
    backup.shared_blob_digest
    warning : Table is marked as crashed
    warning : 1 client is using or hasn't closed the table properly
    error : Can't read key from filepos: 4228096
    Error : Incorrect key file for table './backup/shared_blob_digest.MYI'; try to repair it
    error : Corrupt

    Trying to connect to mysql to check tables

    [root@mail ~]$ /opt/zimbra/mysql/bin/mysql
    ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)

    contents of /opt/zimbra/conf/my.cnf
    [mysqld]

    basedir = /opt/zimbra/mysql
    datadir = /opt/zimbra/db/data
    socket = /opt/zimbra/db/mysql.sock
    pid-file = /opt/zimbra/db/mysql.pid
    bind-address = localhost
    port = 7306
    user = zimbra

    external-locking

    log-slow-queries = /opt/zimbra/log/myslow.log
    long-query-time = 1
    log-long-format
    log-queries-not-using-indexes

  2. #2
    uxbod's Avatar
    uxbod is offline Moderator
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    24

    Default

    Code:
    su - zimbra
    mysql
    use backup
    repair table shared_blob_digest;
    use zimbra
    repair table jiveID;
    repair table jiveOffline;
    repair table jiveUserProp;
    exit

  3. #3
    alto is offline Special Member
    Join Date
    Feb 2007
    Location
    Ireland
    Posts
    125
    Rep Power
    8

    Default

    Many thanks uxbod. No idea what I was doing but i ran all that and the errors are gone.

  4. #4
    scohol is offline Active Member
    Join Date
    Sep 2009
    Location
    Canberra, Australia
    Posts
    25
    Rep Power
    5

    Default

    I have a similar issue. But this might be abit more serious.

    This is the result of a db integrity check. However, server seems to still be in ok working order.

    Database errors found.
    /opt/zimbra/mysql/bin/mysqlcheck --defaults-file=/opt/zimbra/conf/my.cnf -S /opt/zimbra/db/mysql.sock -A -C -s -u root --password=

    mboxgroup1.appointment
    error : Corrupt
    mboxgroup1.data_source_item
    error : Corrupt
    mboxgroup1.imap_folder
    error : Corrupt
    mboxgroup1.imap_message
    error : Corrupt
    mboxgroup1.mail_item
    error : Corrupt
    mboxgroup1.open_conversation
    error : Corrupt
    mboxgroup1.pop3_message
    error : Corrupt
    mboxgroup1.revision
    error : Corrupt
    mboxgroup1.tombstone
    error : Corrupt

    This is only some of the results
    Last edited by scohol; 02-06-2011 at 04:24 PM.

  5. #5
    MKC
    MKC is offline Member
    Join Date
    Feb 2011
    Posts
    10
    Rep Power
    4

    Default

    Hello everyone.
    I'm sorry to bring up this old topic, but I've received a similar e-mail:

    Code:
    Database errors found.
    /opt/zimbra/mysql/bin/mysqlcheck --defaults-file=/opt/zimbra/conf/my.cnf -S /opt/zimbra/db/mysql.sock -A -C -s -u root --password=???????
    mboxgroup1.appointment
     error    : Table upgrade required. Please do "REPAIR TABLE `appointment`" or dump/reload to fix it!
     mboxgroup1.data_source_item
     error    : Table upgrade required. Please do "REPAIR TABLE `data_source_item`" or dump/reload to fix it!
     mboxgroup1.imap_folder
     error    : Table upgrade required. Please do "REPAIR TABLE `imap_folder`" or dump/reload to fix it!
     mboxgroup1.mail_item
     error    : Table upgrade required. Please do "REPAIR TABLE `mail_item`" or dump/reload to fix it!
     mboxgroup1.pop3_message
     error    : Table upgrade required. Please do "REPAIR TABLE `pop3_message`" or dump/reload to fix it!
     mboxgroup2.appointment
     error    : Table upgrade required. Please do "REPAIR TABLE `appointment`" or dump/reload to fix it!
     mboxgroup2.data_source_item
     error    : Table upgrade required. Please do "REPAIR TABLE `data_source_item`" or dump/reload to fix it!
     mboxgroup2.imap_folder
     error    : Table upgrade required. Please do "REPAIR TABLE `imap_folder`" or dump/reload to fix it!
     mboxgroup2.mail_item
     error    : Table upgrade required. Please do "REPAIR TABLE `mail_item`" or dump/reload to fix it!
     mboxgroup2.pop3_message
     error    : Table upgrade required. Please do "REPAIR TABLE `pop3_message`" or dump/reload to fix it!
     mboxgroup3.appointment
     error    : Table upgrade required. Please do "REPAIR TABLE `appointment`" or dump/reload to fix it!
     mboxgroup3.data_source_item
     error    : Table upgrade required. Please do "REPAIR TABLE `data_source_item`" or dump/reload to fix it!
     mboxgroup3.imap_folder
     error    : Table upgrade required. Please do "REPAIR TABLE `imap_folder`" or dump/reload to fix it!
     mboxgroup3.mail_item
     error    : Table upgrade required. Please do "REPAIR TABLE `mail_item`" or dump/reload to fix it!
     mboxgroup3.pop3_message
     error    : Table upgrade required. Please do "REPAIR TABLE `pop3_message`" or dump/reload to fix it!
     mboxgroup4.appointment
     error    : Table upgrade required. Please do "REPAIR TABLE `appointment`" or dump/reload to fix it!
     mboxgroup4.data_source_item
     error    : Table upgrade required. Please do "REPAIR TABLE `data_source_item`" or dump/reload to fix it!
     mboxgroup4.imap_folder
     error    : Table upgrade required. Please do "REPAIR TABLE `imap_folder`" or dump/reload to fix it!
     mboxgroup4.mail_item
     error    : Table upgrade required. Please do "REPAIR TABLE `mail_item`" or dump/reload to fix it!
     mboxgroup4.pop3_message
     error    : Table upgrade required. Please do "REPAIR TABLE `pop3_message`" or dump/reload to fix it!
     mboxgroup5.appointment
     error    : Table upgrade required. Please do "REPAIR TABLE `appointment`" or dump/reload to fix it!
     mboxgroup5.data_source_item
     error    : Table upgrade required. Please do "REPAIR TABLE `data_source_item`" or dump/reload to fix it!
     mboxgroup5.imap_folder
     error    : Table upgrade required. Please do "REPAIR TABLE `imap_folder`" or dump/reload to fix it!
     mboxgroup5.mail_item
     error    : Table upgrade required. Please do "REPAIR TABLE `mail_item`" or dump/reload to fix it!
     mboxgroup5.pop3_message
     error    : Table upgrade required. Please do "REPAIR TABLE `pop3_message`" or dump/reload to fix it!
     mboxgroup6.appointment
     error    : Table upgrade required. Please do "REPAIR TABLE `appointment`" or dump/reload to fix it!
     mboxgroup6.data_source_item
     error    : Table upgrade required. Please do "REPAIR TABLE `data_source_item`" or dump/reload to fix it!
     mboxgroup6.imap_folder
     error    : Table upgrade required. Please do "REPAIR TABLE `imap_folder`" or dump/reload to fix it!
     mboxgroup6.mail_item
     error    : Table upgrade required. Please do "REPAIR TABLE `mail_item`" or dump/reload to fix it!
     mboxgroup6.pop3_message
     error    : Table upgrade required. Please do "REPAIR TABLE `pop3_message`" or dump/reload to fix it!
     mysql.general_log
     Error    : You can't use locks with log tables.
     mysql.slow_log
     Error    : You can't use locks with log tables.
     zimbra.config
     error    : Table upgrade required. Please do "REPAIR TABLE `config`" or dump/reload to fix it!
     zimbra.deleted_account
     error    : Table upgrade required. Please do "REPAIR TABLE `deleted_account`" or dump/reload to fix it!
     zimbra.mailbox
     error    : Table upgrade required. Please do "REPAIR TABLE `mailbox`" or dump/reload to fix it!
     zimbra.mailbox_metadata
     error    : Table upgrade required. Please do "REPAIR TABLE `mailbox_metadata`" or dump/reload to fix it!
     zimbra.mobile_devices
     error    : Table upgrade required. Please do "REPAIR TABLE `mobile_devices`" or dump/reload to fix it!
     zimbra.out_of_office
     error    : Table upgrade required. Please do "REPAIR TABLE `out_of_office`" or dump/reload to fix it!
     zimbra.scheduled_task
     error    : Table upgrade required. Please do "REPAIR TABLE `scheduled_task`" or dump/reload to fix it!
     zimbra.table_maintenance
     error    : Table upgrade required. Please do "REPAIR TABLE `table_maintenance`" or dump/reload to fix it!
     zimbra.volume
     error    : Table upgrade required. Please do "REPAIR TABLE `volume`" or dump/reload to fix it!
    So I've logged in and tried to repair the tables as described earlier in this topic, however MySQL returned with the following error:
    "The storage engine for the table doesn't support repair."

    What should I do?
    Thanks in advance!

    PS: I'm using ZCS 7.1.2, but I simply can't seem to find where to update this information in the user CP.
    Last edited by MKC; 09-10-2011 at 06:03 AM.

  6. #6
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,506
    Rep Power
    57

    Default

    Quote Originally Posted by MKC View Post
    I'm sorry to bring up this old topic, but I've received a similar e-mail:
    Except your problem isn't the same as the one in this thread.

    Quote Originally Posted by MKC View Post
    What should I do?!
    I guess you've just upgraded your version of Zimbra? If that's the case, this question has been asked and answered many times (recently) in the forums and you should read the post-install steps in the Release Notes.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  7. #7
    MKC
    MKC is offline Member
    Join Date
    Feb 2011
    Posts
    10
    Rep Power
    4

    Default

    Quote Originally Posted by phoenix View Post
    Except your problem isn't the same as the one in this thread.

    I guess you've just upgraded your version of Zimbra? If that's the case, this question has been asked and answered many times (recently) in the forums and you should read the post-install steps in the Release Notes.
    I'm confused about this, it seems that I hadn't searched enough. I've applied the script, sorry for the bother. Feel free to delete my previous post.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Replies: 2
    Last Post: 04-19-2010, 04:58 PM
  2. zimbra 0.92 build 1433: append message errors
    By kellner in forum Error Reports
    Replies: 4
    Last Post: 01-20-2009, 04:34 PM
  3. Database errors found
    By samgreco in forum Administrators
    Replies: 2
    Last Post: 12-01-2008, 07:27 AM
  4. Mailbox log errors?
    By carnold in forum Administrators
    Replies: 3
    Last Post: 08-11-2008, 07:31 AM
  5. Upgrading to 3.1.3 errors sumary
    By kowell in forum Administrators
    Replies: 8
    Last Post: 06-25-2006, 12:11 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •