Missing audit.log file

[cjking]

Hi,
I have Zimbra 7.2.0 running on Ubuntu 10.04.
There is no /opt/zimbra/log/audit.log or mailbox.log file on my Zimbra installation. According to zmcontrol status, everything is running:
antispam Running
antivirus Running
ldap Running
logger Running
mailbox Running
memcached Running
mta Running
snmp Running
spell Running
stats Running
zmconfigd Running

Can anyone offer any assistance with this?

Thanks,
Chris.

[cjking]

Still haven't solved this, but looking in zmmailboxd.out:

log4j:WARN Failed to set property [rollingPolicy] to value "org.apache.log4j.rolling.TimeBasedRollingPoli cy".
log4j:WARN Please set a rolling policy for the RollingFileAppender named 'MILTER'
log4j:WARN Failed to set property [rollingPolicy] to value "org.apache.log4j.rolling.TimeBasedRollingPoli cy".
log4j:WARN Please set a rolling policy for the RollingFileAppender named 'AUDIT'
log4j:ERROR No output stream or file set for the appender named [LOGFILE].
Total time for which application threads were stopped: 0.0002960 seconds
4.015: [GC 4.015: [ParNew: 490752K->22361K(552064K), 0.0681330 secs] 490752K->22361K(2392192K), 0.0681870 secs] [Times: user=0.12 sys=0.00, real=0.07 secs]
Total time for which application threads were stopped: 0.0691700 seconds
Total time for which application threads were stopped: 0.0005250 seconds
Total time for which application threads were stopped: 0.0000720 seconds
Total time for which application threads were stopped: 0.0052590 seconds
log4j:ERROR No output stream or file set for the appender named [AUDIT].

[cjking]

I figured it out - I'll leave this here incase anyone else runs into the same problem.
There were leftover versions of lib4j libraries after an upgrade. I used find -name '*lib4j*' in /opt/zimbra to locate them.
/opt/zimbra/lib/jars/log4j-1.2.15.jar
/opt/zimbra/lib/jars/slf4j-log4j12-1.5.8.jar
/opt/zimbra/jetty-6.1.22.z6/lib/log4j-1.2.15.jar

After deleting those files and running zmmailboxdctl restart my audit.log and mailbox.log are back in action!

[phoenix]

I figured it out - I'll leave this here incase anyone else runs into the same problem.

Thanks for posting your solution, can you file a bug report and include what version was upgraded?