Upgrade Problems from 1.2 to 2.0
Hi,
Today I upgraded from 1.2. to 2.0. When trying to login (after I press
the login button) the page hangs and the server does not respond anymore.
When I have a look at the server, I see that the tomcat5.exe process is
constantly at 50%. I think it takes all resources of one processor,
because it is a dual processor machine.
After I stop the TeamCity agent and only start the web server,
everything works alright - so it has something to do with the agent.
Unfortunately I can't see anything useful in the logs. The only thing is
the following exception:
INFO | jvm 1 | 2007/04/16 13:47:43 | c:\TeamCity\jre\bin\java -ea
-Xmx384m -Dlog4j.configuration=file:../conf/teamcity-agent-log4j.xml
-Dteamcity_logs=../logs/ -classpath
C:\TeamCity\buildAgent\lib\activation.jar;C:\TeamCity\buildAgent\lib\agentInstaller-UI.jar;C:\TeamCity\buildAgent\lib\agentInstaller.jar;C:\TeamCity\buildAgent\lib\annotations.jar;C:\TeamCity\buildAgent\lib\buildServerAgent.jar;C:\TeamCity\buildAgent\lib\buildServerCommon.jar;C:\TeamCity\buildAgent\lib\buildServerCommonRuntime.jar;C:\TeamCity\buildAgent\lib\buildServerMessages.jar;C:\TeamCity\buildAgent\lib\buildServerRemoteServerProxy.jar;C:\TeamCity\buildAgent\lib\buildServerRuntimeUtil.jar;C:\TeamCity\buildAgent\lib\buildServerServerLogging.jar;C:\TeamCity\buildAgent\lib\buildServerServerModel.jar;C:\TeamCity\buildAgent\lib\buildServerXmlRpcWrapper.jar;C:\TeamCity\buildAgent\lib\commons-beanutils-core.jar;C:\TeamCity\buildAgent\lib\commons-codec-1.3.jar;C:\TeamCity\buildAgent\lib\commons-collections-3.2.jar;C:\TeamCity\buildAgent\lib\commons-dbcp-1.2.1.jar;C:\TeamCity\buildAgent\lib\commons-httpclient-3.0-rc4.jar;C:\TeamCity\buildAgent\lib\commons-logging.jar;C:\TeamCity\
buildAgent\lib\commons-pool-1.3.jar;C:\TeamCity\buildAgent\lib\idea-settings.jar;C:\TeamCity\buildAgent\lib\ivy-1.4.1.jar;C:\TeamCity\buildAgent\lib\jdk-searcher.jar;C:\TeamCity\buildAgent\lib\jdom.jar;C:\TeamCity\buildAgent\lib\JNIWrap.jar;C:\TeamCity\buildAgent\lib\junit-4.1.jar;C:\TeamCity\buildAgent\lib\launcher.jar;C:\TeamCity\buildAgent\lib\log4j-1.2.12.jar;C:\TeamCity\buildAgent\lib\mail.jar;C:\TeamCity\buildAgent\lib\nanocontainer-1.0-RC-1.jar;C:\TeamCity\buildAgent\lib\openapi.jar;C:\TeamCity\buildAgent\lib\patches-impl.jar;C:\TeamCity\buildAgent\lib\patches.jar;C:\TeamCity\buildAgent\lib\picocontainer-1.2.jar;C:\TeamCity\buildAgent\lib\resources.jar;C:\TeamCity\buildAgent\lib\resources_en.jar;C:\TeamCity\buildAgent\lib\shaj-0.5.jar;C:\TeamCity\buildAgent\lib\trove4j.jar;C:\TeamCity\buildAgent\lib\utils.jar;C:\TeamCity\buildAgent\lib\winpack.jar;C:\TeamCity\buildAgent\lib\xmlrpc-2.0.1.jar;C:\TeamCity\buildAgent\lib\xpp3_min-1.1.3.4.M.jar;C:\TeamCity\buildAgent\lib\xs
tream-1.2.1.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-antlr.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-apache-bcel.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-apache-bsf.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-apache-log4j.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-apache-oro.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-apache-regexp.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-apache-resolver.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-commons-logging.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-commons-net.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-icontract.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-jai.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-javamail.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-jdepend.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-jmf.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-jsch.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-junit.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-launcher.jar;C:\TeamCi
ty\buildAgent\plugins\ant\lib\ant-netrexx.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-nodeps.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-starteam.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-stylebook.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-swing.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-testutil.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-trax.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-vaj.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-weblogic.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-xalan1.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant-xslp.jar;C:\TeamCity\buildAgent\plugins\ant\lib\ant.jar;C:\TeamCity\buildAgent\plugins\ant\lib\junit-3.8.1.jar;C:\TeamCity\buildAgent\plugins\ant\lib\xercesImpl.jar;C:\TeamCity\buildAgent\plugins\ant\lib\xml-apis.jar;C:\TeamCity\buildAgent\plugins\antPlugin\lib\buildServerAntRunner.jar;C:\TeamCity\buildAgent\plugins\antPlugin\lib\buildServerAntRuntime.jar;C:\TeamCity\buildAgent\plugins\antPlugin\lib\buildServ
erAntServerLogging.jar;C:\TeamCity\buildAgent\plugins\coveragePlugin\lib\buildServerCoverageAgent.jar;C:\TeamCity\buildAgent\plugins\coveragePlugin\lib\emma.jar;C:\TeamCity\buildAgent\plugins\cvsAgent\lib\buildServerCvsAgentPlugin.jar;C:\TeamCity\buildAgent\plugins\cvsAgent\lib\cvs_util.jar;C:\TeamCity\buildAgent\plugins\cvsAgent\lib\javacvs.jar;C:\TeamCity\buildAgent\plugins\cvsAgent\lib\maverick-sftp.jar;C:\TeamCity\buildAgent\plugins\cvsAgent\lib\maverick-ssh1.jar;C:\TeamCity\buildAgent\plugins\cvsAgent\lib\maverick-ssh2.jar;C:\TeamCity\buildAgent\plugins\cvsAgent\lib\maverick.jar;C:\TeamCity\buildAgent\plugins\cvsAgent\lib\resources_en.jar;C:\TeamCity\buildAgent\plugins\cvsAgent\lib\smartcvs-src.jar;C:\TeamCity\buildAgent\plugins\cvsAgent\lib\sshtools-ant.jar;C:\TeamCity\buildAgent\plugins\cvsAgent\lib\sshtools-cipher.jar;C:\TeamCity\buildAgent\plugins\cvsAgent\lib\sshtools-net.jar;C:\TeamCity\buildAgent\plugins\cvsAgent\lib\sshtools-publickey.jar;C:\TeamCity\buildAgent\p
lugins\cvsAgent\lib\sshtools-scp.jar;C:\TeamCity\buildAgent\plugins\cvsAgent\lib\sshtools-sftp.jar;C:\TeamCity\buildAgent\plugins\cvsAgent\lib\sshtools-util.jar;C:\TeamCity\buildAgent\plugins\cvsAgent\lib\sshtools-zlib.jar;C:\TeamCity\buildAgent\plugins\dotnetPlugin\lib\dotNet-searcher.jar;C:\TeamCity\buildAgent\plugins\dotnetPlugin\lib\dotNetCommonRuntime.jar;C:\TeamCity\buildAgent\plugins\dotnetPlugin\lib\msBuildRunner.jar;C:\TeamCity\buildAgent\plugins\dotnetPlugin\lib\nantRunner.jar;C:\TeamCity\buildAgent\plugins\dotnetPlugin\lib\solution2003Runner.jar;C:\TeamCity\buildAgent\plugins\dotnetPlugin\lib\solution2005Runner.jar;C:\TeamCity\buildAgent\plugins\duplicatePlugin\lib\buildServerDuplicateRunner.jar;C:\TeamCity\buildAgent\plugins\duplicatePlugin\lib\buildServerDuplicateServer.jar;C:\TeamCity\buildAgent\plugins\idea\lib\alloy.jar;C:\TeamCity\buildAgent\plugins\idea\lib\annotations.jar;C:\TeamCity\buildAgent\plugins\idea\lib\asm-commons.jar;C:\TeamCity\buildAgent\plugins
\idea\lib\asm.jar;C:\TeamCity\buildAgent\plugins\idea\lib\boot.jar;C:\TeamCity\buildAgent\plugins\idea\lib\bootstrap.jar;C:\TeamCity\buildAgent\plugins\idea\lib\cglib-nodep-2.1_3.jar;C:\TeamCity\buildAgent\plugins\idea\lib\commons-codec-1.3.jar;C:\TeamCity\buildAgent\plugins\idea\lib\commons-collections.jar;C:\TeamCity\buildAgent\plugins\idea\lib\emma-agent.jar;C:\TeamCity\buildAgent\plugins\idea\lib\emma.jar;C:\TeamCity\buildAgent\plugins\idea\lib\extensions.jar;C:\TeamCity\buildAgent\plugins\idea\lib\forms_rt.jar;C:\TeamCity\buildAgent\plugins\idea\lib\icons.jar;C:\TeamCity\buildAgent\plugins\idea\lib\idea.jar;C:\TeamCity\buildAgent\plugins\idea\lib\idea_rt.jar;C:\TeamCity\buildAgent\plugins\idea\lib\j2ee.jar;C:\TeamCity\buildAgent\plugins\idea\lib\jasper2_rt.jar;C:\TeamCity\buildAgent\plugins\idea\lib\javac2.jar;C:\TeamCity\buildAgent\plugins\idea\lib\javaee.jar;C:\TeamCity\buildAgent\plugins\idea\lib\jaxen.jar;C:\TeamCity\buildAgent\plugins\idea\lib\jdom.jar;C:\TeamCity\b
uildAgent\plugins\idea\lib\jgoodies-forms.jar;C:\TeamCity\buildAgent\plugins\idea\lib\jsf-api.jar;C:\TeamCity\buildAgent\plugins\idea\lib\jsp-api.jar;C:\TeamCity\buildAgent\plugins\idea\lib\junit-4.0.jar;C:\TeamCity\buildAgent\plugins\idea\lib\junit.jar;C:\TeamCity\buildAgent\plugins\idea\lib\log4j.jar;C:\TeamCity\buildAgent\plugins\idea\lib\microba.jar;C:\TeamCity\buildAgent\plugins\idea\lib\nanoxml-2.2.3.jar;C:\TeamCity\buildAgent\plugins\idea\lib\openapi.jar;C:\TeamCity\buildAgent\plugins\idea\lib\oromatcher.jar;C:\TeamCity\buildAgent\plugins\idea\lib\picocontainer.jar;C:\TeamCity\buildAgent\plugins\idea\lib\resolver.jar;C:\TeamCity\buildAgent\plugins\idea\lib\resources.jar;C:\TeamCity\buildAgent\plugins\idea\lib\resources_en.jar;C:\TeamCity\buildAgent\plugins\idea\lib\saxpath.jar;C:\TeamCity\buildAgent\plugins\idea\lib\servlet-api.jar;C:\TeamCity\buildAgent\plugins\idea\lib\trove4j.jar;C:\TeamCity\buildAgent\plugins\idea\lib\trove4j_src.jar;C:\TeamCity\buildAgent\plugins\
idea\lib\velocity.jar;C:\TeamCity\buildAgent\plugins\idea\lib\xerces.jar;C:\TeamCity\buildAgent\plugins\idea\lib\xml-apis.jar;C:\TeamCity\buildAgent\plugins\idea\lib\xmlrpc-2.0.jar;C:\TeamCity\buildAgent\plugins\idea\lib\xstream.jar;C:\TeamCity\buildAgent\plugins\inspectionPlugin\lib\buildServerInspectionRunner.jar;C:\TeamCity\buildAgent\plugins\inspectionPlugin\lib\buildServerInspectionServerLogging.jar;C:\TeamCity\buildAgent\plugins\iprPlugin\lib\asm-commons.jar;C:\TeamCity\buildAgent\plugins\iprPlugin\lib\asm.jar;C:\TeamCity\buildAgent\plugins\iprPlugin\lib\bd-ant-extensions.jar;C:\TeamCity\buildAgent\plugins\iprPlugin\lib\buildGenerator.jar;C:\TeamCity\buildAgent\plugins\iprPlugin\lib\buildServerIprRunner.jar;C:\TeamCity\buildAgent\plugins\iprPlugin\lib\javac2.jar;C:\TeamCity\buildAgent\plugins\iprPlugin\lib\jgoodies-forms.jar;C:\TeamCity\buildAgent\plugins\maven-2.0.6\lib\maven-core-2.0.6-uber.jar;C:\TeamCity\buildAgent\plugins\mavenPlugin\lib\buildServerMaven2Agent.jar;
C:\TeamCity\buildAgent\plugins\mavenPlugin\lib\maven2AgentRuntime.jar;C:\TeamCity\buildAgent\plugins\mavenPlugin\lib\maven2AgentRuntimeCommon.jar;C:\TeamCity\buildAgent\plugins\svnAgent\lib\buildServerSvnAgentPlugin.jar;C:\TeamCity\buildAgent\plugins\svnAgent\lib\ganymed.jar;C:\TeamCity\buildAgent\plugins\svnAgent\lib\svnkit-cli.jar;C:\TeamCity\buildAgent\plugins\svnAgent\lib\svnkit-javahl.jar;C:\TeamCity\buildAgent\plugins\svnAgent\lib\svnkit.jar;C:\TeamCity\buildAgent\plugins\svnAgent\lib\svnkitsrc.zip;C:\TeamCity\buildAgent\plugins\testNGPlugin\lib\testng-runtime.jar;C:\TeamCity\buildAgent\plugins\testNGPlugin\lib\testNGAntExtension.jar
jetbrains.buildServer.agent.AgentMain -file ../conf/buildAgent.properties
INFO | jvm 1 | 2007/04/16 13:47:43 | java.util.NoSuchElementException
Can you please tell me how to fix that problem?
Cheers,
Stephan
Please sign in to leave a comment.
Now I did an additional test...
.. 04/16/2007 12:16 PM bin 04/16/2007 12:16 PM conf 04/16/2007 12:15 PM 2,590 JavaServiceWrapperLicense.txt 04/16/2007 12:16 PM lib 1 File(s) 2,590 bytes Directory of C:\TeamCity\buildAgent\launcher\bin 04/16/2007 12:16 PM . 04/16/2007 12:16 PM .. 04/16/2007 12:15 PM 140,198 TeamCityAgentService-linux-ppc-64 04/16/2007 12:15 PM 99,401 TeamCityAgentService-linux-x86-32 04/16/2007 12:15 PM 111,027 TeamCityAgentService-linux-x86-64 04/16/2007 12:15 PM 114,052 TeamCityAgentService-macosx-ppc-32 04/16/2007 12:15 PM 233,604 TeamCityAgentService-macosx-universal-32 04/16/2007 12:15 PM 112,536 TeamCityAgentService-solaris-sparc-32 04/16/2007 12:15 PM 148,512 TeamCityAgentService-solaris-sparc-64 04/16/2007 12:15 PM 110,992 TeamCityAgentService-solaris-x86-32 04/16/2007 12:15 PM 204,800 TeamCityAgentService-windows-x86-32.exe 9 File(s) 1,275,122 bytes Directory of C:\TeamCity\buildAgent\launcher\conf 04/16/2007 12:16 PM . 04/16/2007 12:16 PM .. 04/16/2007 12:15 PM 4,457 wrapper.conf 1 File(s) 4,457 bytes Directory of C:\TeamCity\buildAgent\launcher\lib 04/16/2007 12:16 PM . 04/16/2007 12:16 PM ]]> ..Additionally to the Upgrade described in 'Upgrading using the Windows Installer' (see http://www.jetbrains.net/confluence/display/TCD/Upgrade), I also tried to manually upgrade the BuildAgent, because I've seen there was a launcher.latest directory in my Agent directory.
I did that like described on the above mentioned web page, but now I directly get an exception when trying to start the BuildAgent service:
STATUS | wrapper | 2007/04/16 15:10:03 | --> Wrapper Started as Service
STATUS | wrapper | 2007/04/16 15:10:03 | Launching a JVM...
FATAL | wrapper | 2007/04/16 15:10:03 | Unable to execute Java command. The system cannot find the file specified. (0x2)
FATAL | wrapper | 2007/04/16 15:10:03 | "java" -Djava.library.path="../launcher/lib;../launcher/bin" -classpath "../launcher/lib/wrapper.jar;../launcher/lib/launcher.jar" -Dwrapper.key="qlDraDn1RfwyDkog" -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=6580 -Dwrapper.version="3.2.3" -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp jetbrains.buildServer.agent.StandAloneLauncher -ea -Xmx384m -Dlog4j.configuration=file:../conf/teamcity-agent-log4j.xml -Dteamcity_logs=../logs/ jetbrains.buildServer.agent.AgentMain -file ../conf/buildAgent.properties
FATAL | wrapper | 2007/04/16 15:10:03 | Critical error: wait for JVM process failed
The files that are in my launcher directory, are listed blow. Please help!
Stephan
Directory of C:\TeamCity\buildAgent\launcher
04/16/2007 12:16 PM . 04/16/2007 12:16 PM
04/16/2007 12:15 PM 23,587 launcher.jar
04/16/2007 12:15 PM 23,839 libwrapper-linux-ppc-64.so
04/16/2007 12:15 PM 11,887 libwrapper-linux-x86-32.so
04/16/2007 12:15 PM 15,248 libwrapper-linux-x86-64.so
04/16/2007 12:15 PM 15,400 libwrapper-macosx-ppc-32.jnilib
04/16/2007 12:15 PM 35,332 libwrapper-macosx-universal-32.jnilib
04/16/2007 12:15 PM 13,760 libwrapper-solaris-sparc-32.so
04/16/2007 12:15 PM 21,032 libwrapper-solaris-sparc-64.so
04/16/2007 12:15 PM 12,572 libwrapper-solaris-x86-32.so
04/16/2007 12:15 PM 81,920 wrapper-windows-x86-32.dll
04/16/2007 12:15 PM 83,820 wrapper.jar
11 File(s) 338,397 bytes
Stephan Brenner wrote:
Hello Stephan,
Try to reinstall build agent (remove old version and install new). Ask
uninstaller to preserve build agent configuration and work directory.
--
Pavel Sher
"Stephan Brenner" <no_reply@enteo.com> wrote in message
news:evvtt0$pms$1@is.intellij.net...
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>> Hi,
>>
>> Today I upgraded from 1.2. to 2.0. When trying to login (after I press
>> the login button) the page hangs and the server does not respond anymore.
>>
>> When I have a look at the server, I see that the tomcat5.exe process is
>> constantly at 50%. I think it takes all resources of one processor,
>> because it is a dual processor machine.
>>
>> After I stop the TeamCity agent and only start the web server, everything
>> works alright - so it has something to do with the agent.
>>
>> Unfortunately I can't see anything useful in the logs. The only thing is
>> the following exception:
>> INFO | jvm 1 | 2007/04/16 13:47:43 |
>> c:\TeamCity\jre\bin\java -ea -Xmx384m -Dlog4j.configuration=file:../conf/teamcity-agent-log4j.xml
>> -Dteamcity_logs=../logs/ -classpath ...
>> jetbrains.buildServer.agent.AgentMain -file ../conf/buildAgent.properties
>> INFO | jvm 1 | 2007/04/16 13:47:43 |
>> java.util.NoSuchElementException
>>
>> Can you please tell me how to fix that problem?
>>
>> Cheers,
>> Stephan
Hi Pavel,
I just tried that (called service.uninstall.bat and then executed agentInstaller.exe). After starting it, the tomcat5.exe process uses 50% of the CPU and the web site does not respond anymore. Without agent, the TC web site works well.
I additionally have to mention, that we only have one buildagent (runnning on the same machine as the TC web site).
Do you have any other ideas? Could it help to reset the DB (and how to do that)?
Cheers,
Stephan
Pavel Sher wrote:
>> Now I did an additional test...
.. >> 04/16/2007 12:16 PM bin >> 04/16/2007 12:16 PM conf >> 04/16/2007 12:15 PM 2,590 JavaServiceWrapperLicense.txt >> 04/16/2007 12:16 PM lib >> 1 File(s) 2,590 bytes >> >> Directory of C:\TeamCity\buildAgent\launcher\bin >> >> 04/16/2007 12:16 PM . >> 04/16/2007 12:16 PM .. >> 04/16/2007 12:15 PM 140,198 TeamCityAgentService-linux-ppc-64 >> 04/16/2007 12:15 PM 99,401 TeamCityAgentService-linux-x86-32 >> 04/16/2007 12:15 PM 111,027 TeamCityAgentService-linux-x86-64 >> 04/16/2007 12:15 PM 114,052 TeamCityAgentService-macosx-ppc-32 >> 04/16/2007 12:15 PM 233,604 >> TeamCityAgentService-macosx-universal-32 >> 04/16/2007 12:15 PM 112,536 >> TeamCityAgentService-solaris-sparc-32 >> 04/16/2007 12:15 PM 148,512 >> TeamCityAgentService-solaris-sparc-64 >> 04/16/2007 12:15 PM 110,992 TeamCityAgentService-solaris-x86-32 >> 04/16/2007 12:15 PM 204,800 >> TeamCityAgentService-windows-x86-32.exe >> 9 File(s) 1,275,122 bytes >> >> Directory of C:\TeamCity\buildAgent\launcher\conf >> >> 04/16/2007 12:16 PM . >> 04/16/2007 12:16 PM .. >> 04/16/2007 12:15 PM 4,457 wrapper.conf >> 1 File(s) 4,457 bytes >> >> Directory of C:\TeamCity\buildAgent\launcher\lib >> >> 04/16/2007 12:16 PM . >> 04/16/2007 12:16 PM .. >> 04/16/2007 12:15 PM 23,587 launcher.jar >> 04/16/2007 12:15 PM 23,839 libwrapper-linux-ppc-64.so >> 04/16/2007 12:15 PM 11,887 libwrapper-linux-x86-32.so >> 04/16/2007 12:15 PM 15,248 libwrapper-linux-x86-64.so >> 04/16/2007 12:15 PM 15,400 libwrapper-macosx-ppc-32.jnilib >> 04/16/2007 12:15 PM 35,332 >> libwrapper-macosx-universal-32.jnilib >> 04/16/2007 12:15 PM 13,760 libwrapper-solaris-sparc-32.so >> 04/16/2007 12:15 PM 21,032 libwrapper-solaris-sparc-64.so >> 04/16/2007 12:15 PM 12,572 libwrapper-solaris-x86-32.so >> 04/16/2007 12:15 PM 81,920 wrapper-windows-x86-32.dll >> 04/16/2007 12:15 PM 83,820 wrapper.jar >> 11 File(s) 338,397 bytes >> >> >> Stephan Brenner wrote: >>> Hi, >>> >>> Today I upgraded from 1.2. to 2.0. When trying to login (after I press >>> the login button) the page hangs and the server does not respond anymore. >>> >>> When I have a look at the server, I see that the tomcat5.exe process is >>> constantly at 50%. I think it takes all resources of one processor, >>> because it is a dual processor machine. >>> >>> After I stop the TeamCity agent and only start the web server, everything >>> works alright - so it has something to do with the agent. >>> >>> Unfortunately I can't see anything useful in the logs. The only thing is >>> the following exception: >>> INFO | jvm 1 | 2007/04/16 13:47:43 | >>> c:\TeamCity\jre\bin\java -ea -Xmx384m -Dlog4j.configuration=file:../conf/teamcity-agent-log4j.xml >>> -Dteamcity_logs=../logs/ -classpath ... >>> jetbrains.buildServer.agent.AgentMain -file ../conf/buildAgent.properties >>> INFO | jvm 1 | 2007/04/16 13:47:43 | >>> java.util.NoSuchElementException >>> >>> Can you please tell me how to fix that problem? >>> >>> Cheers, >>>]]> Stephan>>
>> Additionally to the Upgrade described in 'Upgrading using the Windows
>> Installer' (see http://www.jetbrains.net/confluence/display/TCD/Upgrade),
>> I also tried to manually upgrade the BuildAgent, because I've seen there
>> was a launcher.latest directory in my Agent directory.
>>
>> I did that like described on the above mentioned web page, but now I
>> directly get an exception when trying to start the BuildAgent service:
>> STATUS | wrapper | 2007/04/16 15:10:03 | --> Wrapper Started as Service
>> STATUS | wrapper | 2007/04/16 15:10:03 | Launching a JVM...
>> FATAL | wrapper | 2007/04/16 15:10:03 | Unable to execute Java command.
>> The system cannot find the file specified. (0x2)
>> FATAL | wrapper | 2007/04/16 15:10:03 |
>> "java" -Djava.library.path="../launcher/lib;../launcher/bin" -classpath
>> "../launcher/lib/wrapper.jar;../launcher/lib/launcher.jar" -Dwrapper.key="qlDraDn1RfwyDkog"
>> -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999
>> -Dwrapper.pid=6580 -Dwrapper.version="3.2.3" -Dwrapper.native_library="wrapper"
>> -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1
>> org.tanukisoftware.wrapper.WrapperSimpleApp
>> jetbrains.buildServer.agent.StandAloneLauncher -ea -Xmx384m -Dlog4j.configuration=file:../conf/teamcity-agent-log4j.xml
>> -Dteamcity_logs=../logs/ jetbrains.buildServer.agent.AgentMain -file
>> ../conf/buildAgent.properties
>> FATAL | wrapper | 2007/04/16 15:10:03 | Critical error: wait for JVM
>> process failed
>>
>> The files that are in my launcher directory, are listed blow. Please help!
>>
>> Stephan
>>
>>
>> Directory of C:\TeamCity\buildAgent\launcher
>>
>> 04/16/2007 12:16 PM . >> 04/16/2007 12:16 PM
Could you please send us teamcity-server.log and teamcity-agent.log?
--
Pavel Sher
"Stephan Brenner" <no_reply@enteo.com> wrote in message
news:f00234$ech$1@is.intellij.net...
>
>
>
>
>
>> Hello Stephan,
. >>> 04/16/2007 12:16 PM .. >>> 04/16/2007 12:16 PM bin >>> 04/16/2007 12:16 PM conf >>> 04/16/2007 12:15 PM 2,590 JavaServiceWrapperLicense.txt >>> 04/16/2007 12:16 PM lib >>> 1 File(s) 2,590 bytes >>> >>> Directory of C:\TeamCity\buildAgent\launcher\bin >>> >>> 04/16/2007 12:16 PM . >>> 04/16/2007 12:16 PM .. >>> 04/16/2007 12:15 PM 140,198 TeamCityAgentService-linux-ppc-64 >>> 04/16/2007 12:15 PM 99,401 TeamCityAgentService-linux-x86-32 >>> 04/16/2007 12:15 PM 111,027 TeamCityAgentService-linux-x86-64 >>> 04/16/2007 12:15 PM 114,052 >>> TeamCityAgentService-macosx-ppc-32 >>> 04/16/2007 12:15 PM 233,604 >>> TeamCityAgentService-macosx-universal-32 >>> 04/16/2007 12:15 PM 112,536 >>> TeamCityAgentService-solaris-sparc-32 >>> 04/16/2007 12:15 PM 148,512 >>> TeamCityAgentService-solaris-sparc-64 >>> 04/16/2007 12:15 PM 110,992 >>> TeamCityAgentService-solaris-x86-32 >>> 04/16/2007 12:15 PM 204,800 >>> TeamCityAgentService-windows-x86-32.exe >>> 9 File(s) 1,275,122 bytes >>> >>> Directory of C:\TeamCity\buildAgent\launcher\conf >>> >>> 04/16/2007 12:16 PM . >>> 04/16/2007 12:16 PM .. >>> 04/16/2007 12:15 PM 4,457 wrapper.conf >>> 1 File(s) 4,457 bytes >>> >>> Directory of C:\TeamCity\buildAgent\launcher\lib >>> >>> 04/16/2007 12:16 PM . >>> 04/16/2007 12:16 PM .. >>> 04/16/2007 12:15 PM 23,587 launcher.jar >>> 04/16/2007 12:15 PM 23,839 libwrapper-linux-ppc-64.so >>> 04/16/2007 12:15 PM 11,887 libwrapper-linux-x86-32.so >>> 04/16/2007 12:15 PM 15,248 libwrapper-linux-x86-64.so >>> 04/16/2007 12:15 PM 15,400 libwrapper-macosx-ppc-32.jnilib >>> 04/16/2007 12:15 PM 35,332 >>> libwrapper-macosx-universal-32.jnilib >>> 04/16/2007 12:15 PM 13,760 libwrapper-solaris-sparc-32.so >>> 04/16/2007 12:15 PM 21,032 libwrapper-solaris-sparc-64.so >>> 04/16/2007 12:15 PM 12,572 libwrapper-solaris-x86-32.so >>> 04/16/2007 12:15 PM 81,920 wrapper-windows-x86-32.dll >>> 04/16/2007 12:15 PM 83,820 wrapper.jar >>> 11 File(s) 338,397 bytes >>> >>> >>> Stephan Brenner wrote: >>>> Hi, >>>> >>>> Today I upgraded from 1.2. to 2.0. When trying to login (after I press >>>> the login button) the page hangs and the server does not respond >>>> anymore. >>>> >>>> When I have a look at the server, I see that the tomcat5.exe process is >>>> constantly at 50%. I think it takes all resources of one processor, >>>> because it is a dual processor machine. >>>> >>>> After I stop the TeamCity agent and only start the web server, >>>> everything works alright - so it has something to do with the agent. >>>> >>>> Unfortunately I can't see anything useful in the logs. The only thing >>>> is the following exception: >>>> INFO | jvm 1 | 2007/04/16 13:47:43 | >>>> c:\TeamCity\jre\bin\java -ea -Xmx384m -Dlog4j.configuration=file:../conf/teamcity-agent-log4j.xml >>>> -Dteamcity_logs=../logs/ -classpath ... >>>> jetbrains.buildServer.agent.AgentMain -file >>>> ../conf/buildAgent.properties >>>> INFO | jvm 1 | 2007/04/16 13:47:43 | >>>> java.util.NoSuchElementException >>>> >>>> Can you please tell me how to fix that problem? >>>> >>>> Cheers, >>>> Stephan >>]]>>>
>> Try to reinstall build agent (remove old version and install new). Ask
>> uninstaller to preserve build agent configuration and work directory.
>>
>> --
>> Pavel Sher
>>
>>
>> "Stephan Brenner" wrote in message >> news:evvtt0$pms$1@is.intellij.net... >>> Now I did an additional test... >>> >>> Additionally to the Upgrade described in 'Upgrading using the Windows >>> Installer' (see >>> http://www.jetbrains.net/confluence/display/TCD/Upgrade), I also tried >>> to manually upgrade the BuildAgent, because I've seen there was a >>> launcher.latest directory in my Agent directory. >>> >>> I did that like described on the above mentioned web page, but now I >>> directly get an exception when trying to start the BuildAgent service: >>> STATUS | wrapper | 2007/04/16 15:10:03 | --> Wrapper Started as Service >>> STATUS | wrapper | 2007/04/16 15:10:03 | Launching a JVM... >>> FATAL | wrapper | 2007/04/16 15:10:03 | Unable to execute Java >>> command. The system cannot find the file specified. (0x2) >>> FATAL | wrapper | 2007/04/16 15:10:03 | >>> "java" -Djava.library.path="../launcher/lib;../launcher/bin" -classpath >>> "../launcher/lib/wrapper.jar;../launcher/lib/launcher.jar" -Dwrapper.key="qlDraDn1RfwyDkog" >>> -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 >>> -Dwrapper.pid=6580 -Dwrapper.version="3.2.3" -Dwrapper.native_library="wrapper" >>> -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 >>> org.tanukisoftware.wrapper.WrapperSimpleApp >>> jetbrains.buildServer.agent.StandAloneLauncher -ea -Xmx384m -Dlog4j.configuration=file:../conf/teamcity-agent-log4j.xml >>> -Dteamcity_logs=../logs/ jetbrains.buildServer.agent.AgentMain -file >>> ../conf/buildAgent.properties >>> FATAL | wrapper | 2007/04/16 15:10:03 | Critical error: wait for JVM >>> process failed >>> >>> The files that are in my launcher directory, are listed blow. Please >>> help! >>> >>> Stephan >>> >>> >>> Directory of C:\TeamCity\buildAgent\launcher >>> >>> 04/16/2007 12:16 PM
I've uploaded following files to ftp.intellij.net/.uploads:
snb-teamcity-server.log
snb-teamcity-agent.log
snb-wrapper.log
Pavel Sher wrote:
>> Hi Pavel,
. >>>> 04/16/2007 12:16 PM .. >>>> 04/16/2007 12:16 PM bin >>>> 04/16/2007 12:16 PM conf >>>> 04/16/2007 12:15 PM 2,590 JavaServiceWrapperLicense.txt >>>> 04/16/2007 12:16 PM lib >>>> 1 File(s) 2,590 bytes >>>> >>>> Directory of C:\TeamCity\buildAgent\launcher\bin >>>> >>>> 04/16/2007 12:16 PM . >>>> 04/16/2007 12:16 PM .. >>>> 04/16/2007 12:15 PM 140,198 TeamCityAgentService-linux-ppc-64 >>>> 04/16/2007 12:15 PM 99,401 TeamCityAgentService-linux-x86-32 >>>> 04/16/2007 12:15 PM 111,027 TeamCityAgentService-linux-x86-64 >>>> 04/16/2007 12:15 PM 114,052 >>>> TeamCityAgentService-macosx-ppc-32 >>>> 04/16/2007 12:15 PM 233,604 >>>> TeamCityAgentService-macosx-universal-32 >>>> 04/16/2007 12:15 PM 112,536 >>>> TeamCityAgentService-solaris-sparc-32 >>>> 04/16/2007 12:15 PM 148,512 >>>> TeamCityAgentService-solaris-sparc-64 >>>> 04/16/2007 12:15 PM 110,992 >>>> TeamCityAgentService-solaris-x86-32 >>>> 04/16/2007 12:15 PM 204,800 >>>> TeamCityAgentService-windows-x86-32.exe >>>> 9 File(s) 1,275,122 bytes >>>> >>>> Directory of C:\TeamCity\buildAgent\launcher\conf >>>> >>>> 04/16/2007 12:16 PM . >>>> 04/16/2007 12:16 PM .. >>>> 04/16/2007 12:15 PM 4,457 wrapper.conf >>>> 1 File(s) 4,457 bytes >>>> >>>> Directory of C:\TeamCity\buildAgent\launcher\lib >>>> >>>> 04/16/2007 12:16 PM . >>>> 04/16/2007 12:16 PM .. >>>> 04/16/2007 12:15 PM 23,587 launcher.jar >>>> 04/16/2007 12:15 PM 23,839 libwrapper-linux-ppc-64.so >>>> 04/16/2007 12:15 PM 11,887 libwrapper-linux-x86-32.so >>>> 04/16/2007 12:15 PM 15,248 libwrapper-linux-x86-64.so >>>> 04/16/2007 12:15 PM 15,400 libwrapper-macosx-ppc-32.jnilib >>>> 04/16/2007 12:15 PM 35,332 >>>> libwrapper-macosx-universal-32.jnilib >>>> 04/16/2007 12:15 PM 13,760 libwrapper-solaris-sparc-32.so >>>> 04/16/2007 12:15 PM 21,032 libwrapper-solaris-sparc-64.so >>>> 04/16/2007 12:15 PM 12,572 libwrapper-solaris-x86-32.so >>>> 04/16/2007 12:15 PM 81,920 wrapper-windows-x86-32.dll >>>> 04/16/2007 12:15 PM 83,820 wrapper.jar >>>> 11 File(s) 338,397 bytes >>>> >>>> >>>> Stephan Brenner wrote: >>>>> Hi, >>>>> >>>>> Today I upgraded from 1.2. to 2.0. When trying to login (after I press >>>>> the login button) the page hangs and the server does not respond >>>>> anymore. >>>>> >>>>> When I have a look at the server, I see that the tomcat5.exe process is >>>>> constantly at 50%. I think it takes all resources of one processor, >>>>> because it is a dual processor machine. >>>>> >>>>> After I stop the TeamCity agent and only start the web server, >>>>> everything works alright - so it has something to do with the agent. >>>>> >>>>> Unfortunately I can't see anything useful in the logs. The only thing >>>>> is the following exception: >>>>> INFO | jvm 1 | 2007/04/16 13:47:43 | >>>>> c:\TeamCity\jre\bin\java -ea -Xmx384m -Dlog4j.configuration=file:../conf/teamcity-agent-log4j.xml >>>>> -Dteamcity_logs=../logs/ -classpath ... >>>>> jetbrains.buildServer.agent.AgentMain -file >>>>> ../conf/buildAgent.properties >>>>> INFO | jvm 1 | 2007/04/16 13:47:43 | >>>>> java.util.NoSuchElementException >>>>> >>>>> Can you please tell me how to fix that problem? >>>>> >>>>> Cheers, >>>>>]]> Stephan>>
>> I just tried that (called service.uninstall.bat and then executed
>> agentInstaller.exe). After starting it, the tomcat5.exe process uses 50%
>> of the CPU and the web site does not respond anymore. Without agent, the
>> TC web site works well.
>>
>> I additionally have to mention, that we only have one buildagent (runnning
>> on the same machine as the TC web site).
>>
>> Do you have any other ideas? Could it help to reset the DB (and how to do
>> that)?
>> Cheers,
>> Stephan
>>
>>
>> Pavel Sher wrote:
>>> Hello Stephan,
>>>
>>> Try to reinstall build agent (remove old version and install new). Ask
>>> uninstaller to preserve build agent configuration and work directory.
>>>
>>> --
>>> Pavel Sher
>>>
>>>
>>> "Stephan Brenner" wrote in message >>> news:evvtt0$pms$1@is.intellij.net... >>>> Now I did an additional test... >>>> >>>> Additionally to the Upgrade described in 'Upgrading using the Windows >>>> Installer' (see >>>> http://www.jetbrains.net/confluence/display/TCD/Upgrade), I also tried >>>> to manually upgrade the BuildAgent, because I've seen there was a >>>> launcher.latest directory in my Agent directory. >>>> >>>> I did that like described on the above mentioned web page, but now I >>>> directly get an exception when trying to start the BuildAgent service: >>>> STATUS | wrapper | 2007/04/16 15:10:03 | --> Wrapper Started as Service >>>> STATUS | wrapper | 2007/04/16 15:10:03 | Launching a JVM... >>>> FATAL | wrapper | 2007/04/16 15:10:03 | Unable to execute Java >>>> command. The system cannot find the file specified. (0x2) >>>> FATAL | wrapper | 2007/04/16 15:10:03 | >>>> "java" -Djava.library.path="../launcher/lib;../launcher/bin" -classpath >>>> "../launcher/lib/wrapper.jar;../launcher/lib/launcher.jar" -Dwrapper.key="qlDraDn1RfwyDkog" >>>> -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 >>>> -Dwrapper.pid=6580 -Dwrapper.version="3.2.3" -Dwrapper.native_library="wrapper" >>>> -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 >>>> org.tanukisoftware.wrapper.WrapperSimpleApp >>>> jetbrains.buildServer.agent.StandAloneLauncher -ea -Xmx384m -Dlog4j.configuration=file:../conf/teamcity-agent-log4j.xml >>>> -Dteamcity_logs=../logs/ jetbrains.buildServer.agent.AgentMain -file >>>> ../conf/buildAgent.properties >>>> FATAL | wrapper | 2007/04/16 15:10:03 | Critical error: wait for JVM >>>> process failed >>>> >>>> The files that are in my launcher directory, are listed blow. Please >>>> help! >>>> >>>> Stephan >>>> >>>> >>>> Directory of C:\TeamCity\buildAgent\launcher >>>> >>>> 04/16/2007 12:16 PM
Could you please make a thread dump of the TeamCity java process when it
took 50% CPU and send it to us? Please refer to this document for details
http://www.jetbrains.net/confluence/display/TW/HowtoDebug+problems
(section Hangs and thread dumps).
--
Pavel Sher
"Stephan Brenner" <no_reply@enteo.com> wrote in message
news:f003nn$2ra$1@is.intellij.net...
>
>
>> Could you please send us teamcity-server.log and teamcity-agent.log?
. >>>>> 04/16/2007 12:16 PM .. >>>>> 04/16/2007 12:16 PM bin >>>>> 04/16/2007 12:16 PM conf >>>>> 04/16/2007 12:15 PM 2,590 JavaServiceWrapperLicense.txt >>>>> 04/16/2007 12:16 PM lib >>>>> 1 File(s) 2,590 bytes >>>>> >>>>> Directory of C:\TeamCity\buildAgent\launcher\bin >>>>> >>>>> 04/16/2007 12:16 PM . >>>>> 04/16/2007 12:16 PM .. >>>>> 04/16/2007 12:15 PM 140,198 >>>>> TeamCityAgentService-linux-ppc-64 >>>>> 04/16/2007 12:15 PM 99,401 >>>>> TeamCityAgentService-linux-x86-32 >>>>> 04/16/2007 12:15 PM 111,027 >>>>> TeamCityAgentService-linux-x86-64 >>>>> 04/16/2007 12:15 PM 114,052 >>>>> TeamCityAgentService-macosx-ppc-32 >>>>> 04/16/2007 12:15 PM 233,604 >>>>> TeamCityAgentService-macosx-universal-32 >>>>> 04/16/2007 12:15 PM 112,536 >>>>> TeamCityAgentService-solaris-sparc-32 >>>>> 04/16/2007 12:15 PM 148,512 >>>>> TeamCityAgentService-solaris-sparc-64 >>>>> 04/16/2007 12:15 PM 110,992 >>>>> TeamCityAgentService-solaris-x86-32 >>>>> 04/16/2007 12:15 PM 204,800 >>>>> TeamCityAgentService-windows-x86-32.exe >>>>> 9 File(s) 1,275,122 bytes >>>>> >>>>> Directory of C:\TeamCity\buildAgent\launcher\conf >>>>> >>>>> 04/16/2007 12:16 PM . >>>>> 04/16/2007 12:16 PM .. >>>>> 04/16/2007 12:15 PM 4,457 wrapper.conf >>>>> 1 File(s) 4,457 bytes >>>>> >>>>> Directory of C:\TeamCity\buildAgent\launcher\lib >>>>> >>>>> 04/16/2007 12:16 PM . >>>>> 04/16/2007 12:16 PM .. >>>>> 04/16/2007 12:15 PM 23,587 launcher.jar >>>>> 04/16/2007 12:15 PM 23,839 libwrapper-linux-ppc-64.so >>>>> 04/16/2007 12:15 PM 11,887 libwrapper-linux-x86-32.so >>>>> 04/16/2007 12:15 PM 15,248 libwrapper-linux-x86-64.so >>>>> 04/16/2007 12:15 PM 15,400 libwrapper-macosx-ppc-32.jnilib >>>>> 04/16/2007 12:15 PM 35,332 >>>>> libwrapper-macosx-universal-32.jnilib >>>>> 04/16/2007 12:15 PM 13,760 libwrapper-solaris-sparc-32.so >>>>> 04/16/2007 12:15 PM 21,032 libwrapper-solaris-sparc-64.so >>>>> 04/16/2007 12:15 PM 12,572 libwrapper-solaris-x86-32.so >>>>> 04/16/2007 12:15 PM 81,920 wrapper-windows-x86-32.dll >>>>> 04/16/2007 12:15 PM 83,820 wrapper.jar >>>>> 11 File(s) 338,397 bytes >>>>> >>>>> >>>>> Stephan Brenner wrote: >>>>>> Hi, >>>>>> >>>>>> Today I upgraded from 1.2. to 2.0. When trying to login (after I >>>>>> press the login button) the page hangs and the server does not >>>>>> respond anymore. >>>>>> >>>>>> When I have a look at the server, I see that the tomcat5.exe process >>>>>> is constantly at 50%. I think it takes all resources of one >>>>>> processor, because it is a dual processor machine. >>>>>> >>>>>> After I stop the TeamCity agent and only start the web server, >>>>>> everything works alright - so it has something to do with the agent. >>>>>> >>>>>> Unfortunately I can't see anything useful in the logs. The only thing >>>>>> is the following exception: >>>>>> INFO | jvm 1 | 2007/04/16 13:47:43 | >>>>>> c:\TeamCity\jre\bin\java -ea -Xmx384m -Dlog4j.configuration=file:../conf/teamcity-agent-log4j.xml >>>>>> -Dteamcity_logs=../logs/ -classpath ... >>>>>> jetbrains.buildServer.agent.AgentMain -file >>>>>> ../conf/buildAgent.properties >>>>>> INFO | jvm 1 | 2007/04/16 13:47:43 | >>>>>> java.util.NoSuchElementException >>>>>> >>>>>> Can you please tell me how to fix that problem? >>>>>> >>>>>> Cheers, >>>>>> Stephan >>]]>>>
>> --
>> Pavel Sher
>>
>> "Stephan Brenner" wrote in message >> news:f00234$ech$1@is.intellij.net... >>> Hi Pavel, >>> >>> I just tried that (called service.uninstall.bat and then executed >>> agentInstaller.exe). After starting it, the tomcat5.exe process uses 50% >>> of the CPU and the web site does not respond anymore. Without agent, the >>> TC web site works well. >>> >>> I additionally have to mention, that we only have one buildagent >>> (runnning on the same machine as the TC web site). >>> >>> Do you have any other ideas? Could it help to reset the DB (and how to >>> do that)? >>> Cheers, >>> Stephan >>> >>> >>> Pavel Sher wrote: >>>> Hello Stephan, >>>> >>>> Try to reinstall build agent (remove old version and install new). Ask >>>> uninstaller to preserve build agent configuration and work directory. >>>> >>>> -- >>>> Pavel Sher >>>> >>>> >>>> "Stephan Brenner" wrote in message >>>> news:evvtt0$pms$1@is.intellij.net... >>>>> Now I did an additional test... >>>>> >>>>> Additionally to the Upgrade described in 'Upgrading using the Windows >>>>> Installer' (see >>>>> http://www.jetbrains.net/confluence/display/TCD/Upgrade), I also tried >>>>> to manually upgrade the BuildAgent, because I've seen there was a >>>>> launcher.latest directory in my Agent directory. >>>>> >>>>> I did that like described on the above mentioned web page, but now I >>>>> directly get an exception when trying to start the BuildAgent service: >>>>> STATUS | wrapper | 2007/04/16 15:10:03 | --> Wrapper Started as >>>>> Service >>>>> STATUS | wrapper | 2007/04/16 15:10:03 | Launching a JVM... >>>>> FATAL | wrapper | 2007/04/16 15:10:03 | Unable to execute Java >>>>> command. The system cannot find the file specified. (0x2) >>>>> FATAL | wrapper | 2007/04/16 15:10:03 | >>>>> "java" -Djava.library.path="../launcher/lib;../launcher/bin" -classpath >>>>> "../launcher/lib/wrapper.jar;../launcher/lib/launcher.jar" -Dwrapper.key="qlDraDn1RfwyDkog" >>>>> -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 >>>>> -Dwrapper.pid=6580 -Dwrapper.version="3.2.3" -Dwrapper.native_library="wrapper" >>>>> -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 >>>>> org.tanukisoftware.wrapper.WrapperSimpleApp >>>>> jetbrains.buildServer.agent.StandAloneLauncher -ea -Xmx384m -Dlog4j.configuration=file:../conf/teamcity-agent-log4j.xml >>>>> -Dteamcity_logs=../logs/ jetbrains.buildServer.agent.AgentMain -file >>>>> ../conf/buildAgent.properties >>>>> FATAL | wrapper | 2007/04/16 15:10:03 | Critical error: wait for JVM >>>>> process failed >>>>> >>>>> The files that are in my launcher directory, are listed blow. Please >>>>> help! >>>>> >>>>> Stephan >>>>> >>>>> >>>>> Directory of C:\TeamCity\buildAgent\launcher >>>>> >>>>> 04/16/2007 12:16 PM
I've uploaded the thread dump to ftp://ftp.intellij.net/.uploads/snb-thread-dumb.txt
Pavel Sher wrote:
>> I've uploaded following files to ftp.intellij.net/.uploads:
. >>>>>> 04/16/2007 12:16 PM .. >>>>>> 04/16/2007 12:16 PM bin >>>>>> 04/16/2007 12:16 PM conf >>>>>> 04/16/2007 12:15 PM 2,590 JavaServiceWrapperLicense.txt >>>>>> 04/16/2007 12:16 PM lib >>>>>> 1 File(s) 2,590 bytes >>>>>> >>>>>> Directory of C:\TeamCity\buildAgent\launcher\bin >>>>>> >>>>>> 04/16/2007 12:16 PM . >>>>>> 04/16/2007 12:16 PM .. >>>>>> 04/16/2007 12:15 PM 140,198 >>>>>> TeamCityAgentService-linux-ppc-64 >>>>>> 04/16/2007 12:15 PM 99,401 >>>>>> TeamCityAgentService-linux-x86-32 >>>>>> 04/16/2007 12:15 PM 111,027 >>>>>> TeamCityAgentService-linux-x86-64 >>>>>> 04/16/2007 12:15 PM 114,052 >>>>>> TeamCityAgentService-macosx-ppc-32 >>>>>> 04/16/2007 12:15 PM 233,604 >>>>>> TeamCityAgentService-macosx-universal-32 >>>>>> 04/16/2007 12:15 PM 112,536 >>>>>> TeamCityAgentService-solaris-sparc-32 >>>>>> 04/16/2007 12:15 PM 148,512 >>>>>> TeamCityAgentService-solaris-sparc-64 >>>>>> 04/16/2007 12:15 PM 110,992 >>>>>> TeamCityAgentService-solaris-x86-32 >>>>>> 04/16/2007 12:15 PM 204,800 >>>>>> TeamCityAgentService-windows-x86-32.exe >>>>>> 9 File(s) 1,275,122 bytes >>>>>> >>>>>> Directory of C:\TeamCity\buildAgent\launcher\conf >>>>>> >>>>>> 04/16/2007 12:16 PM . >>>>>> 04/16/2007 12:16 PM .. >>>>>> 04/16/2007 12:15 PM 4,457 wrapper.conf >>>>>> 1 File(s) 4,457 bytes >>>>>> >>>>>> Directory of C:\TeamCity\buildAgent\launcher\lib >>>>>> >>>>>> 04/16/2007 12:16 PM . >>>>>> 04/16/2007 12:16 PM .. >>>>>> 04/16/2007 12:15 PM 23,587 launcher.jar >>>>>> 04/16/2007 12:15 PM 23,839 libwrapper-linux-ppc-64.so >>>>>> 04/16/2007 12:15 PM 11,887 libwrapper-linux-x86-32.so >>>>>> 04/16/2007 12:15 PM 15,248 libwrapper-linux-x86-64.so >>>>>> 04/16/2007 12:15 PM 15,400 libwrapper-macosx-ppc-32.jnilib >>>>>> 04/16/2007 12:15 PM 35,332 >>>>>> libwrapper-macosx-universal-32.jnilib >>>>>> 04/16/2007 12:15 PM 13,760 libwrapper-solaris-sparc-32.so >>>>>> 04/16/2007 12:15 PM 21,032 libwrapper-solaris-sparc-64.so >>>>>> 04/16/2007 12:15 PM 12,572 libwrapper-solaris-x86-32.so >>>>>> 04/16/2007 12:15 PM 81,920 wrapper-windows-x86-32.dll >>>>>> 04/16/2007 12:15 PM 83,820 wrapper.jar >>>>>> 11 File(s) 338,397 bytes >>>>>> >>>>>> >>>>>> Stephan Brenner wrote: >>>>>>> Hi, >>>>>>> >>>>>>> Today I upgraded from 1.2. to 2.0. When trying to login (after I >>>>>>> press the login button) the page hangs and the server does not >>>>>>> respond anymore. >>>>>>> >>>>>>> When I have a look at the server, I see that the tomcat5.exe process >>>>>>> is constantly at 50%. I think it takes all resources of one >>>>>>> processor, because it is a dual processor machine. >>>>>>> >>>>>>> After I stop the TeamCity agent and only start the web server, >>>>>>> everything works alright - so it has something to do with the agent. >>>>>>> >>>>>>> Unfortunately I can't see anything useful in the logs. The only thing >>>>>>> is the following exception: >>>>>>> INFO | jvm 1 | 2007/04/16 13:47:43 | >>>>>>> c:\TeamCity\jre\bin\java -ea -Xmx384m -Dlog4j.configuration=file:../conf/teamcity-agent-log4j.xml >>>>>>> -Dteamcity_logs=../logs/ -classpath ... >>>>>>> jetbrains.buildServer.agent.AgentMain -file >>>>>>> ../conf/buildAgent.properties >>>>>>> INFO | jvm 1 | 2007/04/16 13:47:43 | >>>>>>> java.util.NoSuchElementException >>>>>>> >>>>>>> Can you please tell me how to fix that problem? >>>>>>> >>>>>>> Cheers, >>>>>>>]]> Stephan>> snb-teamcity-server.log
>> snb-teamcity-agent.log
>> snb-wrapper.log
>>
>>
>> Pavel Sher wrote:
>>> Could you please send us teamcity-server.log and teamcity-agent.log?
>>>
>>> --
>>> Pavel Sher
>>>
>>> "Stephan Brenner" wrote in message >>> news:f00234$ech$1@is.intellij.net... >>>> Hi Pavel, >>>> >>>> I just tried that (called service.uninstall.bat and then executed >>>> agentInstaller.exe). After starting it, the tomcat5.exe process uses 50% >>>> of the CPU and the web site does not respond anymore. Without agent, the >>>> TC web site works well. >>>> >>>> I additionally have to mention, that we only have one buildagent >>>> (runnning on the same machine as the TC web site). >>>> >>>> Do you have any other ideas? Could it help to reset the DB (and how to >>>> do that)? >>>> Cheers, >>>> Stephan >>>> >>>> >>>> Pavel Sher wrote: >>>>> Hello Stephan, >>>>> >>>>> Try to reinstall build agent (remove old version and install new). Ask >>>>> uninstaller to preserve build agent configuration and work directory. >>>>> >>>>> -- >>>>> Pavel Sher >>>>> >>>>> >>>>> "Stephan Brenner" wrote in message >>>>> news:evvtt0$pms$1@is.intellij.net... >>>>>> Now I did an additional test... >>>>>> >>>>>> Additionally to the Upgrade described in 'Upgrading using the Windows >>>>>> Installer' (see >>>>>> http://www.jetbrains.net/confluence/display/TCD/Upgrade), I also tried >>>>>> to manually upgrade the BuildAgent, because I've seen there was a >>>>>> launcher.latest directory in my Agent directory. >>>>>> >>>>>> I did that like described on the above mentioned web page, but now I >>>>>> directly get an exception when trying to start the BuildAgent service: >>>>>> STATUS | wrapper | 2007/04/16 15:10:03 | --> Wrapper Started as >>>>>> Service >>>>>> STATUS | wrapper | 2007/04/16 15:10:03 | Launching a JVM... >>>>>> FATAL | wrapper | 2007/04/16 15:10:03 | Unable to execute Java >>>>>> command. The system cannot find the file specified. (0x2) >>>>>> FATAL | wrapper | 2007/04/16 15:10:03 | >>>>>> "java" -Djava.library.path="../launcher/lib;../launcher/bin" -classpath >>>>>> "../launcher/lib/wrapper.jar;../launcher/lib/launcher.jar" -Dwrapper.key="qlDraDn1RfwyDkog" >>>>>> -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 >>>>>> -Dwrapper.pid=6580 -Dwrapper.version="3.2.3" -Dwrapper.native_library="wrapper" >>>>>> -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 >>>>>> org.tanukisoftware.wrapper.WrapperSimpleApp >>>>>> jetbrains.buildServer.agent.StandAloneLauncher -ea -Xmx384m -Dlog4j.configuration=file:../conf/teamcity-agent-log4j.xml >>>>>> -Dteamcity_logs=../logs/ jetbrains.buildServer.agent.AgentMain -file >>>>>> ../conf/buildAgent.properties >>>>>> FATAL | wrapper | 2007/04/16 15:10:03 | Critical error: wait for JVM >>>>>> process failed >>>>>> >>>>>> The files that are in my launcher directory, are listed blow. Please >>>>>> help! >>>>>> >>>>>> Stephan >>>>>> >>>>>> >>>>>> Directory of C:\TeamCity\buildAgent\launcher >>>>>> >>>>>> 04/16/2007 12:16 PM
I've migrated to MySQL (Quick Migration). Now everything works fine.
Stephan Brenner wrote:
Glad to here that TC is working fine now. BTW what is your HSQL database
size (file buildServer.data from the .BuildServer/system folder)?
--
Pavel Sher
"Stephan Brenner" <no_reply@enteo.com> wrote in message
news:f021bd$6rn$1@is.intellij.net...
>
>> Hi,
>>
>> Today I upgraded from 1.2. to 2.0. When trying to login (after I press
>> the login button) the page hangs and the server does not respond anymore.
>>
>> When I have a look at the server, I see that the tomcat5.exe process is
>> constantly at 50%. I think it takes all resources of one processor,
>> because it is a dual processor machine.
>>
>> After I stop the TeamCity agent and only start the web server, everything
>> works alright - so it has something to do with the agent.
>>
>> Unfortunately I can't see anything useful in the logs. The only thing is
>> the following exception:
>> INFO | jvm 1 | 2007/04/16 13:47:43 |
>> c:\TeamCity\jre\bin\java -ea -Xmx384m -Dlog4j.configuration=file:../conf/teamcity-agent-log4j.xml
>> -Dteamcity_logs=../logs/ -classpath ...
>> INFO | jvm 1 | 2007/04/16 13:47:43 |
>> java.util.NoSuchElementException
>>
>> Can you please tell me how to fix that problem?
>>
>> Cheers,
>> Stephan
The size of the HSQL DB was 65 MB.
Pavel Sher wrote:
>> I've migrated to MySQL (Quick Migration). Now everything works fine.
>>
>> Stephan Brenner wrote:
>>> Hi,
>>>
>>> Today I upgraded from 1.2. to 2.0. When trying to login (after I press
>>> the login button) the page hangs and the server does not respond anymore.
>>>
>>> When I have a look at the server, I see that the tomcat5.exe process is
>>> constantly at 50%. I think it takes all resources of one processor,
>>> because it is a dual processor machine.
>>>
>>> After I stop the TeamCity agent and only start the web server, everything
>>> works alright - so it has something to do with the agent.
>>>
>>> Unfortunately I can't see anything useful in the logs. The only thing is
>>> the following exception:
>>> INFO | jvm 1 | 2007/04/16 13:47:43 |
>>> c:\TeamCity\jre\bin\java -ea -Xmx384m -Dlog4j.configuration=file:../conf/teamcity-agent-log4j.xml
>>> -Dteamcity_logs=../logs/ -classpath ...
>>> INFO | jvm 1 | 2007/04/16 13:47:43 |
>>> java.util.NoSuchElementException
>>>
>>> Can you please tell me how to fix that problem?
>>>
>>> Cheers,
>>> Stephan