Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: Problem with zmdbintegrityreport

  1. #1
    glitch23 is offline Special Member
    Join Date
    Jul 2006
    Location
    New York, NY
    Posts
    122
    Rep Power
    9

    Default Problem with zmdbintegrityreport

    Last night I got this email for the first time:

    Code:
    Can't locate Zimbra/Util/Common.pm in @INC (@INC contains: /zimbramon/lib /etc/perl /usr/local/lib/perl/5.8.7 /usr/local/share/perl/5.8.7 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at /opt/zimbra/libexec/zmdbintegrityreport line 30.
    BEGIN failed--compilation aborted at /opt/zimbra/libexec/zmdbintegrityreport line 30.
    Then I went to run the command as the zimbra user and got this:

    Code:
    zimbra@mail:~/libexec$ ./zmdbintegrityreport
    Generating report
    Database errors found.
    /opt/zimbra/mysql/bin/mysqlcheck --defaults-file=/opt/zimbra/conf/my.cnf -A -C -s -S /opt/zimbra/db/mysql.sock -u root --password=xxxxxxxxxxxxxxxxx
    mysql.help_category
     error    : Table upgrade required. Please do "REPAIR TABLE `help_category`" to fix it!
     mysql.help_keyword
     error    : Table upgrade required. Please do "REPAIR TABLE `help_keyword`" to fix it!
     mysql.help_topic
     error    : Table upgrade required. Please do "REPAIR TABLE `help_topic`" to fix it!
     zimbra.config
     error    : Table upgrade required. Please do "REPAIR TABLE `config`" to fix it!
     zimbra.mailbox_metadata
     error    : Table upgrade required. Please do "REPAIR TABLE `mailbox_metadata`" to fix it!
     zimbra.out_of_office
     error    : Table upgrade required. Please do "REPAIR TABLE `out_of_office`" to fix it!
     zimbra.service_status
     error    : Table upgrade required. Please do "REPAIR TABLE `service_status`" to fix it!
     zimbra.table_maintenance
     error    : Table upgrade required. Please do "REPAIR TABLE `table_maintenance`" to fix it!
     zimbra.volume
     error    : Table upgrade required. Please do "REPAIR TABLE `volume`" to fix it!
    And yes /opt/zimbra/zimbramon/lib/Zimbra/Util/Common.pm does exist.

    This was after installing ZCS-4.5.6 for Ubuntu in my Dev environment which is why I haven't updated my profile yet

    In any case help would be greatly appreciated.
    Because we all can't be geniuses, I'll go first.

  2. #2
    mmorse's Avatar
    mmorse is offline Moderator
    Join Date
    May 2006
    Location
    USA
    Posts
    6,242
    Rep Power
    21

    Default

    let me guess- (though u did say last night) 11:00:01pm sunday night?
    Cron <zimbra@box> /opt/zimbra/libexec/zmdbintegrityreport -m
    Last edited by mmorse; 07-09-2007 at 07:29 AM.

  3. #3
    glitch23 is offline Special Member
    Join Date
    Jul 2006
    Location
    New York, NY
    Posts
    122
    Rep Power
    9

    Default

    Yup at 11:00pm from Cron Daemon.
    Because we all can't be geniuses, I'll go first.

  4. #4
    mmorse's Avatar
    mmorse is offline Moderator
    Join Date
    May 2006
    Location
    USA
    Posts
    6,242
    Rep Power
    21

    Default

    This wiki page will discuss some solutions in general-please do not attempt anything without a full backup of all your zimbra directories
    What to Do When zmdbintegrityreport Reports Errors - ZimbraWiki

  5. #5
    jdell is offline Project Contributor
    Join Date
    Jul 2006
    Location
    Reno, NV, USA
    Posts
    203
    Rep Power
    9

    Exclamation 2 problems with new db integrity report

    I recently upgraded to 4.5.6 NE, and saw had some problems with the db integrity check cron job. I'm Running CentOS 4.5.

    I found Util/Common.pm here: /opt/zimbra/zimbramon/lib/Zimbra/Util/Common.pm

    Detailed error below:

    Code:
    Can't locate Zimbra/Util/Common.pm in @INC (@INC contains: /zimbramon/lib /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl/5.8.4 /usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8
     /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl/5.8.4 /usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .) at /opt/zimbra/libexec/zmdbintegrityreport line 30.
    BEGIN failed--compilation aborted at /opt/zimbra/libexec/zmdbintegrityreport line 30.
    Logging in as zimbra, I manually ran zmdbintegrityreport and it runs ok but with these errors.

    Should I run repair table? I would think if a table needed upgrading the zimbra installer script would have done that?

    Code:
    zimbra@zimbra->./zmdbintegrityreport 
    Generating report
    Database errors found.
    /opt/zimbra/mysql/bin/mysqlcheck --defaults-file=/opt/zimbra/conf/my.cnf -A -C -s -S /opt/zimbra/db/mysql.sock -u root --password=[*sanitized*]
    mysql.help_category
     error    : Table upgrade required. Please do "REPAIR TABLE `help_category`" to fix it!
     mysql.help_keyword
     error    : Table upgrade required. Please do "REPAIR TABLE `help_keyword`" to fix it!
     mysql.help_topic
     error    : Table upgrade required. Please do "REPAIR TABLE `help_topic`" to fix it!
     zimbra.config
     error    : Table upgrade required. Please do "REPAIR TABLE `config`" to fix it!
     zimbra.mailbox_metadata
     error    : Table upgrade required. Please do "REPAIR TABLE `mailbox_metadata`" to fix it!
     zimbra.out_of_office
     error    : Table upgrade required. Please do "REPAIR TABLE `out_of_office`" to fix it!
     zimbra.service_status
     error    : Table upgrade required. Please do "REPAIR TABLE `service_status`" to fix it!
     zimbra.table_maintenance
     error    : Table upgrade required. Please do "REPAIR TABLE `table_maintenance`" to fix it!
     zimbra.volume
     error    : Table upgrade required. Please do "REPAIR TABLE `volume`" to fix it!

  6. #6
    mmorse's Avatar
    mmorse is offline Moderator
    Join Date
    May 2006
    Location
    USA
    Posts
    6,242
    Rep Power
    21

    Default

    Mlo isn't quite finished with his methodology and documentation yet-If you do so please make a backup

  7. #7
    jdell is offline Project Contributor
    Join Date
    Jul 2006
    Location
    Reno, NV, USA
    Posts
    203
    Rep Power
    9

    Default 3 zimbra servers, all 3 have same problem

    I have 3 separate zimbra servers, and all 3 had the same errors reported by zmdbintegrityreport. I think there is definitely an upgrade bug that the integrity check has revealed. After the repair table, zmdbintegrityreport is clean on all my servers.

    Per this page: What to Do When zmdbintegrityreport Reports Errors - ZimbraWiki

    All had error posted above. All are RHEL4. All were upgrades from 4.0 to 4.5. A full dump/restore was only performed on 1 of the 3 boxes. 2 boxes RHEL4 32-bit, 1 RHEL4 64-bit. All error tables showed version 9, after repair, version was 10.

    To be safe, I shutdown all of zimbra, backed up, and then just started mysql to make the changes:

    Code:
    # su - zimbra
    # zmcontrol stop
    # mysql.server start
    # mysql
    mysql> use mysql;
    mysql> REPAIR TABLE `help_category`;
    mysql> REPAIR TABLE `help_keyword`;
    mysql> REPAIR TABLE `help_topic`;
    mysql> use zimbra;
    mysql> REPAIR TABLE `config`;
    mysql> REPAIR TABLE `mailbox_metadata`;
    mysql> REPAIR TABLE `out_of_office`;
    mysql> REPAIR TABLE `service_status`;
    mysql> REPAIR TABLE `table_maintenance`;
    mysql> REPAIR TABLE `volume`;
    mysql> exit
    # zmdbintegrityreport (should be clean now)
    # mysql.server stop
    # zmcontrol start

  8. #8
    mmorse's Avatar
    mmorse is offline Moderator
    Join Date
    May 2006
    Location
    USA
    Posts
    6,242
    Rep Power
    21

    Default

    Good to hear-thanks for being one of the first testers

  9. #9
    glitch23 is offline Special Member
    Join Date
    Jul 2006
    Location
    New York, NY
    Posts
    122
    Rep Power
    9

    Default

    Quote Originally Posted by jdell View Post
    I have 3 separate zimbra servers, and all 3 had the same errors reported by zmdbintegrityreport. I think there is definitely an upgrade bug that the integrity check has revealed. After the repair table, zmdbintegrityreport is clean on all my servers.

    Per this page: What to Do When zmdbintegrityreport Reports Errors - ZimbraWiki

    All had error posted above. All are RHEL4. All were upgrades from 4.0 to 4.5. A full dump/restore was only performed on 1 of the 3 boxes. 2 boxes RHEL4 32-bit, 1 RHEL4 64-bit. All error tables showed version 9, after repair, version was 10.

    To be safe, I shutdown all of zimbra, backed up, and then just started mysql to make the changes:

    Code:
    # su - zimbra
    # zmcontrol stop
    # mysql.server start
    # mysql
    mysql> use mysql;
    mysql> REPAIR TABLE `help_category`;
    mysql> REPAIR TABLE `help_keyword`;
    mysql> REPAIR TABLE `help_topic`;
    mysql> use zimbra;
    mysql> REPAIR TABLE `config`;
    mysql> REPAIR TABLE `mailbox_metadata`;
    mysql> REPAIR TABLE `out_of_office`;
    mysql> REPAIR TABLE `service_status`;
    mysql> REPAIR TABLE `table_maintenance`;
    mysql> REPAIR TABLE `volume`;
    mysql> exit
    # zmdbintegrityreport (should be clean now)
    # mysql.server stop
    # zmcontrol start
    That indeed fixed the integrity report. BTW the install this happened on was originally a ZCS 3.x version.
    Because we all can't be geniuses, I'll go first.

  10. #10
    hlribeiro is offline Project Contributor
    Join Date
    Feb 2007
    Location
    Maringá, PR, Brasil
    Posts
    67
    Rep Power
    8

    Default

    I receive this emails weekly since upgraded to 4.5.6.
    Today I ran the script manually, and got no errors:

    Code:
    [zimbra@mail libexec]$ ./zmdbintegrityreport
    Generating report
    No errors found
    [zimbra@mail libexec]$
    Anyway, the script isn't running from cron.
    The error message I receive from email, like the above listed, contains the first path:

    Code:
    Can't locate Zimbra/Util/Common.pm in @INC (@INC contains: /zimbramon/lib [...]
    I don't know anything about perl, but this path seems wrong at all to me, once there is no "/zimbramon", but /opt/zimbra/zimbramon.

    Is this not an error?
    Last edited by hlribeiro; 07-16-2007 at 07:54 AM.
    hugo ribeiro

Page 1 of 2 12 LastLast

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Zimbra, WM5.0, AS + problem with regional fonts
    By wojo2000 in forum Zimbra Mobile
    Replies: 7
    Last Post: 06-25-2007, 01:04 AM
  2. strange MTA Relay Problem
    By pfuschi in forum Installation
    Replies: 0
    Last Post: 10-31-2006, 11:51 AM
  3. Is it started or not
    By kwelipatton in forum Installation
    Replies: 10
    Last Post: 03-28-2006, 11:11 PM

Posting Permissions

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