After installing Bamboo server is not coming up
Asked by QAFDS:

After installing Bamboo server is not coming up. Getting below error on log:

\[automation@localhost bamboo-install\]$ cat /home/automation/bamboo-install/logs/catalina.out  
OpenJDK 64-Bit Server VM warning: If the number of processors is expected to increase from one, then you should configure the number of parallel GC threads appropriately using -XX:ParallelGCThreads=N  
14-Sep-2022 13:55:04.683 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin \[SetPropertiesRule\]{Server/Service/Engine/Valve} Setting property 'enableLookups' to 'false' did not find a matching property.  
14-Sep-2022 13:55:04.702 INFO \[main\] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The Apache Tomcat Native library which allows using OpenSSL was not found on the java.library.path: \[/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib\]  
14-Sep-2022 13:55:04.771 INFO \[main\] org.apache.coyote.http11.AbstractHttp11Protocol.configureUpgradeProtocol The \["http-nio-8085"\] connector has been configured to support HTTP upgrade to \[h2c\]  
14-Sep-2022 13:55:04.772 INFO \[main\] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler \["http-nio-8085"\]  
14-Sep-2022 13:55:04.796 SEVERE \[main\] org.apache.catalina.core.StandardService.initInternal Failed to initialize connector \[Connector\[HTTP/1.1-8085\]\]  
org.apache.catalina.LifecycleException: Protocol handler initialization failed  
at org.apache.catalina.connector.Connector.initInternal(Connector.java:1076)  
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)  
at org.apache.catalina.core.StandardService.initInternal(StandardService.java:552)  
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)  
at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:843)  
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)  
at org.apache.catalina.startup.Catalina.load(Catalina.java:639)  
at org.apache.catalina.startup.Catalina.load(Catalina.java:662)  
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:305)  
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:475)  
Caused by: java.net.BindException: Address already in use  
at sun.nio.ch.Net.bind0(Native Method)  
at sun.nio.ch.Net.bind(Net.java:461)  
at sun.nio.ch.Net.bind(Net.java:453)  
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:222)  
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:85)  
at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:221)  
at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:1147)  
at org.apache.tomcat.util.net.AbstractJsseEndpoint.init(AbstractJsseEndpoint.java:222)  
at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:599)  
at org.apache.coyote.http11.AbstractHttp11Protocol.init(AbstractHttp11Protocol.java:80)  
at org.apache.catalina.connector.Connector.initInternal(Connector.java:1074)  
... 13 more  
14-Sep-2022 13:55:04.796 INFO \[main\] org.apache.catalina.startup.Catalina.load Initialization processed in 813 ms  
14-Sep-2022 13:55:04.816 INFO \[main\] org.apache.catalina.core.StandardService.startInternal Starting service \[Catalina\]  
14-Sep-2022 13:55:04.816 INFO \[main\] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: \[Apache Tomcat/8.5.70\]  
\[automation@localhost bamboo-install\]$


Answers:
author: Eduardo Alvarenga
body: Hello [@QAFDS](/t5/user/viewprofilepage/user-id/5030750)

Welcome to **Atlassian Community**!

By checking the logs we can notice:

```
Caused by: java.net.BindException: Address already in use
```

Can you review your system and validate if another service/application or even another Bamboo instance is running and using the same port as configured on the Tomcat connection (8085 by default).

Restarting the server may solve the issue.

Sincerely,

Eduardo Alvarenga  
Atlassian Support APAC

**--please don't forget to Accept the answer if the reply is helpful--**