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

Closed
Open
Created Jan 25, 2016 by Administrator@rootOwner

gitlab:backup:create error message: fatal: Not a git repository

Created by: rjhornsby

Have started getting this message after upgrading Gitlab to 8.4.0

$ sudo gitlab-rake gitlab:backup:create
fatal: Not a git repository (or any parent up to mount point /opt)
Stopping at filesystem boundary (...)

For reference, this appears to be similar to #1155 (closed).

The backup appears to otherwise complete successfully. Like the comments in #1155 (closed), we are using a different directory for the backups (/var/opt/gitlab/backups), but haven't changed any of the configuration -- just ran the rpm -Uvh to upgrade to 8.4 over the weekend.

I admittedly don't know or understand enough about rake to know where to look to see what is happening behind the scenes of the gitlab-rake command.

Assignee
Assign to
Time tracking