Gentics CMS Log Files

1 File locations

All log files will be rotated automatically.

Log File	Description
/Node/node/content/log/publishrun_*	Logfiles for each publish run. There is a simple version and a verbose version for each publish run.
/Node/node/log/halt.log	Contains log information if Gentics CMS can’t connect to the database
/Node/node/log/scheduler.log	Default logfile to log output of the scheduler process
/Node/var/httpd/logs and /Node/var/httpd/logs	Apache access and error logs
/Node/node/system/log/scheduler_task_*	individual scheduler task log files
/Node/mysql/var/*.error	MySql error logs
/Node/tomcat/logs/gentics.log	Gentics CMS Java error log
/Node/tomcat/logs/catalina.out	Tomcat logs
/Node/tomcat/logs/*.log	Tomcat startup logs

2 Configuration

The Gentics CMS Java error log file (default: /Node/tomcat/logs/gentics.log) is generated with log4j. The exact file name and format depends on the version of Gentics CMS.

2.1 Configuration with log4j 1.x

Up to Gentics CMS Version 5.41.x, the used logging library is log4j 1.×. The configuration file is located at `/Node/tomcat/conf/gentics/nodelog.properties` and uses the Java properties format.

/Node/tomcat/conf/gentics/nodelog.properties


# default log4j configuration: log ERROR and FATAL
log4j.rootLogger=ERROR,GENTICS

log4j.logger.com.gentics.lib.base.factory.NodeFactory=ERROR
log4j.logger.com.gentics.contentnode.events.DependencyManager=ERROR

# devtools logging
log4j.logger.com.gentics.contentnode.devtools=ERROR,DEVTOOLS

# Default Gentics appender.
# Old log files will be tar.gz'ed by Gentics Content.Node.

log4j.appender.GENTICS=org.apache.log4j.DailyRollingFileAppender
log4j.appender.GENTICS.File=/Node/var/tomcat/logs/gentics.log
log4j.appender.GENTICS.DatePattern='.'yyyy-MM-dd'.txt'

log4j.appender.GENTICS.layout=org.apache.log4j.PatternLayout
log4j.appender.GENTICS.layout.ConversionPattern=%d [%t] %-5p %c - %m%n

# devtools appender
log4j.appender.DEVTOOLS=org.apache.log4j.DailyRollingFileAppender
log4j.appender.DEVTOOLS.File=/Node/var/tomcat/logs/devtools.log
log4j.appender.DEVTOOLS.DatePattern='.'yyyy-MM-dd'.txt'
log4j.appender.DEVTOOLS.layout=org.apache.log4j.PatternLayout
log4j.appender.DEVTOOLS.layout.ConversionPattern=%d [%t] %-5p %c - %m%n

2.2 Configuration with log4j 2.x

Starting with Gentics CMS Version 5.42.x, the used logging library is log4j 2.x. The configuration file is located at `/Node/tomcat/conf/gentics/nodelog.yml` and uses the YAML format.

/Node/tomcat/conf/gentics/nodelog.yml


Configuration:
  status: error
  name: CMS Configuration
  monitorInterval: 10
  properties:
    property:
      name: filename
      value: /Node/var/tomcat/logs/gentics.log
  appenders:
    Console:
      name: STDOUT
      target: SYSTEM_OUT
      PatternLayout:
        Pattern: "%d [%t] %-5p %c - %m%n"
    RollingFile:
      name: rollingFile
      fileName: ${filename}
      filePattern: ${filename}.%d{yyyy-MM-dd}.gz
      PatternLayout:
        Pattern: "%d [%t] %-5p %c - %m%n"
      Policies:
        TimeBasedTriggeringPolicy:
          interval: 1
          modulate: true
      DefaultRollOverStrategy:
          max: 30
  Loggers:
    Root:
      level: error
      AppenderRef:
        -
          ref: rollingFile
        -
          ref: STDOUT

Gentics CMS Documentation