Bamboo6.5 installation on EC2 instance- Cannot stop Tomcat
Asked by Rajashree Baradur:

I am installing Atlassian Bamboo 6.5 on an Amazon EC2 instance. I have followed the steps mentioned in this post - <http://sdbaddas.blogspot.com/2016/08/how-to-install-bamboo-with-jira.html>

These are the version deatils:

    Using CATALINA_BASE:   /opt/bambooUsing CATALINA_HOME:   /opt/bambooUsing CATALINA_TMPDIR: /opt/bamboo/tempUsing JRE_HOME:        /usr/lib/jvm/java-1.8.0-openjdk-amd64Using CLASSPATH:       /opt/bamboo/bin/bootstrap.jar:/opt/bamboo/bin/tomcat juli.jarServer version: Apache Tomcat/8.0.36Server built:   Jun 9 2016 13:55:50 UTCServer number:  8.0.36.0OS Name:        LinuxOS Version:     4.4.0-1052-awsArchitecture:   amd64JVM Version:    1.8.0_171-8u171-b11-0ubuntu0.16.04.1-b11JVM Vendor:     Oracle Corporation

When I run start-bamboo.sh, I get this output:

    Using CATALINA_BASE:   /opt/bambooUsing CATALINA_HOME:   /opt/bambooUsing CATALINA_TMPDIR: /opt/bamboo/tempUsing JRE_HOME:        /usr/lib/jvm/java-1.8.0-openjdk-amd64Using CLASSPATH:       /opt/bamboo/bin/bootstrap.jar:/opt/bamboo/bin/tomcat-juli.jarTomcat started.

But I am not able to browse to the application using the IP address or the servername.

When I run stop-bamboo.sh, I get the following error:

    org.apache.catalina.startup.Catalina stopServerSEVERE: Could not contact localhost:8007. Tomcat may not be running.org.apache.catalina.startup.Catalina stopServerSEVERE: Catalina.stop:java.net.ConnectException: Connection timed out (Connection timed out)    at java.net.PlainSocketImpl.socketConnect(Native Method)    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)    atjava.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)    at  java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)        at java.net.Socket.connect(Socket.java:589)        at java.net.Socket.connect(Socket.java:538)        at java.net.Socket.<init>(Socket.java:434)        at java.net.Socket.<init>(Socket.java:211)        at org.apache.catalina.startup.Catalina.stopServer(Catalina.java:450)        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.stopServer(Bootstrap.java:400)        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:487)

Has anyone had the same issue? I think it means that Tomcat is not running on the server and it has something to do with the 8007 port which is the SHUTDOWN port mentioned in the server.xml file. Please advise.


Answers:
author: Alexis Robert
body: Hi [@Rajashree Baradur](/t5/user/viewprofilepage/user-id/1293865),

you should first check if Bamboo is running after you start it with the following command:

```
ps -ef | grep bamboo
```

You should also have a look at the logs in `/opt/bamboo/logs/catalina.out to check if you have any errors.`

`Regarding the shutdown port, don't worry about it: it's normal for this to be different than the application port, the error you're seeing is because there is no Bamboo process running, so Tomcat is unable to perform the shutdown action.`

`There is very probably another problem that prevents Bamboo from starting, this is what you should look for in the first place.`

`Let me know if you have any questions,`

`--Alexis`


Tags: aws