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

Closed
Open
Created May 06, 2013 by Administrator@rootOwner

DENIED by fallthru in GitLab 5.1

Created by: vfilimonov

Hello everyone

I just faced a problem with creating new repos and pushing to them in gitlab 5.1. On the push attempt git tells:

FATAL: W any user/repo email_1358258702 DENIED by fallthru (or you mis-spelled the reponame) fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.

Before I upgraded to 5.1 I did not face that issues. (well, I haven't created any repos in 5.0 but in 4.x it worked well). Pushing to existing repos works well.

I found that group permissions for newly created repos are different from the old ones:

root@server:/home/git/repositories/user# ls -l project_new.git/
total 32
drwxr-xr-x 2 git git 4096 May  3 11:00 branches
-rw-r--r-- 1 git git   66 May  3 11:00 config
-rw-r--r-- 1 git git   73 May  3 11:00 description
-rw-r--r-- 1 git git   23 May  3 11:00 HEAD
drwxr-xr-x 2 git git 4096 May  3 11:00 hooks
drwxr-xr-x 2 git git 4096 May  3 11:00 info
drwxr-xr-x 4 git git 4096 May  3 11:00 objects
drwxr-xr-x 4 git git 4096 May  3 11:00 refs
root@server:/home/git/repositories/user# ls -l project_old.git/
total 32
drwxrws--- 2 git git 4096 Jan 15 15:17 branches
-rw-rw---- 1 git git   91 Mar 21 18:55 config
-rw-rw---- 1 git git  274 Mar 21 18:55 gl-conf
-rw-rw---- 1 git git   23 Jan 15 15:17 HEAD
drwxrws--- 2 git git 4096 Apr  5 16:27 hooks
drwxrws--- 2 git git 4096 Jan 15 15:17 info
drwxrws--- 4 git git 4096 Jan 15 15:17 objects
drwxrws--- 4 git git 4096 Jan 15 15:17 refs

But aligning group permissions obviously does not help

I would appreciate any help with this issue.

Assignee
Assign to
Time tracking