Can't Access TeamCity Localhost

After following docs, I ran runAll.bat and then navigated to: http://localhost:9090/. But I keep getting the error below. Any ideas?

 

Method GET not implemented (try POST)
8 comments
Comment actions Permalink

Hi Dave,

port 9090 is usually the port that the agent uses to communicate with the server. By default, connect to localhost:8111 instead.

0
Comment actions Permalink

When I try 8111, I get: localhost refused to connect.

Ran runAll.bat but still getting it.

0
Comment actions Permalink

If 8111 or 80 posts do not work for you, then please attach teamcity-server.log file?

0
Comment actions Permalink

Ok, here is the last group of startup messages from the log:

 

[2017-03-14 17:34:25,956] INFO - jetbrains.buildServer.STARTUP - ===========================================================
[2017-03-14 17:34:25,956] INFO - jetbrains.buildServer.STARTUP - Starting TeamCity server
[2017-03-14 17:34:26,315] INFO - jetbrains.buildServer.STARTUP - TeamCity version: 10.0.4 (build 42538), data format version 787
[2017-03-14 17:34:26,315] INFO - jetbrains.buildServer.STARTUP - OS: Windows 10, User: DAVIDM$, Java: 1.8.0_66, Java HotSpot(TM) Server VM (32 bit) (25.66-b17, mixed mode), Java(TM) SE Runtime Environment (1.8.0_66-b17), Oracle Corporation
[2017-03-14 17:34:26,315] INFO - jetbrains.buildServer.STARTUP - JVM parameters: -Djava.util.logging.config.file=C:\Program Files (x86)\TeamCity\bin\..\conf\logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xrs -Xmx512m -Dteamcity.configuration.path=../conf/teamcity-startup.properties -Dlog4j.configuration=file:../conf/teamcity-server-log4j.xml -Dteamcity_logs=../logs/ -Djava.endorsed.dirs=C:\Program Files (x86)\TeamCity\bin\..\endorsed -Dcatalina.base=C:\Program Files (x86)\TeamCity\bin\.. -Dcatalina.home=C:\Program Files (x86)\TeamCity\bin\.. -Djava.io.tmpdir=C:\Program Files (x86)\TeamCity\bin\..\temp
[2017-03-14 17:34:26,315] INFO - jetbrains.buildServer.STARTUP - Garbage collection: PS Scavenge, PS MarkSweep
[2017-03-14 17:34:26,346] INFO - jetbrains.buildServer.STARTUP - Web server version: Apache Tomcat/7.0.68
[2017-03-14 17:34:26,346] INFO - jetbrains.buildServer.STARTUP - Server IP address: 555.555.5.55
[2017-03-14 17:34:26,346] INFO - jetbrains.buildServer.STARTUP - Web server ports: 80 (protocol: org.apache.coyote.http11.Http11NioProtocol, scheme: http), 8105 (shutdown port)
[2017-03-14 17:34:26,346] INFO - jetbrains.buildServer.STARTUP - TeamCity server work mode: Main TeamCity Server
[2017-03-14 17:34:26,362] INFO - rocesses.ProcessTreeTerminator - Using jetbrains.buildServer.processes.ProcessTreeTerminatorWindows
[2017-03-14 17:34:26,409] INFO - .ProcessTreeTerminatorImplBase - Will use command 'C:\Program Files (x86)\TeamCity\temp\TeamCity7389126685821034473ps\JetBrains.TeamCity.ps.exe ps'.
[2017-03-14 17:34:26,502] INFO - jetbrains.buildServer.STARTUP - TeamCity server process ID (4492) stored in: C:\Program Files (x86)\TeamCity\logs\teamcity.pid
[2017-03-14 17:34:26,502] INFO - jetbrains.buildServer.STARTUP - Version file lock was successfully obtained: C:\Program Files (x86)\TeamCity\bin\..\webapps\ROOT\BUILD_42538
[2017-03-14 17:34:26,534] INFO - jetbrains.buildServer.STARTUP - Servlet real path: C:\Program Files (x86)\TeamCity\bin\..\webapps\ROOT\
[2017-03-14 17:34:26,549] INFO - jetbrains.buildServer.STARTUP - Current stage: Looking for the TeamCity Data Directory
[2017-03-14 17:34:26,549] INFO - jetbrains.buildServer.STARTUP - The TeamCity Data Directory path is determined using the user home directory
[2017-03-14 17:34:26,549] INFO - jetbrains.buildServer.STARTUP - The TeamCity Data Directory "C:\Windows\System32\config\systemprofile\.BuildServer" doesn't exist
[2017-03-14 17:34:26,549] INFO - jetbrains.buildServer.STARTUP - Asking user to select the TeamCity Data Directory path from UI
[2017-03-14 17:34:26,549] INFO - jetbrains.buildServer.STARTUP - Startup confirmation is required. Open TeamCity web page in the browser
[2017-03-14 17:34:26,549] INFO - jetbrains.buildServer.STARTUP - Current stage: Confirming TeamCity first start (administrator login is required to proceed)

0
Comment actions Permalink

According to the log the server started successfully and requires confirmation via UI to proceed. What do you see if you open http://localhost:80 in web browser?

0
Comment actions Permalink

Thanks for the follow-up. Since we could not get this working and Visual Studio Team Systems was super simple, our team is going with VSTS.

 

David McCarter

1
Comment actions Permalink

Same problem for me

In server log there is an error

org.apache.catalina.LifecycleException: Failed to initialize component [Connector[HTTP/1.1-9090]]
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:112)
at org.apache.catalina.core.StandardService.initInternal(StandardService.java:549)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:875)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
at org.apache.catalina.startup.Catalina.load(Catalina.java:632)
at org.apache.catalina.startup.Catalina.load(Catalina.java:655)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:309)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:492)
Caused by: org.apache.catalina.LifecycleException: Protocol handler initialization failed
at org.apache.catalina.connector.Connector.initInternal(Connector.java:995)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
... 12 more
Caused by: java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:433)
at sun.nio.ch.Net.bind(Net.java:425)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:210)
at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:1086)
at org.apache.tomcat.util.net.AbstractJsseEndpoint.init(AbstractJsseEndpoint.java:268)
at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:581)
at org.apache.coyote.http11.AbstractHttp11Protocol.init(AbstractHttp11Protocol.java:68)
at org.apache.catalina.connector.Connector.initInternal(Connector.java:993)
... 13 more

Try to open 8111 and 80 port but same in browser Method GET not implemented (try POST)

0
Comment actions Permalink

Hi Alexey,

 

that message means strictly that the port trying to be used by TeamCity (seems like 9090 from the exception) was already in use by another service. Please make sure you stop all services using the ports required by teamcity, then try again.

0

Please sign in to leave a comment.