Activity and error monitoring

Activity monitoring, including error logging is controlled by setting CONTENTA CRAWLER/CRAWLER_DEBUG_LEVEL to one of the values below. The default is warn.

  • trace
  • debug
  • info
  • warn
  • error
  • fatal

After it reaches 10 MB, the activity will spill over to a new crawler.log file. The original will be renamed and have a number appended to it, starting with 1. For example, crawler_1.log

Solr logging is controlled by the file, Contenta_Home\Tools\Solr\example\resources\log4j.properties. The directory where the solr.log log file is created is specified in the first line of this file, the default setting for which is solr.log=logs/.

Note that this is a relative path, meaning that the directory named logs is created relative to where the Solr service is started. On Windows, the logs directory will reliably be found at Contenta_Home\Tools\Solr\example\logs if the setting in the log4j.properties file hasn't been modified. However, on Linux, the location of the logs directory depends on what directory the administrator is in when starting the Solr daemon. For this reason, RWS recommends that you change the solr.log setting in the log4j.properties file to a full path, which will ensure that solr.log is always created in the same directory. The following are examples of the solr.log set to a full file path.
  • On Linux: solr.log=/pdm/logs/Solr
  • On Windows: solr.log=\Contenta_home\logs\Solr