Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Bitbucket Data Center minimal setup

Alexander Kitaev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 23, 2015

I'm trying to run a minimal installation of Bitbucket Data Center but whatever I do, http://host:7990/admin/clustering shows no nodes (I have no load balancer as it is optional according to documentation):

clustering.png

Though I expected to see at least one.

When I try to run another node with "shared" directory shared on NFS, it starts bu then I see this error in the browser:

---------------------------------------------------------------------

A fatal error has occurred

The following problem occurred, which prevents Atlassian Bitbucket from starting:

  • Home directory '/home/username/atlassian/stashik/shared' is already locked by another running instance of Bitbucket.

    Please stop the other instance of Bitbucket and restart this instance.

    If you are absolutely certain that no other instance of Bitbucket is running, please remove the lock file '/home/username/atlassian/stashik/shared/.lock' and restart this instance.

---------------------------------------------------------------------

So the fact that the directory is shared prevents it from starting.

When I tried to specify the same Postgres database to the second node, it complained that the database is not empty (of course, it's not empty, it was initialized by the first node).

So I'm absolutely confused.

My bitbucket.properties files is:

 

#>*******************************************************
#> Migrated to database at jdbc:postgresql://IP1:5432/stashik
#> Updated on 2015-10-23T23:22:32.416+02:00
#>*******************************************************
jdbc.driver=org.postgresql.Driver
jdbc.url=jdbc:postgresql://IP1:5432/stashik
jdbc.user=postgres
jdbc.password=

# Use multicast to discover cluster nodes (recommended).
hazelcast.network.multicast=false

# If your network does not support multicast, you may uncomment the following lines and substitute
# the IP addresses of some or all of your cluster nodes. (Not all of the cluster nodes have to be
# listed here but at least one of them has to be active when a new node joins.) 
hazelcast.network.tcpip=true
hazelcast.network.tcpip.members=IP1:5701,IP2:5701

# The following should uniquely identify your cluster on the LAN. 
hazelcast.group.name=your-bitbucket-cluster
hazelcast.group.password=your-bitbucket-cluster

Where IP1 and IP2 are IP addresses of my 2 nodes. I tried both multicast and tcpip.

My setenv.sh file contains

JVM_SUPPORT_RECOMMENDED_ARGS="-Dcluster.node.name=bitbucket-1"

line.

The log file contains no errors.

What should I do to tell Bitbucket Server that my configuration should consist of multiple nodes?

1 answer

1 accepted

0 votes
Answer accepted
Roger Barnes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 25, 2015

Hi Alexander, I'd suggest contacting us via support.atlassian.com for this so we can dig into this.

One thing to check is that you have a Bitbucket Data Center license, not a Bitbucket Server license.

Aside, you will need a load balancer of some kind unless you're planning on pointing clients to individual nodes (not recommended). The documentation states "You can use the load balancer of your choice". We use and recommend HAProxy.

 

Alexander Kitaev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 26, 2015

Thanks, Bitbucket Data Center license solved the issue.

Ganesh Bhise February 16, 2018

Hey what you did to fix below error I am getting similar issue.


A fatal error has occurred

The following problem occurred, which prevents Atlassian Bitbucket from starting:

  • Home directory '/home/username/atlassian/stashik/shared' is already locked by another running instance of Bitbucket.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events