Transport Service and Content Deployer logs
Both the log files and the configuration files of the Transport Service and the Content Deployer can help you zoom in on publishing problems. 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 the 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
DEBUGto reveal more than just standard log information. - Set your log level to
TRACEfor highly detailed log information (note that the Content Deployer does not log much information). - As a last resort, define a new
loggerelement, set itsnameattribute to org.hibernate, and set therefattribute of theappender-refelement 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.
- Set your log level to
- 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
TransportSummaryelement that is not indented.