error 400 while accessing http

hello
we are getting this error frequently:
build	24-Feb-2014 21:39:21	     [exec]   [RuntimeException]                                                                                                                                                                                                                                                                                                              
build	24-Feb-2014 21:39:21	     [exec]   Failed to execute git clone 'http://stash.mydomain.com/scm/myproject/myrepo.git' '/mydir/myrepo' && cd '/mydir/myrepo' && git remote add composer 'http://stash.mydomain.com/scm/myproject/myrepo.git' && git fetch composer  
build	24-Feb-2014 21:39:21	     [exec]                                                                                                                                                                                                                                                                                                                                   
build	24-Feb-2014 21:39:21	     [exec]   error: The requested URL returned error: 400 while accessing http://stash.mydomain.com/scm/myproject/myrepo.git/info/refs                                                                                                                                                                                                      
build	24-Feb-2014 21:39:21	     [exec]   fatal: HTTP request failed

at other times it works.

in atlassian-stash.log we see this relevant line:

" It looks like we've received a 'dumb' protocol git request. "

but in atlassian-stash-access.log, the only git version is "git/1.7.10"

this is stash version 2.10.1.

any idea how to deal with this?

2 answers

i noticed that 'dumb' protocol error messages occur after we upgrade stash to v 2.10.1.

previously we ran stash v 2.5.2 and there was no such error.

we found 603 occurences of this error messages since we did the upgrade on February 2.

Hi Edwin,

That doesn't sound right. My initial suspicion is that you have a proxy that is doing the wrong thing (but that's purely a guess). In any case would you mind raising a support ticket and attach your Stash logs?

To save a round-trip it might also help to capture the trace of the fetch using the following:

https://bitbucket.org/atlassian/git-client-debug/src/e55c6ac3728ec1e17d44d4332f4db14d9ce239f5/bin/git-debug-clone?at=master

(You may need to modify the 'clone' part)

Cheers,

Charles

i can't use your git clone wrapper since the git cloning operation is done by composer.

still no clue what's going on.

Hi Edwin,

Did you raise a support ticket?

Charles

yes and the answer is the same as yours.

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 ...

250 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