zmmsgtrace not working

[Alfspace]

Hi,

we have Network GA 3.0.1_160 and I was trying the zmmsgtrace command but no results so far, always 0 messages found, I tried with this for example:

[zimbra@store1 ~]$ zmmsgtrace -s agms@xxx.edu -r agms3@xxx.edu
-t 20062702
Tracing messages
from agms@xxx.edu
to agms3@xxx.edu
During 20062702


0 messages found

And I'm sure the message was sent and received because I sent it.
I typed it in my store1 server where I have the logger running (only server which has it running)

any suggestions ?

[marcmac]

Try expanding your search (fewer search terms)
zmmsgtrace -s sender

Just use the sender's username, without the domain.

[Alfspace]

[zimbra@store1 ~]$ zmmsgtrace -s agms@xxx.edu
Tracing messages
from agms@xxx.edu


0 messages found


Same result.

[marcmac]

and
zmmsgtrace -s agms

returns the same thing?

Are any statistics showing up in your admin UI for message traffic?

[Alfspace]

same results no messages found, in the graphics section of admin there are some data from last 30 days, 60 days and from 48 hours just bars for message count from 00 to 04 and nothing else (I suppose these are hours)

[marcmac]

Hmm.

Can you enter this into bugzilla, and we'll take a look at what's causing it?

Thanks for the report.

[Alfspace]

I was looking to Server Status and just the store1 server shows a recent date 25/2/2006, the other servers are way behind 17/1/2006 and I'm pretty sure we rebooted them on last friday after upgrading to GA release.

[Alfspace]

Ok Marc, how I add this to the Bugzilla ?

I'm Alfredo from Universidad Francisco Marroquin, Guatemala.

[marcmac]

Ok, that could be the problem.

Try this on one of the servers that's not showing up in the status:

grep zimbra /etc/syslog.conf

You should see a line that ends with "@loggerhost" where "loggerhost" is the name of the host running the logger daemon.

If that's not present, then run as root:
/opt/zimbra/bin/zmsyslogsetup

and re-check syslog.conf

After verifying that entry, on the same host:

logger -p mail.info "test"

Then, on the logger host, verify that "test" is logged to /var/log/zimbra.log

If it's not, check the process list:
ps auxww | grep syslogd

On RH, syslogd should be running with the "-r" option (to allow logging from remote servers).

If it's not, edit the file
/etc/sysconfig/syslog
and add the -r to the SYSLOGD_OPTIONS item
and
/etc/init.d/syslog stop
/etc/init.d/syslog start

And try the logger command again.

[marcmac]

Hey alfredo - try the stuff I just posted. If you need to add it to bugzilla, go to bugzilla.zimbra.com and you should be able to create a new bug.