Bitbucket crash upgrade 4.14 to 5.6.0 using Reverse proxy and context URL

Hi Nice update 5.6.0 great the server.xml properties moved to a separate properties file and it doesn't work ! :-(

I use a HTTPD front reverse proxy server to route trafic to my BitBucket server and I use a context URL tag and I use for communicating with Jira and Bamboo an extra port 7992.

Here is my original server.xml (most important config)


<Connector port="7990" protocol="HTTP/1.1"
connectionTimeout="20000"
useBodyEncodingForURI="true"
redirectPort="8443"
compression="on"
compressableMimeType="text/html,text/xml,text/plain,text/css,application/json,application/javascript,application/x-javascript"
proxyName="www.mywebsite.nl"
proxyPort="443"
scheme="https"
/>

<Connector port="7992" protocol="HTTP/1.1"
connectionTimeout="20000"
useBodyEncodingForURI="true"
compression="on"
compressableMimeType="text/html,text/xml,text/plain,text/css,application/json,application/javascript,application/x-javascript"
/>

<Context docBase="${catalina.home}/atlassian-bitbucket"
path="/bitbucket"
reloadable="false"
useHttpOnly="true"/>

 

And here is my bitbucket.properties file:

#>*******************************************************
#> Migrated to database at jdbc:postgresql://accatd01.mywebsite.nl:5432/bitbucketdb
#> Updated on 2016-12-29T21:23:30.434+01:00
#>*******************************************************
jdbc.driver=org.postgresql.Driver
jdbc.url=jdbc:postgresql://accatd01.mywebsite.nl:5432/bitbucketdb
jdbc.user=sa_atlassian
jdbc.password=<password>
server.port=7990
server.proxy-port=443
server.proxy-name=www.mywebsite.nl
server.scheme=https
server.secure=true

server.additional-connector.1.port=7992

 

Whats wrong with this config ? 

I tried to comment out the parts in the server.xml but nothing changes

BitBucket doesn't start and this is what I have in my log:

 

2017-12-04 01:44:59,531 ERROR [main] o.a.coyote.http11.Http11NioProtocol Failed to start end point associated with ProtocolHandler ["http-nio-7992"]
java.net.BindException: Address already in use
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)

 

lot of errors follow and this is the tail:

***************************
APPLICATION FAILED TO START
***************************

Description:

The Tomcat connector configured to listen on port 7992 failed to start. The port may already be in use or the connector may be misconfigured.

Action:

Verify the connector's configuration, identify and stop any process that's listening on port 7992, or configure this application to listen on another port.

2017-12-04 01:45:08,384 INFO [main] c.a.b.i.boot.log.BuildInfoLogger Bitbucket 5.6.0 has shut down

 

1 answer

1 accepted

1 vote
Accepted answer
Timothy Chin Community Champion Dec 04, 2017

2017-12-04 01:44:59,531 ERROR [main] o.a.coyote.http11.Http11NioProtocol Failed to start end point associated with ProtocolHandler ["http-nio-7992"]
java.net.BindException: Address already in use

This error means that there is another process already using the 7992 port. This can happen when you have not properly shutdown the previous run / instance of Bitbucket. At this point, kill -9 <pid> is probably your best option.

I allready checked that, there is no service running, if it starts then it crashes, I guess my properties files are wrong. Lets forget about the update, I have moved all my repos before to my BitBucket cloud, they are saved,  so I reinstall the full BitBuccket server, then we have a green field. But what about my properties file and server.xml ?

Timothy Chin Community Champion Dec 04, 2017

What about checking if the ports are being used itself?

lsof -i :<portnumber>

or

netstat -an | grep <port number>

 

Your properties file looks ok from here. If you reinstall Bitbucket and use that port, it could still be blocked.

Hi Timothy,

Thanks for your support  but the problem was in the settings:

This are the right settings:

#>*******************************************************
#> Migrated to database at jdbc:postgresql://accatd01.blabla.nl:5432/bitbucketdb
#> Updated on 2017-12-04T22:55:25.472+01:00
#>*******************************************************
jdbc.driver=org.postgresql.Driver
jdbc.url=jdbc:postgresql://accatd01.blabla.nl:5432/bitbucketdb
jdbc.user=sa_atlassian
jdbc.password=<pw>


#server.port=7990
server.connection-timeout=20000
server.proxy-port=443
server.proxy-name=www.blabla.nl
server.scheme=https
server.secure=true
server.context-path=/bitbucket
server.compression.mime-types=text/html,text/xml,text/plain,text/css,application/json,application/javascript,application/x-javascript
#server.useBodyEncodingForURI=true
server.compression.enabled=true

#server.additional-connector.1.port=7992

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

235 views 3 7
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you