Most server logs are accessible in Configuration->Logs.
- Audit Log (audit.csv) - used for audit and forensic analysis purposes. All archiving and user activity is recorded in the audit log. Data is recorded in CSV format.
- Core Debug Log (core\logs\debug.log) – used for troubleshooting and debugging purposes. All errors and exceptions are reported in the debug log.
- Instance Debug Log (ROOT\logs\debug.log) - also used for troubleshooting and debugging purposes.
- Apache Tomcat Logs (catalina.out or stdout.log) - if the server will not start at all, refer to these logs
Notice that the main server debug log files comprise of both a core and an instance debug.log file. It is separated out this way, since the product is multi-tenant. If you experience problems with the server, view the contents of both debug.log files to troubleshoot problems. Refer to File System Layout for the location of these files. If problems occur, the two debug.log files will usually contain helpful troubleshooting information. Generally, all errors being with the line ERROR. All others log levels are for informational purposes.
MailArchiva uses the Logback logging framework. Appenders are available for outputting logging information to variety of destinations (SNMP, console, syslog, etc.)
By default, the server will output all warnings, exceptions and errors to both core and instance debug logs. To enable detailed logging (i.e. to include troubleshooting messages) set the log level to Troubleshoot in Configuration->Logs.
All system activity that is logged is recorded in the audit log. Where possible, when an activity occurs, the system will record when it occurred, the username of the user that caused it, the user’s IP address and the name of the specific activity that was performed. This information is indexed and searchable in the Audit section of the console.
For convenience reasons, the audit information is stored in CSV format and therefore can be imported into programs like Excel and Crystal Reports for further analysis. In the event that the audit index is corrupted, it can be regenerated by executing a re-index in the Logging section of the console configuration.
Found this information useful? Visit mailarchiva.com to learn more about MailArchiva.