Address already in use after update 2018.1.1
I use the update process over the administration site. And with the update to 2018.1.1 there is this error in the catalina.log.
03-Sep-2018 09:26:43.892 SCHWERWIEGEND [main] org.apache.catalina.core.StandardService.initInternal Failed to initialize connector [Connector[HTTP/1.1-9888]]
org.apache.catalina.LifecycleException: Failed to initialize component [Connector[HTTP/1.1-9888]]
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
The port was 9888. Then I install the 2018.1.1 over the exe-file. In the config is the port 9888, that's ok. But I have no connection over the browser und the services are started and in the teamcity.log is all ok, only in the catalina.log is this error. I change the port to 9880 in the server.xml and in the buildAgend.properties. And it works with the new port.
Now I update to the 2018.1.2 and must do the same procedure. I have no connection to 9880 and I change the port to 9881.
But this is no solution. What can I do?
Please sign in to leave a comment.
That message appears when the port is already being used. That means that either you have another application running on that port, or that you haven't stopped the previous teamcity server before installing. Please make sure that the old server is fully stopped, check the process manager and kill any remaining process, or check in it whether you have any application running on that port.
Ok. You mean, that I stop the teamcity server before I start the update process over the update site (server administration). I thought, it do this automatically. But I use a special user for the services. Could be this the reason? I will do this by the next update. :-) Thank you.
Hi,
If you are updating using the web UI (automatic update) then no, you can't stop the server as then you won't be able to update at all, TeamCity handles it automatically. If you are updating via the exe file (as you mentioned in your initial post), then it would be recommended to stop the server. Specific details for all types of upgrades are available here: https://confluence.jetbrains.com/display/TCD18/Upgrade
Hi, I use the webUI for automatic update. And it works before 2018.1.1 and with this update not. And I must change the port. The updating via exe file is only, because I don't know if the automatic update work correctly. Maybe I did not describe it exactly.