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

simple HTTP request returns 500 error

john livingston May 4, 2023

Traditionally, our company has accessed bitbucket repositories using SSH such as

git ls-remote --heads ssh://

and this command is successful.

We are now implementing a new workflow that uses HTTP to access the repositories such as

git ls-remote --heads

and this command fails with error

fatal: unable to access '': The requested URL returned error: 500

debug mode for the bitbucket log revealed this message

DEBUG [http-scmrequest-handler:thread-10] <user> @919999750x162357408x0 "GET /scm/sqa/ratts.git/info/refs HTTP/1.1" c.a.s.i.s.g.p.h.GitSmartExitHandler SQA/ratts[53]: Read request from succeeded, but the following was written to stderr:
error: bogus format in GIT_CONFIG_PARAMETERS
fatal: unable to parse command-line config

I haven’t been successful resolving this error and need help.
The Bitbucket version is 7.21.0 (and yes, we are absolutely on an upgrade path!)

1 answer

1 accepted

0 votes
Answer accepted
john livingston May 16, 2023
This error related to our linux host git installation.

We used an updated git version installed from tarbal at /usr/local

Over time, git version updates (and rollbacks!) led to out-of-sync git files.
An exact and detailed investigation of the git installation problem was not performed.
However, timestamps revealed git files existing from multiple installs/versions.
Purging /usr/local of multiple git tarbal installs was thought to be time consuming and  problematic.
The remedy was to install a new/fresh version of git at /usr/local-git-<version>.
Then update user stash’s PATH to first reference /usr/local-git-<version>/bin.
And of course stop-bitbucket ; source .bashrc ; start-bitbucket.

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events