...
To fix a problem, we may need a wide range of information about your system and various logs. The information below will help explain how to collect this information from your system when you are having trouble.
In this section:
- Logging
- Hangs and thread dumps
- OutOfMemory problems
- Version Control Debug Logging
- Patch Application Problems
- Remote Run Problems
- Server Performance
- #Sending Large Files to the Developers
| Anchor | ||||
|---|---|---|---|---|
|
Logging
...
Before reproducing the problem it makes sense to enable 'DEBUG' log level for TeamCity classes. To do it, change the following section in teamcity-(server|agent)-log4j.xml files:
| Code Block | ||||
|---|---|---|---|---|
| ||||
<category name="jetbrains.buildServer">
<priority value="DEBUG"/>
<appender-ref ref="ROLL"/>
</category>
|
...
In GUI mode, you can also use AdaptJ StackTrace Utility under Windows, Linux or Mac OS X to get the stacktrace of the process even if it runs without console.
See also Server Performance section below.
| Anchor | ||||
|---|---|---|---|---|
|
...
- determine what process encounters the error (the actual building process, the TeamCity server, or the TeamCity agent)
- try to increase the memory for the process via
'-Xmx'JVM option, like -Xmx512m. The option needs to be passed to the process with problems:- if it is the building process itself, use "JVM Command Line Parameters" settings in the build runner. e.g. Inspections builds may specifically need to increase the parameter;
- if it is TeamCity server, modify runAll.* script or (if server is run as Windows service), use TeamCity/bin/tomcat6w.exe //ES//TeamCity (see more);
- if it is TeamCity build agent, modify agent.* script
- if increasing memory does not help, please get the memory dump and send it to us for further analysis:
- to get a memory dump (hprof file) when an OOM error occurs, please add the following JVM option (works for JDK 1.5.0_07+):
-XX:+HeapDumpOnOutOfMemoryError - when OOM error occurs next time, java_xxx.hprof file will be created in the process startup directory (TeamCity/bin or buildAgent/bin);
- please archive the file and send it to us.
- to get a memory dump (hprof file) when an OOM error occurs, please add the following JVM option (works for JDK 1.5.0_07+):
| Anchor | ||||
|---|---|---|---|---|
|
Version Control Debug Logging
...
To turn on debug logging of the SVNkit library on the agent (only relevant for agent-side checkout mode) uncomment the following lines in the
<agent home>\conf\teamcity-agent-log4j.xml file:
| Code Block | ||||
|---|---|---|---|---|
| ||||
<category name="javasvn.output">
<priority value="DEBUG"/>
<appender-ref ref="SVN.LOG"/>
</category>
|
...
Files under 5Mb in size can be attached right into the tracker issue.
If you do not want the content of the files be publicly available or the file is over 5 Mb, you can upload the archived files to ftpvia https://ftpuploads.intellijjetbrains.net/.uploads and let us know the exact file name.com.