zmdailyreport returns nothing

[rdavisids]

the new open source release mentions a daily summary of postfix is now included. I am not receiving anything. If I force the cron for zmdailyreport it returns no messages found. Is there a config I am missing? I have run searches on the forums and wiki and haven't seen anything about this.

[KevinH]

Do you have the logger installed?

[rdavisids]

there is a check next to logger in the admin UI and when I use zmcontrol start it is always among the services listed. Plus there are two process attributed to it:

/opt/zimbra/logger/mysql/bin/mysqld --defaults-file=/opt/zimbra/conf/my.logger.c ...

/bin/sh /opt/zimbra/logger/mysql/bin/mysqld_safe --defaults-file=/opt/zimbra/con ...

[rdavisids]

Any new ideas about this problem? Can you point me to a config file or a command to debug?

[KevinH]

Originally Posted by rdavisids

Any new ideas about this problem? Can you point me to a config file or a command to debug?

Well you could look at the script itself and see what it's trying to do.

[rdavisids]

If I run perl -w zmdailyreport

I get
Use of uninitialized value in string ne at zmdailyreport line 103

Here is the area of interest:

sub getMsgIds {
my $ids = shift;
my $user = $options{u};

my $whereClause = "";
my @clauses = ();
my $statement = "";
my $ary;

my %uniqIds = ();
my @clauses = ();

my $count = 0;

%uniqIds = ();

if ($user ne "") {
push @clauses, "(sender like '%".$user."%' or recipient like '%".$user."%')";
}

This appears to be a problem. Is this script correct?

[KevinH]

I think ne is ok. You could try making that !=

[rdavisids]

Changed and ran with no effect.

[jholder]

rdavisids,
Ya, there apprears to be a problem with the daily cron job.
I think Marc would have a little bit more info.

I belive this is related to bug 6531 (3-16-06)

http://bugzilla.zimbra.com/show_bug.cgi?id=6531

We'll keep you posted.

/etc/cron.daily/prelink:

/etc/cron.daily/prelink: line 47: 8870 Aborted /usr/sbin/prelink -av $PRELINK_OPTS >>/var/log/prelink.log 2>&1

[rdavisids]

I have now upgraded from 3.01 to 3.11 and the report is now being delivered.

Must have been related to the bug.