Configuring logging for CAS components and command-line utilities

You can change the default logging configuration of the Endeca CAS Service and any CAS components you run from the command line.

Log location and rolling

By default, the logging utilities write logs to the <install path>\CAS\workspace\logs directory.

By default, the CAS Service log rolls once it exceeds a size of 100MB, and the CAS Service keeps 10 backups of its log.

Note: If you delete the log file, the Endeca CAS Service recreates the log only when you restart the service. So it is possible to delete the log, run a crawl, and not have logging information if you did not restart the service.

Configuration files for CAS components

The <install path>\CAS\workspace\conf directory contains the following logging configuration files:
  • cas-cmd.log4j.properties - configures logging for the CAS Server Command-line Utility
  • cas-service-log4j.properties - configures logging for the Endeca CAS Service
  • component-manager-cmd.log4j.properties - configures logging for the Component Instance Manager Command-line Utility
  • recordstore-cmd.log4j.properties - configures logging for the Record Store Command-line Utility

Logging options and levels

You can re-configure log locations, log file size, log pattern, and logging message level such as:
  • DEBUG designates fine-grained informational events that are most useful to debug Record Store problems.
  • INFO designates informational messages that highlight the progress of Record Store operations at a coarse-grained level.
  • WARN designates potentially harmful situations.
  • ERROR designates error events that might still allow the Record Store to continue running.
  • FATAL designates very severe error events that will presumably lead the Record Store to abort.
  • OFF has the highest possible rank and is intended to turn off logging.
These levels allow you to monitor events of interest at the appropriate granularity. When you are initially setting up your Record Store implementation, you might want to use the DEBUG level to get all messages, and change to a less verbose level in production.