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
  #1 (permalink)  
Old 08-21-2007, 08:23 AM
Member
 
Posts: 11
Default [SOLVED] Zimbra 4.5.6 on Ubuntu 6.06 LTS - Logger problem

Hi

I have a problem with logging on my zimbra install. I have looked through a lot of threads in these forums and I'm not experiencing any of the errors detailed in related threads that I can find.

cat /tmp/logprocess.out
Pruning service/server entries older then 2007-08-21 16:00:02
raidar maps to raidar.seabed.no
Processing mta entries from 0
Found 0 messages
Deleting processed postfix logs from raw_logs...Done
Processing clamd entries from 0
Found 0 entries
Deleting processed clamd logs from raw_logs...Done
Processing amavis entries from 31415
Found 4 entries
Saving ID 31455
Deleting processed amavis logs from raw_logs...Done
Processing sendmail entries from 0
Found 0 entries
Deleting processed sendmail logs from raw_logs...Done
Processing zimbramon entries from 31292
Found 3 entries
Saving ID 31488
Deleting processed zimbramon logs from raw_logs...Done
Aggregating hour mta from 2007-08-21 15:00:00 to 2007-08-21 16:00:00
Aggregating day mta from 2007-08-20 00:00:00 to 2007-08-21 00:00:00
Aggregating hour amavis from 2007-08-21 15:00:00 to 2007-08-21 16:00:00
Aggregating day amavis from 2007-08-20 00:00:00 to 2007-08-21 00:00:00
Aggregating hour disk from 2007-08-21 15:00:00 to 2007-08-21 16:00:00
Aggregating day disk from 2007-08-20 00:00:00 to 2007-08-21 00:00:00
Retaining 31 days worth of raw logs based on zimbraLogRawLifetime config.
Retaining 730 days worth of summary logs based on zimbraLogSummaryLifetime config.
Pruning raw mta logs from 2007-07-21 00:00:00
Pruning raw amavis logs from 2007-07-21 00:00:00
Pruning raw disk logs from 2007-07-21 00:00:00
Pruning summary mta logs from 2005-08-21 00:00:00
Pruning summary amavis logs from 2005-08-21 00:00:00
Pruning summary disk logs from 2005-08-21 00:00:00
Pruning other raw logs from 2007-07-21 00:00:00

For some reason it never finds any mail messages when it parses the logs. I have sent a bunch of test mails between accounts on the server and also mails to outside account (I haven't received any external mail as I have no MX record pointing to this server yet). Postfix does log to /var/log/zimbra.log for all mails sent.

Using zmmsgtrace also never finds anything, but I guess that is a related problem.

The logger service seems to run fine otherwise. Can it be a problem with that it doesn't parse the file correctly for the postfix entries? it seems to find the zimbramon entries just fine.

Let me know if I should provide more info

thanks,
Hogne

Edit:

Figured out the problem.

The following thread clued me in to have a look in the DB
MTA logging question

I had the same problem with postfix_qid being NULL and I noticed in my log entries the postfix ID was 13 digits.

After changing the following in /opt/zimbra/libexec/zmlogger everything works fine:

Code:
$qid = $1 if ($app =~ /^postfix/ && $msg =~ /^(\S{8,12}): /);
To:

Code:
$qid = $1 if ($app =~ /^postfix/ && $msg =~ /^(\S{8,13}): /);
It might be an idea to change this regexp into something more robust which can handle the apparent variances in Postfix ID length.

Last edited by hogne; 09-03-2007 at 11:37 PM..
Reply With Quote
  #2 (permalink)  
Old 09-04-2007, 10:37 AM
Former Zimbran
 
Posts: 5,606
Default

Quote:
Originally Posted by hogne View Post
Hi

I have a problem with logging on my zimbra install. I have looked through a lot of threads in these forums and I'm not experiencing any of the errors detailed in related threads that I can find.

cat /tmp/logprocess.out
Pruning service/server entries older then 2007-08-21 16:00:02
raidar maps to raidar.seabed.no
Processing mta entries from 0
Found 0 messages
Deleting processed postfix logs from raw_logs...Done
Processing clamd entries from 0
Found 0 entries
Deleting processed clamd logs from raw_logs...Done
Processing amavis entries from 31415
Found 4 entries
Saving ID 31455
Deleting processed amavis logs from raw_logs...Done
Processing sendmail entries from 0
Found 0 entries
Deleting processed sendmail logs from raw_logs...Done
Processing zimbramon entries from 31292
Found 3 entries
Saving ID 31488
Deleting processed zimbramon logs from raw_logs...Done
Aggregating hour mta from 2007-08-21 15:00:00 to 2007-08-21 16:00:00
Aggregating day mta from 2007-08-20 00:00:00 to 2007-08-21 00:00:00
Aggregating hour amavis from 2007-08-21 15:00:00 to 2007-08-21 16:00:00
Aggregating day amavis from 2007-08-20 00:00:00 to 2007-08-21 00:00:00
Aggregating hour disk from 2007-08-21 15:00:00 to 2007-08-21 16:00:00
Aggregating day disk from 2007-08-20 00:00:00 to 2007-08-21 00:00:00
Retaining 31 days worth of raw logs based on zimbraLogRawLifetime config.
Retaining 730 days worth of summary logs based on zimbraLogSummaryLifetime config.
Pruning raw mta logs from 2007-07-21 00:00:00
Pruning raw amavis logs from 2007-07-21 00:00:00
Pruning raw disk logs from 2007-07-21 00:00:00
Pruning summary mta logs from 2005-08-21 00:00:00
Pruning summary amavis logs from 2005-08-21 00:00:00
Pruning summary disk logs from 2005-08-21 00:00:00
Pruning other raw logs from 2007-07-21 00:00:00

For some reason it never finds any mail messages when it parses the logs. I have sent a bunch of test mails between accounts on the server and also mails to outside account (I haven't received any external mail as I have no MX record pointing to this server yet). Postfix does log to /var/log/zimbra.log for all mails sent.

Using zmmsgtrace also never finds anything, but I guess that is a related problem.

The logger service seems to run fine otherwise. Can it be a problem with that it doesn't parse the file correctly for the postfix entries? it seems to find the zimbramon entries just fine.

Let me know if I should provide more info

thanks,
Hogne

Edit:

Figured out the problem.

The following thread clued me in to have a look in the DB
MTA logging question

I had the same problem with postfix_qid being NULL and I noticed in my log entries the postfix ID was 13 digits.

After changing the following in /opt/zimbra/libexec/zmlogger everything works fine:

Code:
$qid = $1 if ($app =~ /^postfix/ && $msg =~ /^(\S{8,12}): /);
To:

Code:
$qid = $1 if ($app =~ /^postfix/ && $msg =~ /^(\S{8,13}): /);
It might be an idea to change this regexp into something more robust which can handle the apparent variances in Postfix ID length.
File an enhancement on that.
Reply With Quote
  #3 (permalink)  
Old 09-05-2007, 07:09 AM
Advanced Member
 
Posts: 193
Default

Im not sure if I got the correct information: But is this the qid:

mail postfix/smtp[15412]: A2F95945C7: to=<

If this is the qid, in my case I got 10?

Thanks in advance.
Reply With Quote
  #4 (permalink)  
Old 09-05-2007, 07:25 AM
Member
 
Posts: 11
Default

I did some further investigations on this here:

Unfortunate code assumptions about postfix_qid

Sorry for the double posting, but this thread got corrupted for a while because of my noscript add-on messing up when I submitted an edit to the first post in this thread, so I made a new one.
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.