TeamCity 10 Installation On CentOS Won't Start

I'm attempting to install TeamCity 10 on a CentOS VPS with root access and it is not starting, but it's strange.  I've installed older versions of TeamCity several times before but can't actually figure out what is wrong this time.  My environment variables are JAVA_HOME=/usr/local/jdk JRE_HOME=/usr/local/jdk/jre and the version of java stated by java --version is 1.8.0_121.  My server log reads the following:

[2017-03-19 04:51:13,339] INFO - jetbrains.buildServer.STARTUP - ===========================================================
[2017-03-19 04:51:13,339] INFO - jetbrains.buildServer.STARTUP - Starting TeamCity server
[2017-03-19 04:51:13,919] INFO - jetbrains.buildServer.STARTUP - TeamCity version: 10.0.5 (build 42677), data format version 787
[2017-03-19 04:51:13,935] INFO - jetbrains.buildServer.STARTUP - OS: Linux, User: teamcity, Java: 1.8.0_121, Java HotSpot(TM) 64-Bit Server VM (25.121-b13, mixed mode), Java(TM) SE Runtime Environment (1.8.0_121-b13), Oracle Corporation
[2017-03-19 04:51:13,936] INFO - jetbrains.buildServer.STARTUP - JVM parameters: -Djava.util.logging.config.file=/var/www/apps/TeamCity/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xmx512m -Dteamcity.configuration.path=../conf/teamcity-startup.properties -Dlog4j.configuration=file:/var/www/apps/TeamCity/bin/../conf/teamcity-server-log4j.xml -Dteamcity_logs=../logs/ -Djava.awt.headless=true -Djava.endorsed.dirs=/var/www/apps/TeamCity/endorsed -Dcatalina.base=/var/www/apps/TeamCity -Dcatalina.home=/var/www/apps/TeamCity -Djava.io.tmpdir=/var/www/apps/TeamCity/temp
[2017-03-19 04:51:13,938] INFO - jetbrains.buildServer.STARTUP - Garbage collection: PS Scavenge, PS MarkSweep
[2017-03-19 04:51:13,939] INFO - jetbrains.buildServer.STARTUP - Web server version: Apache Tomcat/7.0.68
[2017-03-19 04:51:13,939] INFO - jetbrains.buildServer.STARTUP - Server IP address: [SERVER'S IP ADDRESS] 
[2017-03-19 04:51:13,942] INFO - jetbrains.buildServer.STARTUP - Web server ports: 8111 (protocol: org.apache.coyote.http11.Http11NioProtocol, scheme: http), 8105 (shutdown port)
[2017-03-19 04:51:13,942] INFO - jetbrains.buildServer.STARTUP - TeamCity server work mode: Main TeamCity Server
[2017-03-19 04:51:13,948] INFO - jetbrains.buildServer.STARTUP - Version file lock was successfully obtained: /var/www/apps/TeamCity/webapps/ROOT/BUILD_42677
[2017-03-19 04:51:13,959] INFO - jetbrains.buildServer.STARTUP - Servlet real path: /var/www/apps/TeamCity/webapps/ROOT/
[2017-03-19 04:51:13,966] INFO - jetbrains.buildServer.STARTUP - Current stage: Looking for the TeamCity Data Directory
[2017-03-19 04:51:13,967] INFO - jetbrains.buildServer.STARTUP - The TeamCity Data Directory path is determined using the user home directory
[2017-03-19 04:51:13,976] INFO - jetbrains.buildServer.STARTUP - The TeamCity Data Directory "/home/teamcity/.BuildServer" exists
[2017-03-19 04:51:13,977] INFO - jetbrains.buildServer.STARTUP - Asking user to select the TeamCity Data Directory path from UI
[2017-03-19 04:51:13,977] INFO - jetbrains.buildServer.STARTUP - Startup confirmation is required. Open TeamCity web page in the browser
[2017-03-19 04:51:13,980] INFO - jetbrains.buildServer.STARTUP - Current stage: Confirming TeamCity first start (administrator login is required to proceed)

So it seems normal from prior experiences, but I can't actually reach the server, not even a wget http://localhost:8111/ will do anything other than tell me service unavailable.  Any tips would be appreciated.

I should also add, the server.xml is the default one.

0
2 comments

Hi Cory and sorry for the delay,

were you able to make it work? If not, maybe you can check the catalina logs, where errors about tomcat itself are displayed.

0

Yes, it was dumb.  It came down to an iptables entry being needed due to the VPS I was using, though I ran into enough other issues I switched off a managed VPS onto an unmanaged one.

0

Please sign in to leave a comment.