Log File Location

Log files are in the following directory (folder).

3RABBITZ_HOME/logs

Logs are written to a separate file for each day. Server logs go to catalina.yyyy-MM-dd.log, and application logs go to localhost.yyyy-MM-dd.log.

Changing the Log File Location

To change the log file location, edit the following file.

3RABBITZ_HOME/tomcat/conf/logging.properties

For how to configure this file, see the Apache Tomcat documentation.

If you change the log file location, you can no longer manage logs in the <Admin | Servers | Log> menu. To keep managing them there, set the new log file location with the following command in the Console.

set-preference -name LOG_DIRECTORY -value /app/logs

Downloading Log Files

Download log files in the <Admin | Servers | Log> menu.

Deleting Log Files

Delete log files in the <Admin | Servers | Log> menu.

Preventing Log File Downloads and Deletion

To prevent log files from being downloaded or deleted in the <Admin | Servers | Log> menu, run the following command in the Console.

set-preference -name DISABLE_LOG_FILE_ACCESS -value true

Log File Compression

When you use ManualWorks for a long time, log files pile up. To handle this, ManualWorks automatically compresses old log files by month. The archive is named 3rabbitz_log_files.yyyy-MM.zip, and the compressed log files are deleted.

Changing the Log Level

You can change the log level in the Console. For details, see Log.

If the log level is set more detailed than INFO, ManualWorks notifies the administrator when the server starts. If you lower the level briefly to investigate a problem and forget to restore it, logs pile up and put a load on the disk and performance.

• The levels that trigger the notification are CONFIG, FINE, FINER, FINEST, and ALL. WARNING and SEVERE are less detailed than INFO, so they do not trigger it.

• The check runs every time the server starts.

• The log level item on the system health check screen uses the same criteria.