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
  • #764

Closed
Open
Created May 01, 2012 by Administrator@rootOwner

Add a trouble shooting guide to the Wiki/Docs

Created by: riyad

It would be nice to be guided through a standardized trouble shooting process, especially because there are so many separate parts that need to be working together in order to have GitLab running. Especially for parts that yield notoriously unhelpful/general error messages (e.g. Gitolite about SSH or GitLab about Gitolite)

What I was thinking of was to have a few steps/commands separately documented for each component (e.g. SSH, Gitolite, MySQL, Redis, GitLab) to check if it is working at all and working in concert with the components it is supposed to work with.

There could also be a "common errors/pitfalls" section. This could be started by collecting previous bug reports and their solutions.

Assignee
Assign to
Time tracking