Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation

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
 
LinkBack Thread Tools Search this Thread Display Modes
  #11 (permalink)  
Old 12-11-2007, 02:54 PM
Active Member
 
Posts: 34
Default

I have been battling this problem for a long time. I had it resolved after deleting the db data folder and then reinstalling - or so I think - but really, something is seriously not working there.

I have spent weeks looking into this without much success except a lucky hit once.
Reply With Quote
  #12 (permalink)  
Old 12-12-2007, 09:03 AM
Active Member
 
Posts: 34
Default

Finally got it to work again yesterday by running zmlogprocess and zmgengraphs manually. The reason it was failing was that the processes did not have permissions to update the /tmp files specified for output. (>)

However, after midnight or so this stopped working again.

This is Opensuse and I changed the various files shown in other posts to cause the syslog restart to work properly.

Maybe it is related to that, not sure.
Reply With Quote
  #13 (permalink)  
Old 12-13-2007, 05:18 AM
Active Member
 
Posts: 34
Default

Infuriating. After midnight the statistics show up again. I have no idea why. Some cron job, no doubt.
Reply With Quote
  #14 (permalink)  
Old 12-14-2007, 10:15 PM
Active Member
 
Posts: 32
Default

Any help here would be great...
Reply With Quote
  #15 (permalink)  
Old 12-18-2007, 02:48 AM
Starter Member
 
Posts: 1
Default

Did you look at:

Repair Logger Data Corruption - Zimbra :: Wiki

In my setup I got the following error in /tmp/logprocess.out:

Table './zimbra_logger/raw_logs' is marked as crashed and should be repaired

The wiki solution seems to work for me :-)
Reply With Quote
  #16 (permalink)  
Old 12-18-2007, 09:29 AM
Active Member
 
Posts: 32
Default

I gave the article a shot and this is the output after running the commands:

mysql> REPAIR TABLE raw_logs;
+------------------------+--------+----------+----------+
| Table | Op | Msg_type | Msg_text |
+------------------------+--------+----------+----------+
| zimbra_logger.raw_logs | repair | status | OK |
+------------------------+--------+----------+----------+
1 row in set (24.27 sec)

mysql> REPAIR TABLE raw_logs USE_FRM;
+------------------------+--------+----------+------------------------------------------+
| Table | Op | Msg_type | Msg_text |
+------------------------+--------+----------+------------------------------------------+
| zimbra_logger.raw_logs | repair | warning | Number of rows changed from 0 to 1795910 |
| zimbra_logger.raw_logs | repair | status | OK |
+------------------------+--------+----------+------------------------------------------+
2 rows in set (23.90 sec)
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

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




 

SEO by vBSEO ©2011, Crawlability, Inc.