Documentation Center

Transport Service and Content Deployer logs

Configure and analyze your log files to zoom in on publishing problems related to the Transport Service or Content Deployer.

Logging to one file

Ensure that the Logback loggers used by Transport Service (on the Content Manager server) and by the Content Deployer (on the Content Delivery side) log to the same file. This makes it easier to retrace the interaction between the two.

Log levels

In your logback.xml configuration files:

  • Set your log level to DEBUG to reveal more than just standard log information.
  • Set your log level to TRACE for highly detailed log information (note that the Content Deployer does not log much information).
  • As a last resort, define a new logger element, set its name attribute to org.hibernate, and set the ref attribute of the appender-ref element to a unique string. This type of logging creates humongous logs, detailing all database interactions through the Object Relation Model (ORM), but it does provide the most context.
Log parser
Consider building or buying a log parser, to make it easier to scan your logs.
Metadata XML
When the Content Deployer initializes, it writes important metadata (as XML) to the log file. Check for this metadata.
TransportSummary
Check the log for a TransportSummary element that is not indented.