Results 1 to 9 of 9

Thread: No Server Statistics

  1. #1
    Join Date
    Mar 2006
    Location
    Massachusetts
    Posts
    965
    Rep Power
    10

    Default No Server Statistics

    I just realized that since upgrading to version 4.5.6 my Server Statistics page on the Admin console is not getting updated. In searching around the system I found the following in the /tmp/logprocess.out file:
    Code:
    Table './zimbra_logger/mta' is marked as crashed and should be repaired
    Table './zimbra_logger/mta' is marked as crashed and should be repaired at /opt/zimbra/libexec/zmlogprocess line 1047.
    I'm assuming this is why I'm not getting the stats, but even if it isn't it's probably something that I need to address. How would I go about fixing this table? I'm not too familiar with MySQL database repair so any pointers would be greatly appreciated. I'd also like to know if it's recommended to shutdown Zimbra while doing the repair. Everything else on the system seems to be working fine, so I don't want to take any chances just to get the stats back.

    TIA,
    John

  2. #2
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    21

    Default

    Try
    Code:
    su - zimbra
    logmysql -D zimbra_logger
    Reading table information for completion of table and column names
    You can turn off this feature to get a quicker startup with -A
    
    Welcome to the MySQL monitor. Commands end with a ; or \g.
    Your MySQL connection id is 5
    Server version: 5.0.33-log Source distribution
    
    Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
    
    mysql> repair table mta;
    It should give you some output as to whether it went okay.

    Good luck,
    john

  3. #3
    Join Date
    Mar 2006
    Location
    Massachusetts
    Posts
    965
    Rep Power
    10

    Default

    Any risk of doing this with Zimbra running or should I shut it down first?

  4. #4
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    24

    Exclamation

    I have repaired tables dynamically, but do so at your own *** RISK ***. Best way would be to shutdown Zimbra, take a backup, repair table, and then restart Zimbra.

  5. #5
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    21

    Default

    Quote Originally Posted by soxfan View Post
    Any risk of doing this with Zimbra running or should I shut it down first?
    You have to have logmysql.server running in order to repair the tables.

    My suggestion would be to stop zimbra, and run a
    logmysql.server start

    then repair the tables with only logmysql.server running.

  6. #6
    Join Date
    Mar 2006
    Location
    Massachusetts
    Posts
    965
    Rep Power
    10

    Default

    Well, I finally got a chance to try the repair (weekend - less users on the system, lower email volume, etc.). Unfortunately I didn't have any luck. As suggested, I first shutdown zimbra, and then ran logmysql.server start. Next I executed 'logmysql -D zimbra_logger', which successfully brought up the mysql command prompt, then I ran 'mysql repair mta'. However, it immediately came back and said 'Table is already up to date'. As the command came back so quickly and didn't seem to do anything I was wary and sure enough when I ran 'check table mta' it still shows that the table is 'marked as crashed and should be repaired'. I tried the repair a couple of more times, but always with the same result.

    Any other suggestions? I've been Googling around for some general info on repairing MySQL tables, but I'm afraid to try anything that could make things worse. Since this is apparently just a log/stats table I'm willing to wipe it out and start from scratch, but I don't want to do anything that could mess up an otherwise fully functioning Zimbra server.

  7. #7
    Join Date
    Mar 2006
    Location
    Massachusetts
    Posts
    965
    Rep Power
    10

    Default

    Sorry, but I can't let this one drop. Even though everything seems to be running fine besides the stats, I don't like the idea of having a corrupted/crashed database table on the system. I think at this point I could probably drop the table, recreate it, and start from scratch. However, as I said before I don't want to do anything that might mess up something else. Can anyone provide any further help or suggestions?

    Thanks again,
    John

  8. #8
    Join Date
    Feb 2007
    Location
    Portland, OR
    Posts
    1,147
    Rep Power
    10

    Default

    The following page has a few tricks to repair corrupt tables. You might try one of the alternate methods listed here.

  9. #9
    Join Date
    Sep 2007
    Posts
    2
    Rep Power
    8

    Default

    I found on 4.5.6 that the reason stats were not being generated was that the rrdtool binaries used to generate the images were not in the right place. I suggest looking thru the cron logs and the stuff in /tmp to see if the cron job is executing.

    You can also "su - zimbra" then do "crontab -l" to see all the cron jobs that are executing.

    Also, have you tried a full restart of everything, like /etc/init.d zimbra stop followed by start?

Similar Threads

  1. initializing ldap...FAILED(256)ERROR
    By manjunath in forum Installation
    Replies: 39
    Last Post: 06-07-2013, 10:27 AM
  2. Zimbra fails after working for 2 weeks
    By Linsys in forum Administrators
    Replies: 10
    Last Post: 10-07-2008, 12:42 AM
  3. need advice on configuring zimbra to work with fax server
    By pheonix1t in forum Administrators
    Replies: 0
    Last Post: 07-11-2007, 07:46 PM
  4. Server Statistics dont work after changing hostname
    By rnuno in forum Administrators
    Replies: 1
    Last Post: 06-08-2007, 07:54 PM
  5. Error 256 on Installation
    By RuinExplorer in forum Installation
    Replies: 5
    Last Post: 10-19-2006, 09:19 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
  •