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

Closed
Open
Created 12 years ago by Administrator@rootOwner
  • New issue

  • Report abuse

  • New issue

  • Report abuse

/home/git/repositories/............missing

Closed

/home/git/repositories/............missing

Created by: jbrooksuk

Running Ubuntu Server 12.10 I managed to get GitLab working again just fine, added a user, created a repo, then added my SSH key to my profile. Now I went to add an SSH key for the admin user (of the git server) and I get the following error when checking the status:

itradmin@DEVSRV01:/home/gitlab/gitlab$ sudo -u gitlab bundle exec rake gitlab:app:status RAILS_ENV=production

Starting diagnostics
config/database.yml............exists
config/gitlab.yml............exists
/home/git/repositories/............missing
rake aborted!
unexpected return
/home/gitlab/gitlab/lib/tasks/gitlab/status.rake:29:in `block (3 levels) in <top (required)>'
Tasks: TOP => gitlab:app:status
(See full trace by running task with --trace)

It's strange that it was previously working and now it isn't.

Linked issues
...

    Related merge requests

    • Administrator
      Administrator @root · 12 years ago
      Owner

      Created by: Razer6

      Does your gitlab user has permissions to access the repository path? Is it Symlink? Please use our Support Forum for questions regarding setup/configuration troubles. @riyad Ping

      By Administrator on 2013-02-24T18:22:35 (imported from GitLab project)

    • Administrator
      Administrator @root · 12 years ago
      Owner

      Created by: senny

      @jbrooksuk it's been two months since we heard from you. As @Razer6 explained it's better to use the support forum questions. Also if you open a topic on the forum please provide the information @Razer6 asked to facilitate the debugging.

      I'm closing this one.

      By Administrator on 2013-04-19T11:20:49 (imported from GitLab project)

    • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
    Please register or sign in to reply
    0 Assignees
    Assign to
    Milestone
    No milestone
    None
    None
    Time tracking
    Due date
    None
    None
    1
    Labels
    Awaiting feedback
    Assign labels
    • No matching results
    • Manage project labels
    Confidentiality
    Not confidential

    You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

    Lock issue
    Unlocked
    participants
    Reference: