Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #4765

Closed
Open
Created Aug 13, 2013 by Administrator@rootOwner

Wow, this is really frustrating ...

Created by: spd0mufasa

I installed gitlab sometime ago. I then attempted to use it. If I upload a few files, it goes OK. If I upload 300-400, I get the " 502 Bad Gateway " error. I checked the logs under gitlab and do not see anything in them.

Scouring the internet, it seems that this error results from everything from not enough ram to not having the most up-to-date version of redis installed. There is no place to find out why the error happened. Then afterwards, it takes the server down so badly that I have to restart the entire host in order to have a chance of getting git back up again.

I run the checks and they're clean. I followed this documentation: How to install Gitlab 5.0 on CentOS 6 or RHEL6 - honestly, it was good but it does not look like git is stable enough to use commercially. Too many pieces of software it depends upon and they don't seem to work well together without some major Ruby debugging. It works fine for small files (I think I was able to load 30) but I would not try for anything much higher or else the server gets taken down with 502 errors ...

Assignee
Assign to
Time tracking