Viewing Build Agent Logs

To analyze agent-specific cases, there are internal log files saved by the TeamCity agent process into <TeamCity agent home>/logs directory on the agent machine.

When the agent is connected to TeamCity server, you can browse the logs in UI, on Agent Logs tab for an agent.

Log Files

TeamCity uses Log4J for internal logging of events. Default build agent Log4J configuration file is <agent home>/conf/teamcity-agent-log4j.xml See the comments in the file for enabling DEBUG mode: you will need to increase the value in "<param name="maxBackupIndex"..." node and insert "<priority value="DEBUG"/>" nodes into "<category" elements. Build agent logs are placed into <agent home>/logs directory.

File name	Description
`teamcity-agent.log`	General build agent log
`teamcity-build.log`	`stdout` and `stderr` output of builds run by the agent
`upgrade.log`	log of the build agent upgrade (logged by the upgrading process)
`launcher.log`	log of the agent's monitoring/launching process
`wrapper.log`	(only present when the agent is run as Windows service or by Java Service Wrapper) output of the process build agent launching process

You can configure location of the logs by altering the value of teamcity_logs property (passed to JVM via -D option). You can also change Log4J configuration file location by changing value of log4j.configuration property. See corresponding documentation Configuring Build Agent Startup Properties on how to pass the options.

For additional option on logging tweaking please consult TeamCity Server Logs section.

Specific Debug Logging

To get dump of the data sent from the agent to the server, enable agent XML-RPC log, by uncommenting the line below in the <agent home>/conf/teamcity-agent-log4j.xml file.

  <category name="jetbrains.buildServer.XMLRPC">
    <!--<priority value="DEBUG"/>-->
    <appender-ref ref="ROLL.XMLRPC"/>
  </category>

Then, see teamcity-xmlrpc.log To turn it off, make the line "<priority value="INFO"/>".

Last modified: 20 April 2023