Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
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

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,644,716
Community Members
 
Community Events
196
Community Groups

git-http-backend git clone problem

Obss Sysadmin
Obss Sysadmin Nov 02, 2021

Hello,

When we try to clone the repo using the git tool, we get the following error. The git version we are using is 2.33.1, but there is a problem.

ERROR:

2021-11-02 14:26:26,703 ERROR [http-scmrequest-handler:thread-1] @1RWC27Hx866x126x0 192.168.4.1,127.0.0.1 "GET /scm/test/test1.git/info/refs HTTP/1.1" c.a.s.i.s.g.p.h.GitSmartExitHandler TEST/test1[3]: Read request from 192.168.4.1 failed
The following was written to stderr:
git: 'http-backend' is not a git command. See 'git --help'.
com.atlassian.utils.process.ProcessException: Non-zero exit code: 1
at com.atlassian.bitbucket.internal.process.nu.NioNuProcessHandler.callExitHandler(NioNuProcessHandler.java:332)
at com.atlassian.bitbucket.internal.process.nu.NioNuProcessHandler.finish(NioNuProcessHandler.java:381)
at com.atlassian.bitbucket.internal.process.nu.NioNuProcessHandler.onExit(NioNuProcessHandler.java:136)
at com.zaxxer.nuprocess.internal.BasePosixProcess.onExit(BasePosixProcess.java:315)
at com.zaxxer.nuprocess.linux.ProcessEpoll.handleExit(ProcessEpoll.java:365)
at com.zaxxer.nuprocess.linux.ProcessEpoll.cleanupProcess(ProcessEpoll.java:318)
at com.zaxxer.nuprocess.linux.ProcessEpoll.process(ProcessEpoll.java:253)
at com.zaxxer.nuprocess.internal.BaseEventProcessor.run(BaseEventProcessor.java:82)
at com.zaxxer.nuprocess.linux.ProcessEpoll.run(ProcessEpoll.java:154)
at com.zaxxer.nuprocess.linux.LinuxProcess.run(LinuxProcess.java:110)
at com.zaxxer.nuprocess.linux.LinProcessFactory.runProcess(LinProcessFactory.java:50)
at com.zaxxer.nuprocess.NuProcessBuilder.run(NuProcessBuilder.java:273)
at com.atlassian.bitbucket.internal.process.nu.NuNioProcessHelper.run(NuNioProcessHelper.java:75)
at com.atlassian.bitbucket.internal.process.NioCommand.call(NioCommand.java:46)
at com.atlassian.stash.internal.scm.git.protocol.http.GitSmartRequest.handleRequest(GitSmartRequest.java:80)
at com.atlassian.stash.internal.scm.git.protocol.http.HttpOtherRead.handleRequest(HttpOtherRead.java:16)
at com.atlassian.stash.internal.scm.ThrottledScmRequestFactory$AbstractThrottledScmRequest.handleRequest(ThrottledScmRequestFactory.java:56)
at com.atlassian.stash.internal.scm.DefaultHttpScmRequestExecutor.runSync(DefaultHttpScmRequestExecutor.java:173)
at com.atlassian.stash.internal.scm.DefaultHttpScmRequestExecutor.access$200(DefaultHttpScmRequestExecutor.java:48)
at com.atlassian.stash.internal.scm.DefaultHttpScmRequestExecutor$ScmAsyncRequest.run(DefaultHttpScmRequestExecutor.java:361)
at com.atlassian.stash.internal.request.DefaultRequestManager.lambda$wrapForAsync$0(DefaultRequestManager.java:169)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.lang.Thread.run(Thread.java:748)
... 1 frame trimmed

Answer
Watch
Like Be the first to like this
345 views

2 answers

0 votes
Kurt Klinner
Kurt Klinner
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.
Get recognized
Nov 05, 2021

@Obss Sysadmin 

Just did verify that, it is possible to use git 2.33.1 together with Bitbucket 7.15.1 without any issues, so most probably the git version you had installed was not able to find the git-http-backend (so the suggested workaround should help like described in the KB article)

Screenshot 2021-11-05 at 10.28.17.png

Cheers

Kurt

Reply
0 votes
Kurt Klinner
Kurt Klinner
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.
Get recognized
Nov 04, 2021

@Obss Sysadmin 

 

Did you check https://confluence.atlassian.com/bitbucketserverkb/git-commands-return-error-code-500-825790018.html?

 

Cheers

Kurt

View More Comments
Obss Sysadmin
Obss Sysadmin Nov 04, 2021

The problem is that bitbucket version 7.15.1 does not support git version 2.33. I fixed the problem with the following commands. Hope it helps those who encounter this problem.

sudo apt-get remove git
sudo apt-get remove --auto-remove git
sudo apt-get purge git
sudo apt-get purge --auto-remove git apt install liberror-perl git-man=1:2.25.1-1ubuntu3.2 git=1:2.25.1-1ubuntu3.2


Like
Reply

Suggest an answer

Log in or Sign up to answer
Bitbucket
Bitbucket
TAGS
AUG Leaders

Atlassian Community Events

See all events