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

Closed
Open
Created Sep 10, 2013 by Administrator@rootOwner

Can't save project. Please try again later.

Created by: knoff

  1. Summary When I try create a new project, it say: Can't save project. Please try again later.
  2. Reproduse Clean server on Ubuntu 12.04, Ruby 1.9.3, Git 1.8.4, Gitlab 6 installed by instruction. Create new project with any name.
  3. Expected behavior. When I try create a new project It must create project in repositories folder and project in gilab database, then I can manage project.
  4. Observed behavior. When I try create a new project, it say: Can't save project. Please try again later. It create project in repositories In gitlab database project is not created
  5. Relevant logs In sidekiq.log no records about errors. (except cases when i try create project allready exists in repositories folder)
  6. Output of checks

In gitlab:check I see this: GitLab Shell version >= 1.7.0 ? ... OK (1.7.1) Repo base directory exists? ... yes Repo base directory is a symlink? ... no Repo base owned by git:git? ... yes Repo base access is drwxrws---? ... yes post-receive hook up-to-date? ... can't check because of previous errors post-receive hooks in repos are links: ... can't check because of previous errors update file exists and git user is its owner... 7. Posible fixes Solution described in Issue #3328 (closed) not work for me.

Assignee
Assign to
Time tracking