I am installing Bamboo on a test server under an evaluation license. The server starts up with bin/start-bamboo.sh, but it can't be reached by browser. I'm trying to track down the cause of the problem.
The installation document says that after you run start-bamboo.sh for the first time you should look at localhost:8085. Since this is a remote machine I can't run a local browser and am trying to connect through the machine's name. Can the initial connection come from a remote machine, or does it have to be the same one bamboo is installed on?
lsof -i shows that bamboo's tomcat instance is listening on port 8085
Hey Todd
use a netstat to see what IP address you bamboo process is connected to : (*nix) netstat -an| grep 8085
if it is 0's, or 127.0.0.1 - you can either update your etc hosts by adding the hostname to the /ect/host file (or)
edit <install-dor/conf/server.xml add this to the 8085 connector
address="123.456.789.11" where 123.456.789.11 is your host IP address in double quotes.
restart and try.
good luck!
Hey @James Saxton
I have tried the 2nd method that you had mentioned, but it is not working. Please refer to this issue and these comments. You will have a better understanding. Do you have any resolution idea because I have tried opening the ports, still i'm getting bricked.
Regards
Aditya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is an old post, and an answered one. You're very unlikely to get any help here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Turns out our new systems automation software has a firewall module that isn't iptables.
Wiping egg off my face
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
change "remove" to "remote" is note above
if you can connect - try to telnet from a remote *nix machine to the bamboo server using the above command
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Todd
looks like you are running *nix
the telnet to localhost 8085 will return a connection refused, bamboo is bound to the ip address of 10.12.16.38 5not 127.0.0.1
on the server running bamboo try this
telnet 10.12.16.38 8085
if you get a connection refused - the port is blocked by iptables (most likely)
if you can connect - try to telnet from a remove *nix machine to the bamboo server using the above command
if you get a connection refused - firewall or iptables again may be blocking you.
I'll look for your response. The bamboo process is running so that is great!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you have a firewall or similar on the server?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
still no love. Will have to
netstat -an | grep 8085
tcp 0 0 10.12.16.38:8085 0.0.0.0:* LISTEN
and a telnet to localhost 8085 gives connection refused
ps -ef | grep bamb
tomcat 15206 1 6 13:07 pts/0 00:00:35 /usr/bin/java -Djava.util.logging.config.file=/opt/atlassian/atlassian-bamboo-5.6.0/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -XX:MaxPermSize=256m -Xms256m -Xmx384m -Djava.endorsed.dirs=/opt/atlassian/atlassian-bamboo-5.6.0/endorsed -classpath /opt/atlassian/atlassian-bamboo-5.6.0/bin/bootstrap.jar:/opt/atlassian/atlassian-bamboo-5.6.0/bin/tomcat-juli.jar -Dcatalina.base=/opt/atlassian/atlassian-bamboo-5.6.0 -Dcatalina.home=/opt/atlassian/atlassian-bamboo-5.6.0 -Djava.io.tmpdir=/opt/atlassian/atlassian-bamboo-5.6.0/temp org.apache.catalina.startup.Bootstrap start
frustrating.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.