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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,331
Community Members
 
Community Events
176
Community Groups

Unable to access some repos after upgrade from 5.16.10 to 7.21.6 - Bitbucket Data Center

Hi, we recently upgraded Bitbucket Data Center from version 5.16.10 to 7.21.6. We are unable to access some repos on Bitbucket UI (chrome), access to many other repos are working fine. 

I get the error 

'/usr/bin/git ls-tree -z -l refs/heads/master: --' exited with code 0

I can clone this repo using ssh.

Any help will be highly appreciated.

 

Thank you,

Naushad.

1 answer

1 accepted

0 votes
Answer accepted

Hi Naushad,

Which version of git are you using on the Bitbucket Server side?

Cheers,
Christian
Premier Support Engineer
Atlassian

We use git version 2.36.3 on both Bitbucket nodes

Also I can access the branches, commits etc on the UI. 

When I click on 'source' (on left hand side) - that's when the error comes.

Thanks for your help

Bitbucket Server 7.21.6 only supports git up to version 2.35.x, so downgrade your git install, most likely this will resolve this problem.

Cheers,

Christian
Premier Support Engineer
Atlassian

Thanks Christian, I downgraded git to 2.24.4 and the problem is resolved.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events