Error in build agent and MessageBox

This morning I had this error with TeamCity 5.0.1 on a Windows XP agent, see screenshot.

I have some strange things in agent logs :

[2010-01-08 07:20:53,779]   INFO - nt.win32.DumpDotNetProcessList - Emumerating .NET processes command: "C:\Program Files\TeamCity\buildAgent-src2\bin\..\plugins\stacktracesPlugin\bin\x86\JetBrains.TeamCity.Injector.DotNet.x86.exe" /processes
[2010-01-08 07:22:23,985]   WARN - nt.win32.DumpDotNetProcessList - Injector Start dump stacktraces: "C:\Program Files\TeamCity\buildAgent-src2\bin\..\plugins\stacktracesPlugin\bin\x86\JetBrains.TeamCity.Injector.DotNet.x86.exe" /processes
[2010-01-08 07:22:23,985]   WARN - nt.win32.DumpDotNetProcessList - Injector result code: -1
[2010-01-08 07:22:23,985]   WARN - nt.win32.DumpDotNetProcessList - Injector stdoutput:  
[2010-01-08 07:22:23,985]   WARN - nt.win32.DumpDotNetProcessList - Injector stderror :  
[2010-01-08 07:22:23,985]   INFO - .agent.win32.Win32DoThreadDump - Dump stacktrace for bash.exe pid=3840
[2010-01-08 07:22:24,141]   INFO - .win32.DumpProcessCallInjector - Injector Start dump stacktraces: "C:\Program Files\TeamCity\buildAgent-src2\bin\..\plugins\stacktracesPlugin\bin\x86\JetBrains.TeamCity.Injector.exe" 3840 cmdLine F:\TeamCity\temp\src2\agentTmp\teamCity.cmdLine.1262931744125.540.output
[2010-01-08 07:22:24,814]   INFO - .win32.DumpProcessCallInjector - Injector result code: 0
[2010-01-08 07:22:24,861]   INFO - acktraces.agent.nix.JdkLocator - Looking for JSTACK in agent-running jvm...
[2010-01-08 07:22:24,876]   INFO - acktraces.agent.nix.JdkLocator - Lookup for JSTACK. Found: jstack.exe
[2010-01-08 07:22:24,876]   INFO - tacktraces.agent.nix.JStackRun - jstack call: jstack.exe 3840
[2010-01-08 07:22:24,876]   INFO - in32JavaJStackOrStacktraceCall - Failed to call jstack JStack failed with code -1

Error output:
Make sure you use JDK 1.6+
[2010-01-08 07:22:24,876]   INFO - .win32.DumpProcessCallInjector - Injector Start dump stacktraces: "C:\Program Files\TeamCity\buildAgent-src2\bin\..\plugins\stacktracesPlugin\bin\x86\JetBrains.TeamCity.Injector.exe" 3840 stacktrace F:\TeamCity\temp\src2\agentTmp\teamCity.stacktrace.1262931744829.591.output
[2010-01-08 07:22:25,486]  ERROR - .win32.DumpProcessCallInjector - Injector Start dump stacktraces: "C:\Program Files\TeamCity\buildAgent-src2\bin\..\plugins\stacktracesPlugin\bin\x86\JetBrains.TeamCity.Injector.exe" 3840 stacktrace F:\TeamCity\temp\src2\agentTmp\teamCity.stacktrace.1262931744829.591.output
[2010-01-08 07:22:25,486]  ERROR - .win32.DumpProcessCallInjector - Injector result code: -68
[2010-01-08 07:22:25,486]  ERROR - .win32.DumpProcessCallInjector - Injector stdoutput: TeamCity Java Stacktrace utility. Copyright (C) JetBrains s.r.o. 2007-2009
[2010-01-08 07:22:25,486]  ERROR - .win32.DumpProcessCallInjector - Injector stderror :  
[2010-01-08 07:22:25,830]   INFO - rocesses.ProcessTreeTerminator - Use jetbrains.buildServer.processes.ProcessTreeTerminatorWindows
[2010-01-08 07:22:25,877]   INFO - processes.VisitableProcessTree - Visited process: PID: 3048 PPID: 2492 CMD: JetBrains.TeamCity.Injecto...
[2010-01-08 07:22:25,877]   INFO - processes.VisitableProcessTree - Visited process: PID: 5004 PPID: 3048 CMD: vsjitdebugger.exe
[2010-01-08 07:22:25,877]   INFO - processes.VisitableProcessTree - Visited process: PID: 3840 PPID: 2492 CMD: bash.exe
[2010-01-08 07:22:25,877]   INFO - .ProcessTreeTerminatorImplBase - Kill process pid=3048 cmd=JetBrains.TeamCity.Injector.DotNet.x86.exe
[2010-01-08 07:22:25,877]   INFO - .ProcessTreeTerminatorImplBase - Kill process pid=5004 cmd=vsjitdebugger.exe
[2010-01-08 07:22:25,877]   INFO - .ProcessTreeTerminatorImplBase - Kill process pid=3840 cmd=bash.exe
[2010-01-08 07:22:25,893]   INFO - GenericCommandLineBuildProcess - Killed all children processes
[2010-01-08 07:22:26,034]   INFO - nner2.OsProcessHandlerListener -

It seems that buildAgent is still running. Should I worry ?

Gérald



Attachment(s):
errorTC.png
2 comments
Comment actions Permalink

The error means that someone has tried to view thread dump of a build, but utility failed to obtain it. Agent itself is ok, because utility which takes thread dump from the build is spawned in separate process. It seems this utility crashed, if you submit a bug report with this log and screenshot we will try to investigate this problem.

0
Comment actions Permalink

Le 08/01/2010 23:57, Pavel Sher a ecrit :

The error means that someone has tried to view thread dump of a build, but utility failed to obtain it. Agent itself is ok, because utility which takes thread dump from the build is spawned in separate process. It seems this utility crashed, if you submit a bug report with this log and screenshot we will try to investigate this problem.


Someone, you mean a user ?

What is the thread dump of a build?

This morning, I have a build that is running since friday evening, on a
Linux box, and that cannot be stop, I see this in the logs :

Failed to locate jps tool. No thread dump information is available
Could it be related ?


Gérald

0

Please sign in to leave a comment.