Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: New uploads link

...

To fix a problem, we may need a wide range of information about your system as well as various logs. The section below explains how to collect such information.

In this section:

Table of Contents
maxLevel3
minLevel2

Anchor
hang
hang

Hangs and Thread Dumps

...

  • if you need server thread dump and the server is run from console, press Ctrl+Break in the console window (this will not work for agent, since it's console belongs to launcher process).
  • if JDK 1.6 is used, use jstack <pid_of_java_process> command (jstack is located in the "bin" directory of JDK installation).
  • you can also use TeamCity-bundled thread dump tool (can be found in agent's plugins). Run the command:

    Code Block
    
    <TeamCity agent>\plugins\stacktracesPlugin\bin\x86\JetBrains.TeamCity.Injector.exe <pid_of_java_process>
    

If the hanging process is run as a service, taking the thread dump is more complicated. You can try to run theagent or server process from a console and use one of the aforementioned approaches, or run a thread dumping tool using Microsoft PsExec.
Use the following command line to get the dump:

Code Block

psexec -u <user> -p <password> <full path to the util> <process pid> stacktrace <output file>

...

You can also use third-party GUI tool: AdaptJ StackTrace Utility.
It supports Windows, Linux or Mac OS X. Choose "Launch" on the page (if you have Java installed). When the application is started, select the process id via "Process > Select", then dump its thread dump with "Process > Thread Dump".

See also Server Performance section below.

Back to top

Anchor
oom
oom

OutOfMemory Problems

...

  • Determine what process encounters the error (the actual building process, the TeamCity server, or the TeamCity agent)
  • If you use x64 JVM, please consider using 32 bit JVM
  • Try to increase the memory for the process via '-Xmx' JVM option, like -Xmx512m. If the error message is "java.lang.OutOfMemoryError: PermGen space", the following option should be used instead: -XX:MaxPermSize=150m.
    The option needs to be passed to the process with problems:
  • If increasing memory size does not help, please get the memory dump and send it to us for further analysis. Please reduce the Xmx setting to normal before getting the dump (smaller snapshots are easier to analyze and easier to upload):
    • to get a memory dump (hprof file) when an OoutOfMemory error occurs, 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 home>/bin or <TeamCity Agent home>/bin);
    • archive the file and send it to us.

      Info

      Since TeamCity 5.1 you can dump memory snapshot right from the web UI: go to the Administration | Server Configuration | Diagnostics tab and click Dump Memory Snapshot.

Back to top

Anchor
vcs
vcs

Anchor
logging
logging

...

You can change the log4J configuration files while the server/agent is running. If it is possible (some log4j restrictions apply), the loggers will be reconfigured without process restart.

Back to top

Version Control Debug Logging

...

In general, to debug VCS problems we need information for jetbrains.buildServer.VCS Log4j category. So please enable it in the <TeamCity home>\conf\teamcity-server-log4j.xml and <BuildAgent home>\conf\teamcity-agent-log4j.xml files:

Code Block
xml
xml

<category name="jetbrains.buildServer.VCS" additivity="false">
    <appender-ref ref="ROLL.VCS"/>
    <appender-ref ref="CONSOLE-ERROR"/>
    <priority value="DEBUG"/>
</category>

...

First, please enable generic VCS debug logging, as described above.

Uncomment SVN-related parts (SVN.LOG appender and javasvn.output category) of Log4j configuration file on server and on agent (if agent-side checkout is used). The log will be saved to the logs/teamcity-svn.log file. Generic VCS log should be also taken from logs/teamcity-vcs.log

...

Agent log will contain the line "Patch is saved to file ${file.name}"
Get the file and provide it with the problem description.

Back to top

Anchor
remote
remote

Remote Run Problems

The changes that are sent form the IDE to the server on a remote run can be retrieved from server's .BuildServer\system\changes directory. Locate the <change_number>.changes file that corresponds to your change (you can pick the latest number available or deduce the from the URL of the change form the web UI).
The file contains the patch in the binary form. Please provide it with the problem description.

Back to top

Anchor
serverperformance
serverperformance

...

  • after server startup wait for some time to allow it to "warm up". This can take from 5 to 20 minutes depending on the data volume that TeamCity stores.
  • when CPU usage increase is found on the server, please try to indicate what actions cause the load
  • start CPU profiling and repeat the action several times (5 - 10)
  • capture the snapshot
  • archive the snapshot and send it to us including description of the actions that cause CPU load

Back to top

Logging in TeamCity Visual Studio plugin

...

  1. Close all instances of Microsoft Visual Studio.
  2. Open <username-profile-folder>\Local Settings\Temp\JetLogs folder.
  3. Delete all of the files in this folder.
  4. Restart Microsoft Visual Studio.
  5. Open a solution.
  6. Try to log in to TeamCity.
  7. Close Microsoft Visual Studio.
  8. Navigate back to the <username-profile-folder>\Local Settings\Temp\JetLogs folder. All of the files that were created are logs.

Back to top

Anchor
sendingLargeFiles
sendingLargeFiles

...

To enable tracing for the plugin, run Eclipse IDE with the -debug <filename> program argument. The <filename> portion of the program argument is a properties file containing key-value pairs. Name of each property corresponds to the plugin module and value is either 'true' (to enable debug) or 'false'. Here is an example of enabling most common tracing options:

Code Block

jetbrains.teamcity.core/debug = true
jetbrains.teamcity.core/debug/communications = false
jetbrains.teamcity.core/debug/ui = true
jetbrains.teamcity.core/debug/vcs = true
jetbrains.teamcity.core/debug/vcs/detail = true
jetbrains.teamcity.core/debug/parser = true
jetbrains.teamcity.core/debug/platform = true
jetbrains.teamcity.core/debug/teamcity = true
jetbrains.teamcity.core/perfomance/vcs = true
jetbrains.teamcity.core/perfomance/teamcity = true

Read more about Eclipse Debug mode Gathering Information About Your Plug-in and built-in Eclipse help.

Back to top

Sending Information to the Developers

...

If 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. If you receive permission denied error on upload attempt, please rename the file.com.

You can also send small files via email: teamcity-feedback@jetbrains.com Please do not forget to mention your TeamCity version and environment

Back to top