Connection refused on AWS ubuntu server

Abdullah Fasih_k0a6og

I have downloaded bamboo on an ubuntu aws server and created a bamboo home directory

 

 

If you encounter issues starting or stopping Bamboo Server, please see the Troubleshooting guide at https://confluence.atlassian.com/display/BAMBOO/Installing+and+upgrading+Bamboo

Using CATALINA_BASE: /home/cipipeline/atlassian-bamboo-6.10.3
Using CATALINA_HOME: /home/cipipeline/atlassian-bamboo-6.10.3
Using CATALINA_TMPDIR: /home/cipipeline/atlassian-bamboo-6.10.3/temp
Using JRE_HOME: /usr
Using CLASSPATH: /home/cipipeline/atlassian-bamboo-6.10.3/bin/bootstrap.jar:/home/cipipeline/atlassian-bamboo-6.10.3/bin/tomcat-juli.jar
Tomcat started.

 

i have JAVA_HOME after installation 

set the bamboo home directory to an empty bamboo folder 

and ran the start-bamboo.sh command which gave the underlined output above

 

i have port 8085 open. Connection is always refused i even turned off my proxy

Daniel Santos_157bm4

Hi @Abdullah Fasih

I see two possible reasons for a connection refused from what you describe:

1. The Bamboo server is not up and running. Maybe it crashed during the startup or was not able to bind with the 8085 port.
2. The port is still closed somehow.

Suggested troubleshooting steps:

• For number (1):
  • Check if the Bamboo process is still running
  • Check if you can telnet the server using the server terminal or even try to download the Bamboo startup/wizard page with wget.
    This will allow you to know if Bamboo is accepting connections from the server itself.
  • Check the server logs at <Bamboo_Install>/logs/catalina.out to identify if there are any errors regarding the port binding. 
    
    
• For number (2)
  
  • For this one, you could use nc command (by running a server <-> client connection:
    
    • On the server-side run:
      ⚠️make sure the Bamboo process is stopped
      

      nc -l 8085

    • On the client-side run:
      

      nc bamboo-server-address 8085

      
      If the connection is established, you should be able to send text strings from one side to another. This should validate the network configuration.

I hope the suggestions above will help us to understand what is causing this issue.

Ah, one last thing, check if you are using JAVA 1.8 in your AWS server.