Issues after Win 7 update(s)
I'm a complete Team City newbie. I installed Team City linked to SQLServer 2014 Express, YouTrack, UpSource and then Hub over the past couple of days to get to know them prior to recommendation for use throughout my company. All was well until this morning - following a Windows update (Win 7 Ultimate).
The basics are :-
TeamCity service not running. When I start it manually, it stops after a few seconds.
teamcity-server.log does not show anything untoward.
teamcity-winservice.log does not show anything untoward either but has the last 4 entries :-
[2017-09-14 08:52:36,232] console [Info] INFO: Server startup in 13396 ms
[2017-09-14 08:52:36,387] console [Info] TeamCity version: 2017.1.4 (build 47070), data format version 812
[2017-09-14 08:52:36,387] console [Info] OS: Windows 7, version 6.1, x86, Current user: DMcKelvie, Time zone: BST (UTC+01:00)
[2017-09-14 08:52:36,387] console [Info] Java: 1.8.0_121, Java HotSpot(TM) Server VM (32 bit) (25.121-b13, mixed mode), Java(TM) SE Runtime Environment (1.8.0_121-b13), Oracle Corporation; JVM parameters: -Djava.util.logging.config.file=c:\TeamCity\bin\..\conf\logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djdk.tls.ephemeralDHKeySize=2048 -Xrs -Xmx512m -Dteamcity.configuration.path=../conf/teamcity-startup.properties -Dlog4j.configuration=file:../conf/teamcity-server-log4j.xml -Dteamcity_logs=../logs/ -Dtomcat.util.http.parser.HttpParser.requestTargetAllow={} -Djava.endorsed.dirs=c:\TeamCity\bin\..\endorsed -Dcatalina.base=c:\TeamCity\bin\.. -Dcatalina.home=c:\TeamCity\bin\.. -Djava.io.tmpdir=c:\TeamCity\bin\..\temp
[2017-09-14 08:52:36,841] ProcessCommand [Info] Process exited with code: 1
[2017-09-14 08:52:36,896] ServiceExecuteProcessTask [Error] Service process exited without service stop request
There is nothing untoward logged in any other log file that was created/update around the time I manually start TeamCity service.
Please sign in to leave a comment.
Hi David,
Does the teamcity-server.log not contain anything at all? Or nothing displaying errors? Can you try starting the server via "bin\runAll.bat" instead of as a service? Can you also check the catalina.out?
If your server is rather large, you might want to change that -Xmx512m, which is what we ship by default for testing purposes, but is rarely enough for production servers. If your server is loading large amounts of data, this might be a cause for the problem.