Results 1 to 5 of 5

Thread: Are mailbox.log and audit.log depreciated?

  1. #1
    Join Date
    Jul 2006
    Location
    Milwaukee, Wisconsin
    Posts
    81
    Rep Power
    9

    Default Are mailbox.log and audit.log depreciated?

    Hi,

    I have been trying to figure out why what I though to be critical log files are now empty. Since the 6.0.x series of releases, the following log files are completely blank:

    /opt/zimbra/log/audit.log
    /opt/zimbra/log/mailbox.log

    I have been able to find NOTHING to suggest these should be empty, but then nothing to suggest otherwise.

    So if these have been depreciated, where can I now find this information?

    Thanks,

    -n8

  2. #2
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    No, they're not deprecated and are still being updated on my server. Have you checked that your logger is running correctly? Are any of the other Zimbra log files empty or are they being updated as normal?
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  3. #3
    Join Date
    Jul 2006
    Location
    Milwaukee, Wisconsin
    Posts
    81
    Rep Power
    9

    Default

    Quote Originally Posted by phoenix View Post
    No, they're not deprecated and are still being updated on my server. Have you checked that your logger is running correctly? Are any of the other Zimbra log files empty or are they being updated as normal?
    Everything appears normal, logger is running according to 'zmcontrol status'. I have tried running the 'zmfixperms' script and can see that if I delete the two offending log files they are recreated, yet no data is written to them.

    /var/log/zimbra.log is written as usual and data is also being written to /opt/zimbra/mailboxd/logs/*trace.log and /opt/zimbra/mailboxd/logs/access_log*


    -n8

  4. #4
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    What does the output of this file look like:

    Code:
    /opt/zimbra/conf/log4j.properties
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  5. #5
    Join Date
    Jul 2006
    Location
    Milwaukee, Wisconsin
    Posts
    81
    Rep Power
    9

    Default

    Quote Originally Posted by phoenix View Post
    What does the output of this file look like:

    Code:
    /opt/zimbra/conf/log4j.properties
    Code:
    # An example log4j configuration file that outputs to System.out.  The
    # output information consists of relative time, log level, thread
    # name, logger name, nested diagnostic context and the message in that
    # order.
    
    # For the general syntax of property based configuration files see the
    # documenation of org.apache.log4j.PropertyConfigurator.
    
    log4j.threshhold=OFF
    
    log4j.rootLogger=INFO,LOGFILE
    #log4j.rootLogger=INFO,LOGFILE,SYSLOG
    
    # Appender LOGFILE writes to the file "/opt/zimbra/log/mailbox.log".
    #log4j.appender.LOGFILE=org.apache.log4j.FileAppender
    log4j.appender.LOGFILE=org.apache.log4j.DailyRollingFileAppender
    log4j.appender.LOGFILE.File=/opt/zimbra/log/mailbox.log
    log4j.appender.LOGFILE.DatePattern='.'yyyy-MM-dd
    log4j.appender.LOGFILE.Append=true
    log4j.appender.LOGFILE.layout=com.zimbra.common.util.ZimbraPatternLayout
    log4j.appender.LOGFILE.layout.ConversionPattern=%d %-5p [%t] [%z] %c{1} - %m%n
    
    # Appender AUDIT writes to the file "audit.log".
    log4j.appender.AUDIT=org.apache.log4j.DailyRollingFileAppender
    log4j.appender.AUDIT.File=/opt/zimbra/log/audit.log
    log4j.appender.AUDIT.DatePattern='.'yyyy-MM-dd
    log4j.appender.AUDIT.Append=true
    log4j.appender.AUDIT.layout=com.zimbra.common.util.ZimbraPatternLayout
    log4j.appender.AUDIT.layout.ConversionPattern=%d %-5p [%t] [%z] %c{1} - %m%n
    
    # Save zimbra.security to AUDIT appender 
    log4j.additivity.zimbra.security=false
    log4j.logger.zimbra.security=INFO,AUDIT
    
    # Syslog appender
    log4j.appender.SYSLOG=org.apache.log4j.net.SyslogAppender
    log4j.appender.SYSLOG.SyslogHost=localhost
    log4j.appender.SYSLOG.Facility=LOCAL0
    log4j.appender.SYSLOG.layout=com.zimbra.common.util.ZimbraPatternLayout
    log4j.appender.SYSLOG.layout.ConversionPattern=mailboxd: %-5p [%t] [%z] %c{1} - %m
    
    # Logger service appender
    log4j.appender.SLOGGER=org.apache.log4j.net.SyslogAppender
    log4j.appender.SLOGGER.SyslogHost=apollo.interfaithmilw.org
    log4j.appender.SLOGGER.Facility=LOCAL1
    log4j.appender.SLOGGER.layout=com.zimbra.common.util.ZimbraPatternLayout
    log4j.appender.SLOGGER.layout.ConversionPattern=mailboxd: %-5p [%t] [%z] %c{1} - %m
    
    # Appender SYNC writes to the file "sync.log".
    log4j.appender.SYNC=org.apache.log4j.DailyRollingFileAppender
    log4j.appender.SYNC.File=/opt/zimbra/log/sync.log
    log4j.appender.SYNC.DatePattern='.'yyyy-MM-dd
    log4j.appender.SYNC.Append=true
    log4j.appender.SYNC.layout=com.zimbra.common.util.ZimbraPatternLayout
    log4j.appender.SYNC.layout.ConversionPattern=%d %-5p [%t] [%z] %c{1} - %m%n
    
    # Appender SYNCTRACE writes to the file "synctrace.log".
    log4j.appender.SYNCTRACE=org.apache.log4j.DailyRollingFileAppender
    log4j.appender.SYNCTRACE.File=/opt/zimbra/log/synctrace.log
    log4j.appender.SYNCTRACE.DatePattern='.'yyyy-MM-dd
    log4j.appender.SYNCTRACE.Append=true
    log4j.appender.SYNCTRACE.layout=com.zimbra.common.util.ZimbraPatternLayout
    log4j.appender.SYNCTRACE.layout.ConversionPattern=%d %-5p [%t] [%z] %c{1} - %m%n
    
    # Appender SYNCSTATE writes to the file "syncstate.log".
    log4j.appender.SYNCSTATE=org.apache.log4j.DailyRollingFileAppender
    log4j.appender.SYNCSTATE.File=/opt/zimbra/log/syncstate.log
    log4j.appender.SYNCSTATE.DatePattern='.'yyyy-MM-dd
    log4j.appender.SYNCSTATE.Append=true
    log4j.appender.SYNCSTATE.layout=com.zimbra.common.util.ZimbraPatternLayout
    log4j.appender.SYNCSTATE.layout.ConversionPattern=%d %-5p [%t] [%z] %c{1} - %m%n
    
    # Appender WBXML writes to the file "wbxml.log".
    log4j.appender.WBXML=org.apache.log4j.DailyRollingFileAppender
    log4j.appender.WBXML.File=/opt/zimbra/log/wbxml.log
    log4j.appender.WBXML.DatePattern='.'yyyy-MM-dd
    log4j.appender.WBXML.Append=true
    log4j.appender.WBXML.layout=com.zimbra.common.util.ZimbraPatternLayout
    log4j.appender.WBXML.layout.ConversionPattern=%d %-5p [%t] [%z] %c{1} - %m%n
    
    # HttpMethodBase spews out too many WARN on the badly formatted cookies.
    log4j.logger.org.apache.commons.httpclient.HttpMethodBase=ERROR
    
    # spymemcached is too verbose at INFO level.
    log4j.logger.net.spy.memcached=WARN
    
    log4j.additivity.zimbra.sync=false
    log4j.logger.zimbra.sync=DEBUG,SYNC
    log4j.additivity.zimbra.synctrace=false
    log4j.logger.zimbra.synctrace=INFO,SYNCTRACE
    log4j.additivity.zimbra.syncstate=false
    log4j.logger.zimbra.syncstate=INFO,SYNCSTATE
    log4j.additivity.zimbra.wbxml=false
    log4j.logger.zimbra.wbxml=DEBUG,WBXML
    
    log4j.logger.zimbra=INFO
    log4j.logger.zimbra.op=WARN
    log4j.logger.com.zimbra=INFO
    log4j.additivity.zimbra.slogger=FALSE
    log4j.logger.zimbra.slogger=INFO,SLOGGER
    #log4j.logger.zimbra.slogger=ERROR

Similar Threads

  1. audit.log to syslog
    By captainmish in forum Administrators
    Replies: 6
    Last Post: 08-26-2011, 08:38 PM
  2. What's this audit.log message mean?
    By Baylink in forum Administrators
    Replies: 4
    Last Post: 04-26-2010, 07:14 AM
  3. Process Not Recorded Correctly in audit.log
    By todd_dsm in forum Administrators
    Replies: 2
    Last Post: 09-14-2009, 08:42 AM
  4. DelegateAuth in audit.log
    By Krishopper in forum Administrators
    Replies: 2
    Last Post: 05-17-2007, 06:08 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •