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 |
---|---|
| General build agent log |
|
|
| VCS-related logging (for checkout mode "Automatically on agent") |
| log of the build agent upgrade (logged by the upgrading process) |
| log of the agent's monitoring/launching process |
| (only present when the agent is run as Windows service or by Java Service Wrapper) output of the process build agent launching process |
Generic Debug Logging
To enable general debug logging on agent, change "jetbrains.buildServer" category logging priority in the <agent home>/conf/teamcity-agent-log4j.xml
file:
Then, see teamcity-agent.log*
files To turn debug mode off, make the line "<priority value="INFO"/>
".
VCS Debug Logging
To enable detailed VCS logging on agent, change VCS category logging priority in the <agent home>/conf/teamcity-agent-log4j.xml
file:
Then, see teamcity-vcs.log*
files To turn debug mode off, make the line "<priority value="INFO"/>
".
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.
Then, see teamcity-xmlrpc.log
To turn it off, make the line "<priority value="INFO"/>
".
Advanced Logging Configuration
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 section on how to pass the options.
For additional option on logging tweaking please consult TeamCity Server Logs section.