Upgrade to 2018.1.1 failed
Hello
After upgrading from TeamCity version: 2018.1 (build 58245) to TeamCity version: 2018.1.1 (build 58406)
now the server does not start.
Both Windows services are running but there is no web.
I returned to previuos version, but no luck, the server does not start.
The error in web page is ERR_CONNECTION_REFUSED
Thank you.
Please sign in to leave a comment.
I don´t why but the web server does not start on port 80.
I reinstalled on port 8111 and uncomment the corresponding connector on file server,xml and know the server starts again. ¿?
The error on teamcity-winservice.log is
2018-07-24 18:35:08,545] console [Info] 24-Jul-2018 18:35:08.467 INFORMACIÓN [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent La biblioteca nativa de Apache Tomcat basada en ARP que permite un rendimiento óptimo en entornos de desarrollo no ha sido hallada en java.library.path: [c:\TeamCity\jre\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files\Microsoft SQL Server\110\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\140\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\ManagementStudio\;C:\Program Files\Git\cmd;.]
[2018-07-24 18:35:08,758] console [Info] 24-Jul-2018 18:35:08.726 INFORMACIÓN [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-80"]
[2018-07-24 18:35:08,758] console [Info] 24-Jul-2018 18:35:08.742 GRAVE [main] org.apache.catalina.core.StandardService.initInternal No pude inicializar el conector [Connector[HTTP/1.1-80]]
[2018-07-24 18:35:08,758] console [Info] org.apache.catalina.LifecycleException: Failed to initialize component [Connector[HTTP/1.1-80]]
[2018-07-24 18:35:08,758] console [Info] at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:112)
[2018-07-24 18:35:08,758] console [Info] at org.apache.catalina.core.StandardService.initInternal(StandardService.java:549)
[2018-07-24 18:35:08,758] console [Info] at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
[2018-07-24 18:35:08,758] console [Info] at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:875)
[2018-07-24 18:35:08,758] console [Info] at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
[2018-07-24 18:35:08,758] console [Info] at org.apache.catalina.startup.Catalina.load(Catalina.java:632)
[2018-07-24 18:35:08,758] console [Info] at org.apache.catalina.startup.Catalina.load(Catalina.java:655)
[2018-07-24 18:35:08,758] console [Info] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[2018-07-24 18:35:08,758] console [Info] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[2018-07-24 18:35:08,758] console [Info] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[2018-07-24 18:35:08,758] console [Info] at java.lang.reflect.Method.invoke(Method.java:498)
[2018-07-24 18:35:08,758] console [Info] at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:309)
[2018-07-24 18:35:08,758] console [Info] at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:492)
[2018-07-24 18:35:08,758] console [Info] Caused by: org.apache.catalina.LifecycleException: Falló la inicialización del manejador de protocolo
[2018-07-24 18:35:08,758] console [Info] at org.apache.catalina.connector.Connector.initInternal(Connector.java:995)
[2018-07-24 18:35:08,758] console [Info] at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
[2018-07-24 18:35:08,758] console [Info] ... 12 more
[2018-07-24 18:35:08,758] console [Info] Caused by: java.net.BindException: Address already in use: bind
Hi Enrique,
The problem in the stacktrace seems to indicate that there is another service that is already using port 80, which obviously stops tomcat from using it and it will stop working. In order to bring TeamCity back into port 80, please ensure that no other application in your server is using it.
I had exactly same issue - after running the automatic update, the Windows service started and teamcity-update.log looked fine, but there was no web service and in catalina.xxx.log there was
so apparently something else (leftovers of previous TeamCity process?) was binding the port 80. Restarting the server machine helped, after that everything worked fine.