Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Administrators
Reload this Page Problem with zmdbintegrityreport

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
Page 1 of 2 1 2
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 07-09-2007, 08:16 AM
Special Member
  
Posts: 121
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.
Reply With Quote
  #2 (permalink)  
Old 07-09-2007, 08:24 AM
Moderator
  
Posts: 6,236
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 08:29 AM..
Reply With Quote
  #3 (permalink)  
Old 07-09-2007, 08:49 AM
Special Member
  
Posts: 121
Default
Yup at 11:00pm from Cron Daemon.
__________________
Because we all can't be geniuses, I'll go first.
Reply With Quote
  #4 (permalink)  
Old 07-10-2007, 12:13 PM
Moderator
  
Posts: 6,236
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
Reply With Quote
  #5 (permalink)  
Old 07-10-2007, 03:24 PM
Project Contributor
  
Posts: 203
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!
Reply With Quote
  #6 (permalink)  
Old 07-10-2007, 03:44 PM
Moderator
  
Posts: 6,236
Default
Mlo isn't quite finished with his methodology and documentation yet-If you do so please make a backup
Reply With Quote
  #7 (permalink)  
Old 07-10-2007, 11:52 PM
Project Contributor
  
Posts: 203
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
Reply With Quote
  #8 (permalink)  
Old 07-10-2007, 11:55 PM
Moderator
  
Posts: 6,236
Default
Good to hear-thanks for being one of the first testers
Reply With Quote
  #9 (permalink)  
Old 07-12-2007, 02:58 PM
Special Member
  
Posts: 121
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.
Reply With Quote
  #10 (permalink)  
Old 07-16-2007, 08:52 AM
Project Contributor
  
Posts: 67
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?
__________________
hugo ribeiro
Last edited by hlribeiro; 07-16-2007 at 08:54 AM..
Reply With Quote
Reply
Page 1 of 2 1 2

« Previous Thread | Today's Posts or Week's Posts | Next Thread »

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes
Linear Mode Linear Mode


Similar Threads

Product Information

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com


Home - Blog - Contact Us - Archive - Top


 

SEO by vBSEO ©2011, Crawlability, Inc.