Git clone return 500

How to Use GitLab System Administration
#1

Hello,
I updated gitlab a few months ago, and I think everything is good. I can see all files of my repo on web. Today, I clone it and it returns 500 error. I don’t know how to fix cause the lastest backup was removed (i thought that all is good).

Does anyone get this issue and know how to fix?

#2

@obfuscatus Please could you provide some more information about the environment where you have noticed the problem:

Please mention if you are seeing the issue on GitLab.com. If seeing the issue on your own hosted GitLab instance, please provide the following information:

For Omnibus installs:

Run a diagnostic check of GitLab and it’s components:

sudo gitlab-rake gitlab:check SANITIZE=true

Gather GitLab specific environment information:

sudo gitlab-rake gitlab:env:info

For source installs:

Run a diagnostic check of GitLab and it’s components:

sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true

Gather GitLab specific environment information:

sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production

Please ensure that any sensitive information is removed before posting

#3

@obfuscatus Also, if you are seeing the issue in your own self-managed environment, please attempt to retrieve a stack trace associated with the 500 error.

For Omnibus installs:

  • Tail the GitLab related log files using the command sudo gitlab-ctl tail
  • Reproduce the issue by cloning the repo
  • Copy the stack trace here but please remove all sensitive information first
#4

anybody home?